# Separate Axis stream request overrides from channel defaults > Compare the actual Axis stream request with video-channel defaults before making shared configuration changes. Request overrides and saved default values answer different diagnostic questions. - Canonical URL: https://update.dsesecurity.com/updates/separate-axis-stream-request-overrides-from-channel-defaults/ - Publisher: Detection Systems & Engineering (DSE Security) - Author: DSE Security Editorial Team - Published: 2026-10-29T17:41:28+00:00 - Modified: 2026-10-29T17:41:38+00:00 - Last reviewed by DSE: 2026-10-29 - Resource type: Guide - DSE priority: Advisory - Topics: IT, Video Surveillance - Reading time: 3 minutes ## What you need to know Compare the actual Axis stream request with video-channel defaults before making shared configuration changes. Request overrides and saved default values answer different diagnostic questions. ## Potentially affected Axis products exposing the documented Parameter management for video channels interface; confirm actual device, hardware and software applicability before applying the proposed checks. ## DSE recommendation DSE recommends resolving request-versus-default precedence before altering shared video-channel settings. ## Article Bottom line: Inspect the consumer’s actual stream options before changing channel defaults. Use a controlled with-and-without-override comparison to identify the setting being requested instead of assuming every client inherits the same value. ## Source fact: documented behavior Axis’s [Parameter management for video channels](https://developer.axis.com/vapix/network-video/parameter-management/image-api/) states that video-channel parameters supply default values unless a URL option overrides them. When a listed URL option is omitted, the table identifies the channel parameter supplying its default; reading a video-channel parameter requires Viewer privilege. For the documented fps option, 0 means the maximum available frame rate, and fractional values such as 25/2 are supported. ## What the source does not establish Do not infer actual delivered or recorded cadence from the requested value. Keep this request-precedence investigation separate from performance acceptance and storage budgeting. Confirm supported options for the specific stream path and device. Avoid importing a whole parameter table into a client without checking version-specific notes and product support. ## Applicability questions - Which exact consumer and video channel show the disputed behavior? - What complete sanitized options does that consumer actually request? - Which saved channel parameters supply defaults when those options are absent? - Is the proposed correction consumer-specific or intended to change the shared default? ## DSE recommendation: controlled next steps The following steps are DSE recommendations based on the cited source. DSE recommends resolving request-versus-default precedence before altering shared video-channel settings. - Choose one disputed setting, such as requested frame rate, and write down the intended consumer behavior. Capture the emitted request through an approved diagnostic method and read the matching channel default. Keep the channel identity explicit. Do not substitute a user-interface label for the actual request, and remove secrets before sharing URLs or diagnostic records. - Prepare two proposed test requests that differ only in the selected option: one omits it and one specifies a supported value. Keep the same device, channel and other relevant options. Compare the requests and resulting consumer observations. If testing fps, interpret 0 using the documented maximum-available meaning rather than calling it a disabled stream. Record a fractional request exactly instead of rounding its notation in the worksheet. - Decide where the approved change belongs. If only one client needs a different request, correct and verify that client’s template first. If the shared default should change, identify the other authorized consumers that need review, record the previous value and apply the supported update in a controlled window. Re-read the saved value and inspect the consumers’ actual requests afterward. ## Verification and evidence Retain the before-and-after channel value, paired request templates, client revision and observations tied to the same test interval. Have another reviewer identify which case used the default and which supplied an override. Record any unexplained result as a separate investigation rather than editing several image settings at once. For the final acceptance, measure the operational result through the relevant live or recorded workflow in addition to verifying the request. Preserve the distinction between configuration intent and measured behavior. These are proposed comparisons; no frame-rate measurement, performance threshold or successful client correction is asserted here. ## Official references - [Parameter management for video channels](https://developer.axis.com/vapix/network-video/parameter-management/image-api/) — Axis Communications; official VAPIX documentation. Source review completed October 29, 2026. Recheck the official documentation and the deployed device’s capabilities before changing production settings. ## Primary reference - Name: Axis Communications — Parameter management for video channels - Authority: Axis Communications - URL: https://developer.axis.com/vapix/network-video/parameter-management/image-api/ - Source publication date: Not stated by the source ## Citation and use Preferred citation: “Separate Axis stream request overrides from channel defaults,” DSE Security, https://update.dsesecurity.com/updates/separate-axis-stream-request-overrides-from-channel-defaults/ Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/ Usage and citation policy: https://update.dsesecurity.com/usage/ Copyright © 2026 Detection Systems & Engineering. All rights reserved.