{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/plan-to-reopen-axis-streams-after-a-source-rotation-change/", "item": { "id": "https://update.dsesecurity.com/updates/plan-to-reopen-axis-streams-after-a-source-rotation-change/", "slug": "plan-to-reopen-axis-streams-after-a-source-rotation-change", "url": "https://update.dsesecurity.com/updates/plan-to-reopen-axis-streams-after-a-source-rotation-change/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/plan-to-reopen-axis-streams-after-a-source-rotation-change.md", "json": "https://update.dsesecurity.com/api/v1/posts/plan-to-reopen-axis-streams-after-a-source-rotation-change/" }, "title": "Plan to reopen Axis streams after a source rotation change", "summary": "Distinguish Axis source rotation from per-stream orientation. Plan stream reacquisition and review automatic-rotation state before accepting a source-orientation change.", "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": "business-continuity", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "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-29T17:41:18+00:00", "modified_at": "2026-10-29T17:41:38+00:00", "reviewed_on": "2026-10-29", "reading_minutes": 3, "word_count": 526, "potentially_affected": "Axis products exposing the documented Image source rotation interface; confirm actual device, hardware and software applicability before applying the proposed checks.", "dse_recommendation": "DSE recommends scheduling source rotation with an explicit consumer-reacquisition and orientation check.", "primary_source": { "name": "Axis Communications — Image source rotation", "url": "https://developer.axis.com/vapix/network-video/image-source-rotation/", "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: Plan a source-rotation change as a shared image change with stream reacquisition. Confirm the device’s source-rotation support and automatic-rotation setting before correcting one consumer’s orientation through a copied request.

\n

Source fact: documented behavior

\n

Axis’s Image source rotation explains that source rotation is handled at the sensor dataflow so streams derived from that source rotate the same way.

\n

For products using global source rotation, the documentation says a stream cannot request a rotation differing from the global configuration.

\n

Changing ImageSource.I#.Rotation closes all open streams and requires new stream requests; changing that value through the API also turns off ImageSource.I#.AutoRotationEnabled.

\n

What the source does not establish

\n

Do not infer that every Axis device implements source rotation or automatic rotation. Check the actual source and property support. Keep this orientation operation separate from physical mounting changes, dewarping selection and a complete analytics or privacy-region review. Do not promise uninterrupted recording; explicitly plan and verify consumer recovery.

\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 scheduling source rotation with an explicit consumer-reacquisition and orientation check.

\n
    \n
  1. Read the source-rotation support, current rotation and available automatic-rotation state from the target source. Preserve the returned values, including any missing property. Confirm the desired orientation with the operator owner using a permitted baseline view. Identify dependent consumers before the change and arrange an authorized window with appropriate operational coverage.
    2. \n
  2. Apply the approved supported rotation value to the identified source. Treat closed streams as a planned transition requiring verification, not as evidence that clients necessarily recovered. Have each relevant consumer request or reacquire its stream through the supported client workflow. Read the source configuration again and explicitly review the automatic-rotation state after the manual change.
    3. \n
  3. Inspect the resulting live and recorded orientation and examine the actual change interval. Check the operational regions, overlays or other dependent functions required by the site’s approved design. If a consumer does not recover or the intended orientation is wrong, follow the prepared supported restoration plan. Do not keep changing rotation at several layers until one preview happens to look correct.
    4. \n
\n

Verification and evidence

\n

Retain the before-and-after source values, change time, affected-consumer list and each consumer’s reacquisition result. Keep retrieved recording evidence for the relevant interval where authorized. Separate an accepted parameter update from restored live view, restored recording and any remaining unverified dependency.

\n

For a proposed rehearsal, ask the reviewer to account for a consumer that has not yet reconnected and an automatic-rotation setting that no longer matches the intended policy. Require an explicit disposition for both before acceptance. Record observations after the real exercise; this article does not assert a measured gap duration, successful reconnection or uninterrupted operation.

\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: Plan a source-rotation change as a shared image change with stream reacquisition. Confirm the device’s source-rotation support and automatic-rotation setting before correcting one consumer’s orientation through a copied request.\nSource fact: documented behavior\nAxis’s Image source rotation explains that source rotation is handled at the sensor dataflow so streams derived from that source rotate the same way.\nFor products using global source rotation, the documentation says a stream cannot request a rotation differing from the global configuration.\nChanging ImageSource.I#.Rotation closes all open streams and requires new stream requests; changing that value through the API also turns off ImageSource.I#.AutoRotationEnabled.\nWhat the source does not establish\nDo not infer that every Axis device implements source rotation or automatic rotation. Check the actual source and property support. Keep this orientation operation separate from physical mounting changes, dewarping selection and a complete analytics or privacy-region review. Do not promise uninterrupted recording; explicitly plan and verify consumer recovery.\nApplicability questions\n\nWhich exact image source and software are being changed?\nDoes the device expose source-rotation and automatic-rotation properties?\nWhich authorized live, recording and analytic consumers use that source?\nWho will verify reacquisition and decide how any observed gap is handled?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\nDSE recommends scheduling source rotation with an explicit consumer-reacquisition and orientation check.\n\nRead the source-rotation support, current rotation and available automatic-rotation state from the target source. Preserve the returned values, including any missing property. Confirm the desired orientation with the operator owner using a permitted baseline view. Identify dependent consumers before the change and arrange an authorized window with appropriate operational coverage.\nApply the approved supported rotation value to the identified source. Treat closed streams as a planned transition requiring verification, not as evidence that clients necessarily recovered. Have each relevant consumer request or reacquire its stream through the supported client workflow. Read the source configuration again and explicitly review the automatic-rotation state after the manual change.\nInspect the resulting live and recorded orientation and examine the actual change interval. Check the operational regions, overlays or other dependent functions required by the site’s approved design. If a consumer does not recover or the intended orientation is wrong, follow the prepared supported restoration plan. Do not keep changing rotation at several layers until one preview happens to look correct.\n\nVerification and evidence\nRetain the before-and-after source values, change time, affected-consumer list and each consumer’s reacquisition result. Keep retrieved recording evidence for the relevant interval where authorized. Separate an accepted parameter update from restored live view, restored recording and any remaining unverified dependency.\nFor a proposed rehearsal, ask the reviewer to account for a consumer that has not yet reconnected and an automatic-rotation setting that no longer matches the intended policy. Require an explicit disposition for both before acceptance. Record observations after the real exercise; this article does not assert a measured gap duration, successful reconnection or uninterrupted operation.\nOfficial references\n\nImage source rotation — 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: Plan a source-rotation change as a shared image change with stream reacquisition. Confirm the device’s source-rotation support and automatic-rotation setting before correcting one consumer’s orientation through a copied request.\n\n## Source fact: documented behavior\n\nAxis’s [Image source rotation](https://developer.axis.com/vapix/network-video/image-source-rotation/) explains that source rotation is handled at the sensor dataflow so streams derived from that source rotate the same way.\n\nFor products using global source rotation, the documentation says a stream cannot request a rotation differing from the global configuration.\n\nChanging ImageSource.I#.Rotation closes all open streams and requires new stream requests; changing that value through the API also turns off ImageSource.I#.AutoRotationEnabled.\n\n## What the source does not establish\n\nDo not infer that every Axis device implements source rotation or automatic rotation. Check the actual source and property support. Keep this orientation operation separate from physical mounting changes, dewarping selection and a complete analytics or privacy-region review. Do not promise uninterrupted recording; explicitly plan and verify consumer recovery.\n\n## Applicability questions\n\n- Which exact image source and software are being changed?\n\n- Does the device expose source-rotation and automatic-rotation properties?\n\n- Which authorized live, recording and analytic consumers use that source?\n\n- Who will verify reacquisition and decide how any observed gap is handled?\n\n## DSE recommendation: controlled next steps\n\nThe following steps are DSE recommendations based on the cited source.\n\nDSE recommends scheduling source rotation with an explicit consumer-reacquisition and orientation check.\n\n- Read the source-rotation support, current rotation and available automatic-rotation state from the target source. Preserve the returned values, including any missing property. Confirm the desired orientation with the operator owner using a permitted baseline view. Identify dependent consumers before the change and arrange an authorized window with appropriate operational coverage.\n\n- Apply the approved supported rotation value to the identified source. Treat closed streams as a planned transition requiring verification, not as evidence that clients necessarily recovered. Have each relevant consumer request or reacquire its stream through the supported client workflow. Read the source configuration again and explicitly review the automatic-rotation state after the manual change.\n\n- Inspect the resulting live and recorded orientation and examine the actual change interval. Check the operational regions, overlays or other dependent functions required by the site’s approved design. If a consumer does not recover or the intended orientation is wrong, follow the prepared supported restoration plan. Do not keep changing rotation at several layers until one preview happens to look correct.\n\n## Verification and evidence\n\nRetain the before-and-after source values, change time, affected-consumer list and each consumer’s reacquisition result. Keep retrieved recording evidence for the relevant interval where authorized. Separate an accepted parameter update from restored live view, restored recording and any remaining unverified dependency.\n\nFor a proposed rehearsal, ask the reviewer to account for a consumer that has not yet reconnected and an automatic-rotation setting that no longer matches the intended policy. Require an explicit disposition for both before acceptance. Record observations after the real exercise; this article does not assert a measured gap duration, successful reconnection or uninterrupted operation.\n\n## Official references\n\n- [Image source rotation](https://developer.axis.com/vapix/network-video/image-source-rotation/) — 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/plan-to-reopen-axis-streams-after-a-source-rotation-change/", "url": "https://update.dsesecurity.com/updates/plan-to-reopen-axis-streams-after-a-source-rotation-change/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-10-29" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/plan-to-reopen-axis-streams-after-a-source-rotation-change/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Business Continuity", "item": "https://update.dsesecurity.com/topic/business-continuity/" }, { "@type": "ListItem", "position": 3, "name": "Plan to reopen Axis streams after a source rotation change", "item": "https://update.dsesecurity.com/updates/plan-to-reopen-axis-streams-after-a-source-rotation-change/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/plan-to-reopen-axis-streams-after-a-source-rotation-change/#article", "identifier": "https://update.dsesecurity.com/updates/plan-to-reopen-axis-streams-after-a-source-rotation-change/", "url": "https://update.dsesecurity.com/updates/plan-to-reopen-axis-streams-after-a-source-rotation-change/", "headline": "Plan to reopen Axis streams after a source rotation change", "description": "Distinguish Axis source rotation from per-stream orientation. Plan stream reacquisition and review automatic-rotation state before accepting…", "abstract": "Distinguish Axis source rotation from per-stream orientation. Plan stream reacquisition and review automatic-rotation state before accepting a source-orientation change.", "articleBody": "Bottom line: Plan a source-rotation change as a shared image change with stream reacquisition. Confirm the device’s source-rotation support and automatic-rotation setting before correcting one consumer’s orientation through a copied request.\nSource fact: documented behavior\nAxis’s Image source rotation explains that source rotation is handled at the sensor dataflow so streams derived from that source rotate the same way.\nFor products using global source rotation, the documentation says a stream cannot request a rotation differing from the global configuration.\nChanging ImageSource.I#.Rotation closes all open streams and requires new stream requests; changing that value through the API also turns off ImageSource.I#.AutoRotationEnabled.\nWhat the source does not establish\nDo not infer that every Axis device implements source rotation or automatic rotation. Check the actual source and property support. Keep this orientation operation separate from physical mounting changes, dewarping selection and a complete analytics or privacy-region review. Do not promise uninterrupted recording; explicitly plan and verify consumer recovery.\nApplicability questions\n\nWhich exact image source and software are being changed?\nDoes the device expose source-rotation and automatic-rotation properties?\nWhich authorized live, recording and analytic consumers use that source?\nWho will verify reacquisition and decide how any observed gap is handled?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\nDSE recommends scheduling source rotation with an explicit consumer-reacquisition and orientation check.\n\nRead the source-rotation support, current rotation and available automatic-rotation state from the target source. Preserve the returned values, including any missing property. Confirm the desired orientation with the operator owner using a permitted baseline view. Identify dependent consumers before the change and arrange an authorized window with appropriate operational coverage.\nApply the approved supported rotation value to the identified source. Treat closed streams as a planned transition requiring verification, not as evidence that clients necessarily recovered. Have each relevant consumer request or reacquire its stream through the supported client workflow. Read the source configuration again and explicitly review the automatic-rotation state after the manual change.\nInspect the resulting live and recorded orientation and examine the actual change interval. Check the operational regions, overlays or other dependent functions required by the site’s approved design. If a consumer does not recover or the intended orientation is wrong, follow the prepared supported restoration plan. Do not keep changing rotation at several layers until one preview happens to look correct.\n\nVerification and evidence\nRetain the before-and-after source values, change time, affected-consumer list and each consumer’s reacquisition result. Keep retrieved recording evidence for the relevant interval where authorized. Separate an accepted parameter update from restored live view, restored recording and any remaining unverified dependency.\nFor a proposed rehearsal, ask the reviewer to account for a consumer that has not yet reconnected and an automatic-rotation setting that no longer matches the intended policy. Require an explicit disposition for both before acceptance. Record observations after the real exercise; this article does not assert a measured gap duration, successful reconnection or uninterrupted operation.\nOfficial references\n\nImage source rotation — 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-29T17:41:18+00:00", "dateModified": "2026-10-29T17:41:38+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/plan-to-reopen-axis-streams-after-a-source-rotation-change/" }, "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/plan-to-reopen-axis-streams-after-a-source-rotation-change/#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": "Plan to reopen Axis streams after a source rotation change" }, "articleSection": [ "Business Continuity", "Video Surveillance" ], "keywords": [ "Business Continuity", "Video Surveillance", "Guide", "Advisory priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "@type": "Thing", "name": "Video Surveillance", "url": "https://update.dsesecurity.com/topic/video-surveillance/" } ], "wordCount": 526, "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 — Image source rotation", "url": "https://developer.axis.com/vapix/network-video/image-source-rotation/" } } ] } }