{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/separate-axis-directional-audio-sensitivity-from-detection-timing/", "item": { "id": "https://update.dsesecurity.com/updates/separate-axis-directional-audio-sensitivity-from-detection-timing/", "slug": "separate-axis-directional-audio-sensitivity-from-detection-timing", "url": "https://update.dsesecurity.com/updates/separate-axis-directional-audio-sensitivity-from-detection-timing/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/separate-axis-directional-audio-sensitivity-from-detection-timing.md", "json": "https://update.dsesecurity.com/api/v1/posts/separate-axis-directional-audio-sensitivity-from-detection-timing/" }, "title": "Separate Axis directional audio sensitivity from detection timing", "summary": "Tune Axis directional-audio threshold and dwell separately. The documented dwell is time before another sound can be detected, not evidence that a sound persisted for that duration.", "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:50:00+00:00", "modified_at": "2026-10-29T19:50:08+00:00", "reviewed_on": "2026-10-29", "reading_minutes": 3, "word_count": 504, "potentially_affected": "Axis products exposing the documented Directional audio detection API interface; confirm actual device, hardware and software applicability before applying the proposed checks.", "dse_recommendation": "DSE recommends testing threshold selection and repeated-sound timing independently before enabling an operational response.", "primary_source": { "name": "Axis Communications — Directional audio detection API", "url": "https://developer.axis.com/vapix/device-configuration/directional-audio-detection-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 sensitivity and the interval before another detection as separate controls. Use an authorized two-sound exercise to examine repeat-detection behavior instead of assuming that dwell is a requirement for one sound to persist.

\n

Source fact: documented behavior

\n

Axis’s Directional audio detection API describes detectionThreshold as a sensitivity threshold in decibels.

\n

The dwellTime property is defined as the minimum number of seconds before detection of a new sound.

\n

The audioEvents entity provides up to 1,000 recent audio events, and its reported angles are relative to the detecting unit’s mechanical housing.

\n

What the source does not establish

\n

Do not treat the settings as a detection guarantee for every acoustic scene. Do not reinterpret the dwell definition as a confirmation period for sustained noise or as a geographic bearing. Confirm the exact device and interface support, and keep PTZ calibration and response behavior outside this sensitivity exercise.

\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 testing threshold selection and repeated-sound timing independently before enabling an operational response.

\n
    \n
  1. Record the actual configuration and the intended acoustic task with the responsible operator. Choose harmless permitted test sounds and an appropriate observation area. Keep any recording or personal-data question with the site owner; an event review need not become unrestricted audio capture. Define which observations will count as a detected event and which will remain unexplained.
    2. \n
  2. Use a proposed sensitivity comparison with the same approved sound and controlled conditions while changing only a supported threshold value. Retain the configured value and event observations for each case. Avoid copying the documentation’s sample value as a universal setting. Restore the approved value before moving to the separate timing exercise.
    3. \n
  3. For the timing case, plan two permitted sounds with documented spacing and repeat with another approved spacing around the intended dwell interval. Record the input times and resulting events without inventing an expected detection rate. Compare the outcome with the configured interval before another detection. Keep any PTZ movement or signaling action disabled or independently controlled during this exercise.
    4. \n
\n

Verification and evidence

\n

Retain device/software identity, settings, test-sound description, observation conditions and timestamped event results. Preserve the timing of both inputs even if only one event is observed. Ask a reviewer to distinguish sensitivity, repeat timing and any separate location or response requirement.

\n

Include a desk case in which an operator proposes increasing dwell to prove that a sound lasted longer. Require the reviewer to identify that unsupported interpretation before implementation. These are proposed checks; no sound test, detection performance or location accuracy has been measured for this article.

\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 sensitivity and the interval before another detection as separate controls. Use an authorized two-sound exercise to examine repeat-detection behavior instead of assuming that dwell is a requirement for one sound to persist.\nSource fact: documented behavior\nAxis’s Directional audio detection API describes detectionThreshold as a sensitivity threshold in decibels.\nThe dwellTime property is defined as the minimum number of seconds before detection of a new sound.\nThe audioEvents entity provides up to 1,000 recent audio events, and its reported angles are relative to the detecting unit’s mechanical housing.\nWhat the source does not establish\nDo not treat the settings as a detection guarantee for every acoustic scene. Do not reinterpret the dwell definition as a confirmation period for sustained noise or as a geographic bearing. Confirm the exact device and interface support, and keep PTZ calibration and response behavior outside this sensitivity exercise.\nApplicability questions\n\nWhich sounds should the authorized test distinguish from ordinary background activity?\nWhat threshold and dwell values are currently configured?\nHow closely spaced might relevant repeated sounds be?\nWho approves the acoustic test, observation location and handling of event data?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\nDSE recommends testing threshold selection and repeated-sound timing independently before enabling an operational response.\n\nRecord the actual configuration and the intended acoustic task with the responsible operator. Choose harmless permitted test sounds and an appropriate observation area. Keep any recording or personal-data question with the site owner; an event review need not become unrestricted audio capture. Define which observations will count as a detected event and which will remain unexplained.\nUse a proposed sensitivity comparison with the same approved sound and controlled conditions while changing only a supported threshold value. Retain the configured value and event observations for each case. Avoid copying the documentation’s sample value as a universal setting. Restore the approved value before moving to the separate timing exercise.\nFor the timing case, plan two permitted sounds with documented spacing and repeat with another approved spacing around the intended dwell interval. Record the input times and resulting events without inventing an expected detection rate. Compare the outcome with the configured interval before another detection. Keep any PTZ movement or signaling action disabled or independently controlled during this exercise.\n\nVerification and evidence\nRetain device/software identity, settings, test-sound description, observation conditions and timestamped event results. Preserve the timing of both inputs even if only one event is observed. Ask a reviewer to distinguish sensitivity, repeat timing and any separate location or response requirement.\nInclude a desk case in which an operator proposes increasing dwell to prove that a sound lasted longer. Require the reviewer to identify that unsupported interpretation before implementation. These are proposed checks; no sound test, detection performance or location accuracy has been measured for this article.\nOfficial references\n\nDirectional audio detection 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 sensitivity and the interval before another detection as separate controls. Use an authorized two-sound exercise to examine repeat-detection behavior instead of assuming that dwell is a requirement for one sound to persist.\n\n## Source fact: documented behavior\n\nAxis’s [Directional audio detection API](https://developer.axis.com/vapix/device-configuration/directional-audio-detection-api/) describes detectionThreshold as a sensitivity threshold in decibels.\n\nThe dwellTime property is defined as the minimum number of seconds before detection of a new sound.\n\nThe audioEvents entity provides up to 1,000 recent audio events, and its reported angles are relative to the detecting unit’s mechanical housing.\n\n## What the source does not establish\n\nDo not treat the settings as a detection guarantee for every acoustic scene. Do not reinterpret the dwell definition as a confirmation period for sustained noise or as a geographic bearing. Confirm the exact device and interface support, and keep PTZ calibration and response behavior outside this sensitivity exercise.\n\n## Applicability questions\n\n- Which sounds should the authorized test distinguish from ordinary background activity?\n\n- What threshold and dwell values are currently configured?\n\n- How closely spaced might relevant repeated sounds be?\n\n- Who approves the acoustic test, observation location and handling of event data?\n\n## DSE recommendation: controlled next steps\n\nThe following steps are DSE recommendations based on the cited source.\n\nDSE recommends testing threshold selection and repeated-sound timing independently before enabling an operational response.\n\n- Record the actual configuration and the intended acoustic task with the responsible operator. Choose harmless permitted test sounds and an appropriate observation area. Keep any recording or personal-data question with the site owner; an event review need not become unrestricted audio capture. Define which observations will count as a detected event and which will remain unexplained.\n\n- Use a proposed sensitivity comparison with the same approved sound and controlled conditions while changing only a supported threshold value. Retain the configured value and event observations for each case. Avoid copying the documentation’s sample value as a universal setting. Restore the approved value before moving to the separate timing exercise.\n\n- For the timing case, plan two permitted sounds with documented spacing and repeat with another approved spacing around the intended dwell interval. Record the input times and resulting events without inventing an expected detection rate. Compare the outcome with the configured interval before another detection. Keep any PTZ movement or signaling action disabled or independently controlled during this exercise.\n\n## Verification and evidence\n\nRetain device/software identity, settings, test-sound description, observation conditions and timestamped event results. Preserve the timing of both inputs even if only one event is observed. Ask a reviewer to distinguish sensitivity, repeat timing and any separate location or response requirement.\n\nInclude a desk case in which an operator proposes increasing dwell to prove that a sound lasted longer. Require the reviewer to identify that unsupported interpretation before implementation. These are proposed checks; no sound test, detection performance or location accuracy has been measured for this article.\n\n## Official references\n\n- [Directional audio detection API](https://developer.axis.com/vapix/device-configuration/directional-audio-detection-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/separate-axis-directional-audio-sensitivity-from-detection-timing/", "url": "https://update.dsesecurity.com/updates/separate-axis-directional-audio-sensitivity-from-detection-timing/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-10-29" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/separate-axis-directional-audio-sensitivity-from-detection-timing/#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": "Separate Axis directional audio sensitivity from detection timing", "item": "https://update.dsesecurity.com/updates/separate-axis-directional-audio-sensitivity-from-detection-timing/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/separate-axis-directional-audio-sensitivity-from-detection-timing/#article", "identifier": "https://update.dsesecurity.com/updates/separate-axis-directional-audio-sensitivity-from-detection-timing/", "url": "https://update.dsesecurity.com/updates/separate-axis-directional-audio-sensitivity-from-detection-timing/", "headline": "Separate Axis directional audio sensitivity from detection timing", "description": "Tune Axis directional-audio threshold and dwell separately. The documented dwell is time before another sound can be detected…", "abstract": "Tune Axis directional-audio threshold and dwell separately. The documented dwell is time before another sound can be detected, not evidence that a sound persisted for that duration.", "articleBody": "Bottom line: Review sensitivity and the interval before another detection as separate controls. Use an authorized two-sound exercise to examine repeat-detection behavior instead of assuming that dwell is a requirement for one sound to persist.\nSource fact: documented behavior\nAxis’s Directional audio detection API describes detectionThreshold as a sensitivity threshold in decibels.\nThe dwellTime property is defined as the minimum number of seconds before detection of a new sound.\nThe audioEvents entity provides up to 1,000 recent audio events, and its reported angles are relative to the detecting unit’s mechanical housing.\nWhat the source does not establish\nDo not treat the settings as a detection guarantee for every acoustic scene. Do not reinterpret the dwell definition as a confirmation period for sustained noise or as a geographic bearing. Confirm the exact device and interface support, and keep PTZ calibration and response behavior outside this sensitivity exercise.\nApplicability questions\n\nWhich sounds should the authorized test distinguish from ordinary background activity?\nWhat threshold and dwell values are currently configured?\nHow closely spaced might relevant repeated sounds be?\nWho approves the acoustic test, observation location and handling of event data?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\nDSE recommends testing threshold selection and repeated-sound timing independently before enabling an operational response.\n\nRecord the actual configuration and the intended acoustic task with the responsible operator. Choose harmless permitted test sounds and an appropriate observation area. Keep any recording or personal-data question with the site owner; an event review need not become unrestricted audio capture. Define which observations will count as a detected event and which will remain unexplained.\nUse a proposed sensitivity comparison with the same approved sound and controlled conditions while changing only a supported threshold value. Retain the configured value and event observations for each case. Avoid copying the documentation’s sample value as a universal setting. Restore the approved value before moving to the separate timing exercise.\nFor the timing case, plan two permitted sounds with documented spacing and repeat with another approved spacing around the intended dwell interval. Record the input times and resulting events without inventing an expected detection rate. Compare the outcome with the configured interval before another detection. Keep any PTZ movement or signaling action disabled or independently controlled during this exercise.\n\nVerification and evidence\nRetain device/software identity, settings, test-sound description, observation conditions and timestamped event results. Preserve the timing of both inputs even if only one event is observed. Ask a reviewer to distinguish sensitivity, repeat timing and any separate location or response requirement.\nInclude a desk case in which an operator proposes increasing dwell to prove that a sound lasted longer. Require the reviewer to identify that unsupported interpretation before implementation. These are proposed checks; no sound test, detection performance or location accuracy has been measured for this article.\nOfficial references\n\nDirectional audio detection 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:50:00+00:00", "dateModified": "2026-10-29T19:50:08+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/separate-axis-directional-audio-sensitivity-from-detection-timing/" }, "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/separate-axis-directional-audio-sensitivity-from-detection-timing/#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": "Separate Axis directional audio sensitivity from detection timing" }, "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": 504, "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 — Directional audio detection API", "url": "https://developer.axis.com/vapix/device-configuration/directional-audio-detection-api/" } } ] } }