{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/review-axis-local-video-output-separately-from-stream-image-settings/", "item": { "id": "https://update.dsesecurity.com/updates/review-axis-local-video-output-separately-from-stream-image-settings/", "slug": "review-axis-local-video-output-separately-from-stream-image-settings", "url": "https://update.dsesecurity.com/updates/review-axis-local-video-output-separately-from-stream-image-settings/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/review-axis-local-video-output-separately-from-stream-image-settings.md", "json": "https://update.dsesecurity.com/api/v1/posts/review-axis-local-video-output-separately-from-stream-image-settings/" }, "title": "Review Axis local video output separately from stream image settings", "summary": "Check Axis local video-output configuration separately from ordinary stream image settings. Verify the selected source, orientation and overlays on the actual output and recording paths.", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "advisory", "name": "Advisory" }, "featured": false, "image": { "theme": "physical-security", "label": "Physical security", "alt": "Integrated video surveillance and controlled entry at a modern commercial facility.", "card_url": "https://update.dsesecurity.com/assets/editorial/physical-security-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/physical-security-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "video-surveillance", "name": "Video Surveillance", "url": "https://update.dsesecurity.com/topic/video-surveillance/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-10-29T19:49:51+00:00", "modified_at": "2026-10-29T19:50:08+00:00", "reviewed_on": "2026-10-29", "reading_minutes": 3, "word_count": 520, "potentially_affected": "Axis products exposing the documented Video output API interface; confirm actual device, hardware and software applicability before applying the proposed checks.", "dse_recommendation": "DSE recommends keeping an output-specific configuration and observation record alongside the ordinary stream configuration.", "primary_source": { "name": "Axis Communications — Video output API", "url": "https://developer.axis.com/vapix/network-video/video-output-api/", "published_on": null, "authority": "Axis Communications" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

Bottom line: Review the local monitor output as its own configured path. Do not assume a change to the ordinary video-source image parameters has automatically produced the intended orientation or overlays on the connected display.

\n

Source fact: documented behavior

\n

Axis’s Video output API says settings made through this interface affect only the video output; ordinary source Image parameters do not govern that output unless explicitly requested through the API.

\n

Without configuration through the Video output API, the documented output is a raw stream.

\n

The documented availability is for Axis devices supporting HDMI and view areas, with Properties.VideoOutputControl.VideoOutputControl=yes identifying support.

\n

What the source does not establish

\n

Do not infer identical behavior on an arbitrary camera, decoder or display. Do not treat an accepted monitor image as acceptance of the recording stream, privacy configuration or investigator export. Confirm the exact product’s supported output schema and source choices, and review sensitive information shown on a public-facing screen separately.

\n

Applicability questions

\n\n

DSE recommendation: controlled next steps

\n

The following steps are DSE recommendations based on the cited source.

\n

DSE recommends keeping an output-specific configuration and observation record alongside the ordinary stream configuration.

\n
    \n
  1. Identify the actual device, connected display and intended source. Retrieve the supported output configuration through the documented workflow and record the prior state. Have the display owner approve the orientation and permitted overlay content. Avoid using a screenshot from the ordinary web stream as the only description of what the local monitor should show.
    2. \n
  2. Review which settings are supplied to the output and which source settings, if any, the supported configuration explicitly requests. Apply only the approved output change in a controlled window. Inspect the physical display with an authorized observer, then review the ordinary stream separately. Keep a mirrored public-view requirement distinct from a normal surveillance-view requirement instead of applying one assumption to every consumer.
    3. \n
  3. Retrieve a permitted recorded interval through the normal review path and confirm the separately stated recording requirement. If the output and stream differ unexpectedly, investigate their actual configurations before editing multiple image controls. Restore the approved arrangement when the intended output cannot be established. Keep any broader display-access or privacy question with its responsible owner.
    4. \n
\n

Verification and evidence

\n

Retain product/output identity, supported configuration, selected source, before-and-after settings and the observer’s display result. Keep stream and recording observations in distinct fields. Ask another reviewer to explain which path each setting and observation covers.

\n

Use a proposed desk case in which a source-image change is presented as proof of a local-monitor correction without an output observation. Require the reviewer to obtain the missing evidence. These checks do not report a tested monitor, certified display compatibility or an accepted privacy or recording outcome.

\n

Official references

\n\n

Source review completed October 29, 2026. Recheck the official documentation and the deployed device’s capabilities before changing production settings.

\n", "content_text": "Bottom line: Review the local monitor output as its own configured path. Do not assume a change to the ordinary video-source image parameters has automatically produced the intended orientation or overlays on the connected display.\nSource fact: documented behavior\nAxis’s Video output API says settings made through this interface affect only the video output; ordinary source Image parameters do not govern that output unless explicitly requested through the API.\nWithout configuration through the Video output API, the documented output is a raw stream.\nThe documented availability is for Axis devices supporting HDMI and view areas, with Properties.VideoOutputControl.VideoOutputControl=yes identifying support.\nWhat the source does not establish\nDo not infer identical behavior on an arbitrary camera, decoder or display. Do not treat an accepted monitor image as acceptance of the recording stream, privacy configuration or investigator export. Confirm the exact product’s supported output schema and source choices, and review sensitive information shown on a public-facing screen separately.\nApplicability questions\n\nWhich physical output and exact source should the display show?\nDoes the target device report the documented output support?\nWhich orientation and overlay settings are intended specifically for that output?\nWhat separate live and recorded views must retain their own accepted behavior?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\nDSE recommends keeping an output-specific configuration and observation record alongside the ordinary stream configuration.\n\nIdentify the actual device, connected display and intended source. Retrieve the supported output configuration through the documented workflow and record the prior state. Have the display owner approve the orientation and permitted overlay content. Avoid using a screenshot from the ordinary web stream as the only description of what the local monitor should show.\nReview which settings are supplied to the output and which source settings, if any, the supported configuration explicitly requests. Apply only the approved output change in a controlled window. Inspect the physical display with an authorized observer, then review the ordinary stream separately. Keep a mirrored public-view requirement distinct from a normal surveillance-view requirement instead of applying one assumption to every consumer.\nRetrieve a permitted recorded interval through the normal review path and confirm the separately stated recording requirement. If the output and stream differ unexpectedly, investigate their actual configurations before editing multiple image controls. Restore the approved arrangement when the intended output cannot be established. Keep any broader display-access or privacy question with its responsible owner.\n\nVerification and evidence\nRetain product/output identity, supported configuration, selected source, before-and-after settings and the observer’s display result. Keep stream and recording observations in distinct fields. Ask another reviewer to explain which path each setting and observation covers.\nUse a proposed desk case in which a source-image change is presented as proof of a local-monitor correction without an output observation. Require the reviewer to obtain the missing evidence. These checks do not report a tested monitor, certified display compatibility or an accepted privacy or recording outcome.\nOfficial references\n\nVideo output API — Axis Communications; official VAPIX documentation.\n\nSource review completed October 29, 2026. Recheck the official documentation and the deployed device’s capabilities before changing production settings.", "content_markdown": "Bottom line: Review the local monitor output as its own configured path. Do not assume a change to the ordinary video-source image parameters has automatically produced the intended orientation or overlays on the connected display.\n\n## Source fact: documented behavior\n\nAxis’s [Video output API](https://developer.axis.com/vapix/network-video/video-output-api/) says settings made through this interface affect only the video output; ordinary source Image parameters do not govern that output unless explicitly requested through the API.\n\nWithout configuration through the Video output API, the documented output is a raw stream.\n\nThe documented availability is for Axis devices supporting HDMI and view areas, with Properties.VideoOutputControl.VideoOutputControl=yes identifying support.\n\n## What the source does not establish\n\nDo not infer identical behavior on an arbitrary camera, decoder or display. Do not treat an accepted monitor image as acceptance of the recording stream, privacy configuration or investigator export. Confirm the exact product’s supported output schema and source choices, and review sensitive information shown on a public-facing screen separately.\n\n## Applicability questions\n\n- Which physical output and exact source should the display show?\n\n- Does the target device report the documented output support?\n\n- Which orientation and overlay settings are intended specifically for that output?\n\n- What separate live and recorded views must retain their own accepted behavior?\n\n## DSE recommendation: controlled next steps\n\nThe following steps are DSE recommendations based on the cited source.\n\nDSE recommends keeping an output-specific configuration and observation record alongside the ordinary stream configuration.\n\n- Identify the actual device, connected display and intended source. Retrieve the supported output configuration through the documented workflow and record the prior state. Have the display owner approve the orientation and permitted overlay content. Avoid using a screenshot from the ordinary web stream as the only description of what the local monitor should show.\n\n- Review which settings are supplied to the output and which source settings, if any, the supported configuration explicitly requests. Apply only the approved output change in a controlled window. Inspect the physical display with an authorized observer, then review the ordinary stream separately. Keep a mirrored public-view requirement distinct from a normal surveillance-view requirement instead of applying one assumption to every consumer.\n\n- Retrieve a permitted recorded interval through the normal review path and confirm the separately stated recording requirement. If the output and stream differ unexpectedly, investigate their actual configurations before editing multiple image controls. Restore the approved arrangement when the intended output cannot be established. Keep any broader display-access or privacy question with its responsible owner.\n\n## Verification and evidence\n\nRetain product/output identity, supported configuration, selected source, before-and-after settings and the observer’s display result. Keep stream and recording observations in distinct fields. Ask another reviewer to explain which path each setting and observation covers.\n\nUse a proposed desk case in which a source-image change is presented as proof of a local-monitor correction without an output observation. Require the reviewer to obtain the missing evidence. These checks do not report a tested monitor, certified display compatibility or an accepted privacy or recording outcome.\n\n## Official references\n\n- [Video output API](https://developer.axis.com/vapix/network-video/video-output-api/) — Axis Communications; official VAPIX documentation.\n\nSource review completed October 29, 2026. Recheck the official documentation and the deployed device’s capabilities before changing production settings." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/review-axis-local-video-output-separately-from-stream-image-settings/", "url": "https://update.dsesecurity.com/updates/review-axis-local-video-output-separately-from-stream-image-settings/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-10-29" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/review-axis-local-video-output-separately-from-stream-image-settings/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Video Surveillance", "item": "https://update.dsesecurity.com/topic/video-surveillance/" }, { "@type": "ListItem", "position": 3, "name": "Review Axis local video output separately from stream image settings", "item": "https://update.dsesecurity.com/updates/review-axis-local-video-output-separately-from-stream-image-settings/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/review-axis-local-video-output-separately-from-stream-image-settings/#article", "identifier": "https://update.dsesecurity.com/updates/review-axis-local-video-output-separately-from-stream-image-settings/", "url": "https://update.dsesecurity.com/updates/review-axis-local-video-output-separately-from-stream-image-settings/", "headline": "Review Axis local video output separately from stream image settings", "description": "Check Axis local video-output configuration separately from ordinary stream image settings.", "abstract": "Check Axis local video-output configuration separately from ordinary stream image settings. Verify the selected source, orientation and overlays on the actual output and recording paths.", "articleBody": "Bottom line: Review the local monitor output as its own configured path. Do not assume a change to the ordinary video-source image parameters has automatically produced the intended orientation or overlays on the connected display.\nSource fact: documented behavior\nAxis’s Video output API says settings made through this interface affect only the video output; ordinary source Image parameters do not govern that output unless explicitly requested through the API.\nWithout configuration through the Video output API, the documented output is a raw stream.\nThe documented availability is for Axis devices supporting HDMI and view areas, with Properties.VideoOutputControl.VideoOutputControl=yes identifying support.\nWhat the source does not establish\nDo not infer identical behavior on an arbitrary camera, decoder or display. Do not treat an accepted monitor image as acceptance of the recording stream, privacy configuration or investigator export. Confirm the exact product’s supported output schema and source choices, and review sensitive information shown on a public-facing screen separately.\nApplicability questions\n\nWhich physical output and exact source should the display show?\nDoes the target device report the documented output support?\nWhich orientation and overlay settings are intended specifically for that output?\nWhat separate live and recorded views must retain their own accepted behavior?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\nDSE recommends keeping an output-specific configuration and observation record alongside the ordinary stream configuration.\n\nIdentify the actual device, connected display and intended source. Retrieve the supported output configuration through the documented workflow and record the prior state. Have the display owner approve the orientation and permitted overlay content. Avoid using a screenshot from the ordinary web stream as the only description of what the local monitor should show.\nReview which settings are supplied to the output and which source settings, if any, the supported configuration explicitly requests. Apply only the approved output change in a controlled window. Inspect the physical display with an authorized observer, then review the ordinary stream separately. Keep a mirrored public-view requirement distinct from a normal surveillance-view requirement instead of applying one assumption to every consumer.\nRetrieve a permitted recorded interval through the normal review path and confirm the separately stated recording requirement. If the output and stream differ unexpectedly, investigate their actual configurations before editing multiple image controls. Restore the approved arrangement when the intended output cannot be established. Keep any broader display-access or privacy question with its responsible owner.\n\nVerification and evidence\nRetain product/output identity, supported configuration, selected source, before-and-after settings and the observer’s display result. Keep stream and recording observations in distinct fields. Ask another reviewer to explain which path each setting and observation covers.\nUse a proposed desk case in which a source-image change is presented as proof of a local-monitor correction without an output observation. Require the reviewer to obtain the missing evidence. These checks do not report a tested monitor, certified display compatibility or an accepted privacy or recording outcome.\nOfficial references\n\nVideo output API — Axis Communications; official VAPIX documentation.\n\nSource review completed October 29, 2026. Recheck the official documentation and the deployed device’s capabilities before changing production settings.", "datePublished": "2026-10-29T19:49:51+00:00", "dateModified": "2026-10-29T19:50:08+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/review-axis-local-video-output-separately-from-stream-image-settings/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/review-axis-local-video-output-separately-from-stream-image-settings/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Review Axis local video output separately from stream image settings" }, "articleSection": [ "Video Surveillance" ], "keywords": [ "Video Surveillance", "Guide", "Advisory priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Video Surveillance", "url": "https://update.dsesecurity.com/topic/video-surveillance/" } ], "wordCount": 520, "timeRequired": "PT3M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Axis Communications — Video output API", "url": "https://developer.axis.com/vapix/network-video/video-output-api/" } } ] } }