# AVWatch inventory # ================= # One entry per device or piece of software you want watched. # # IMPORTANT: `installed:` is blank on every item below because only you know # what is actually running in your racks. Until you fill it in, AVWatch can # tell you what the newest version is but not whether you are behind. Fill it # in as you go with: # # python -m avwatch set-installed atem-constellation-4k 10.4 # # That command edits only the one line, so the comments in this file survive. # # Source kinds # ------------ # blackmagic Blackmagic's downloads JSON. Verified reliable, covers their # whole product line from one fetch. # github GitHub Releases. Verified reliable. # html Regex against a vendor page. Brittle by nature -- if one # starts erroring in the report, fix the `pattern` here. # websearch Claude looks the version up with web search and cites a # source. Used for the many vendors whose support sites are # JavaScript-rendered and cannot be scraped (verified on # 2026-09-08: Shure, Resolume, Focusrite, Teradek, Novastar, # Line 6 and Rational Acoustics all return no version text to # a scraper). Cached ~6 days, so the Monday digest pays for the # lookups and mid-week scans reuse them. # manual No automation at all; appears in a "check by hand" list. # # criticality: showstopper | high | normal | low # Drives how long a release must soak before it is recommended, and how # heavily community bug reports are weighted. Be honest here -- marking # everything showstopper makes the report useless. # # freeze: true Never recommend updating (locked show build, licence tied to # a version, known-good config you will not touch). defaults: criticality: normal items: # =========================================================================== # VIDEO -- switching, playback, conversion # =========================================================================== - id: atem-constellation-4k version_hint: >- Blackmagic ATEM Setup utility on the booth machine -- it lists every ATEM device it can see with its firmware version next to it. name: ATEM 4 M/E Constellation 4K Plus vendor: Blackmagic Design category: video criticality: showstopper installed: source: {kind: blackmagic, family: ATEM Switchers} check_url: https://www.blackmagicdesign.com/support/family/atem-live-production-switchers update_group: atem coupled_with: - {id: atem-2me-advanced-panel, relation: must_match, auto: true, note: "ATEM Setup flashes the panel in the same pass, so a divergence here means the panel update FAILED"} - {id: atem-software-control, relation: must_match, auto: true, note: "one Blackmagic download covers both"} risk_queries: - "ATEM Switchers firmware Constellation" - "panel offline after ATEM firmware update" - "Companion buttons dead after ATEM update" notes: >- Main service switcher. CONFIRMED BY THE USER: updating this also updates the 2 M/E panel -- they have never been done separately. Blackmagic's ATEM Setup flashes every connected ATEM device in one pass. So the panel and Software Control edges are marked auto: true, and AVWatch will NOT nag about doing them together. It will still shout if they ever diverge, because that would mean the panel did not take the update -- offline, or a failed flash -- which is worth knowing precisely because it should be impossible. The real hazard here is elsewhere: Blackmagic change the ATEM protocol between firmware trains, and the Bitfocus Companion module follows later. A switcher update can kill every Companion button while Companion itself reports perfectly current. Check your ATEM module before taking a new ATEM train. - id: atem-2me-advanced-panel version_hint: >- NOT on the panel's own menus -- those report the SWITCHER it is connected to, which is why they show the Constellation's version. Use Blackmagic ATEM Setup on the booth computer: the panel appears there as its own device, separate from the switcher, with its own software version on its tile. If that number is the same as the switcher's, that is correct and expected -- they are flashed together -- so just enter it. name: ATEM 2 M/E Advanced Panel 20 vendor: Blackmagic Design category: video criticality: showstopper installed: source: {kind: blackmagic, family: ATEM Switchers} check_url: https://www.blackmagicdesign.com/support/family/atem-live-production-switchers update_group: atem coupled_with: - {id: atem-constellation-4k, relation: must_match, auto: true} risk_queries: - "ATEM Advanced Panel firmware update problem" - "panel offline after ATEM update" - id: atem-software-control version_hint: >- Open ATEM Software Control, then About (Windows: Help menu). name: ATEM Software Control vendor: Blackmagic Design category: video criticality: high installed: source: {kind: blackmagic, family: ATEM Switchers} check_url: https://www.blackmagicdesign.com/support/family/atem-live-production-switchers update_group: atem coupled_with: - {id: atem-constellation-4k, relation: must_match, auto: true} risk_queries: ["ATEM Software Control update issue"] - id: hyperdeck-studio-4k-pro version_hint: >- HyperDeck front panel, or Blackmagic HyperDeck Setup utility. Also shown in the unit's web page if it is on the network. name: HyperDeck Studio 4K Pro vendor: Blackmagic Design category: video criticality: high installed: source: {kind: blackmagic, family: HyperDeck} check_url: https://www.blackmagicdesign.com/support/family/capture-and-playback risk_queries: ["HyperDeck Studio 4K Pro firmware problem"] notes: Service recording. A failed record is unrecoverable. - id: decklink-8k-pro-g2 version_hint: >- Blackmagic Desktop Video Setup on the machine the card is in. One driver version covers every DeckLink in that machine. name: DeckLink 8K Pro G2 vendor: Blackmagic Design category: video criticality: high installed: source: {kind: blackmagic, family: Desktop Video} check_url: https://www.blackmagicdesign.com/support/family/capture-and-playback risk_queries: ["Desktop Video update DeckLink problem"] notes: >- Desktop Video is a single driver package for every DeckLink in the machine, so this version applies host-wide, not per card. - id: decklink-mini-recorder-4k version_hint: >- Same Desktop Video Setup number as the other DeckLink cards in that machine. name: DeckLink Mini Recorder 4K vendor: Blackmagic Design category: video installed: source: {kind: blackmagic, family: Desktop Video} check_url: https://www.blackmagicdesign.com/support/family/capture-and-playback risk_queries: ["Desktop Video DeckLink Mini Recorder issue"] - id: bmd-multiview-4 version_hint: >- Blackmagic MultiView Setup utility over USB. name: Blackmagic MultiView 4 vendor: Blackmagic Design category: video installed: source: {kind: blackmagic, family: MultiView} check_url: https://www.blackmagicdesign.com/support/family/monitoring risk_queries: ["Blackmagic MultiView 4 firmware"] - id: bmd-2110-updowncross-12g version_hint: >- Blackmagic Converters Setup utility, with the unit plugged in over USB. name: Blackmagic 2110 IP UpDownCross 12G vendor: Blackmagic Design category: video criticality: high installed: source: {kind: blackmagic, family: Blackmagic Converters} check_url: https://www.blackmagicdesign.com/support/family/capture-and-playback risk_queries: ["Blackmagic 2110 IP converter firmware problem"] - id: bmd-sdi-to-hdmi-3g name: Mini Converter SDI to HDMI 3G vendor: Blackmagic Design category: video criticality: low installed: source: {kind: blackmagic, family: Blackmagic Converters} check_url: https://www.blackmagicdesign.com/support/family/capture-and-playback - id: bmd-micro-bidirect-12g name: Micro Converter BiDirectional SDI/HDMI 12G vendor: Blackmagic Design category: video criticality: low installed: source: {kind: blackmagic, family: Blackmagic Converters} check_url: https://www.blackmagicdesign.com/support/family/capture-and-playback - id: bmd-optical-fiber-12g name: Mini Converter Optical Fiber 12G vendor: Blackmagic Design category: video criticality: low installed: source: {kind: blackmagic, family: Blackmagic Converters} check_url: https://www.blackmagicdesign.com/support/family/capture-and-playback - id: bmd-micro-hdmi-to-sdi-3g name: Micro Converter HDMI to SDI 3G vendor: Blackmagic Design category: video criticality: low installed: source: {kind: blackmagic, family: Blackmagic Converters} check_url: https://www.blackmagicdesign.com/support/family/capture-and-playback - id: obs-studio version_hint: >- OBS: Help -> About. name: OBS Studio vendor: OBS Project category: video criticality: high installed: source: {kind: github, repo: obsproject/obs-studio} github_repo: obsproject/obs-studio check_url: https://obsproject.com/download risk_queries: ["OBS Studio update crash", "OBS Studio broken after update"] - id: propresenter version_hint: >- ProPresenter menu -> About ProPresenter (Mac: ProPresenter -> About). name: ProPresenter 7 vendor: Renewed Vision category: video criticality: showstopper installed: source: kind: html url: https://www.renewedvision.com/propresenter/download/ pattern: '\b(7\.\d+(?:\.\d+)?)\b' select: max strip_tags: true check_url: https://www.renewedvision.com/propresenter/download/ risk_queries: - "ProPresenter 7 update problem" - "ProPresenter crash after update" notes: >- Scraped from the download page; verified working. If this starts erroring, the page layout changed -- fix the pattern above. r/ProPresenter is unusually good at flagging bad releases early. - id: overflow-propresenter name: Overflow (ProPresenter integration) vendor: Overflow category: video installed: source: {kind: websearch, query: "Overflow app ProPresenter integration version release notes"} check_url: https://overflow.chat/ coupled_with: - {id: propresenter, relation: must_be_at_least, note: "must track the ProPresenter version to link and share libraries"} risk_queries: ["Overflow ProPresenter integration issue"] - id: bitfocus-companion version_hint: >- Open the Companion web page in a browser; the version is shown in the interface, usually bottom-left or under the Companion logo. name: Bitfocus Companion vendor: Bitfocus category: video criticality: high installed: source: {kind: github, repo: bitfocus/companion} github_repo: bitfocus/companion check_url: https://bitfocus.io/companion update_group: companion risk_queries: ["Bitfocus Companion update broke module"] notes: >- Major Companion versions change the module API; modules you rely on can lag a release behind. Check your specific modules before jumping. - id: companion-satellite version_hint: >- Companion Satellite tray icon -> About, or its own web page. Must match the Companion major version. name: Companion Satellite vendor: Bitfocus category: video installed: source: {kind: github, repo: bitfocus/companion-satellite} github_repo: bitfocus/companion-satellite check_url: https://github.com/bitfocus/companion-satellite/releases update_group: companion risk_queries: ["Companion Satellite connection issue"] notes: >- Satellite must be COMPATIBLE with the Companion major it connects to, but the two are numbered on separate tracks (Satellite 3.x pairs with Companion 4.x/5.x), so there is deliberately no must_match edge here -- comparing the numbers would raise a false mismatch on every scan. They share update_group "companion" so they are planned and updated together; check Bitfocus's compatibility note when either moves a major. - id: rustdesk name: RustDesk vendor: RustDesk category: video installed: source: {kind: github, repo: rustdesk/rustdesk} github_repo: rustdesk/rustdesk check_url: https://github.com/rustdesk/rustdesk/releases risk_queries: ["RustDesk update connection broken"] - id: resolume-arena version_hint: >- Resolume Arena: Help -> About. name: Resolume Arena vendor: Resolume category: video criticality: high installed: source: {kind: websearch, query: "Resolume Arena current version release notes download"} check_url: https://www.resolume.com/download/ risk_queries: ["Resolume Arena update crash", "Resolume Arena version problem"] notes: >- Their download page is JavaScript-rendered, so a scraper reads nothing from it -- hence the web lookup. - id: aja-og-dante-12gam version_hint: >- DashBoard: click the frame, then the OG-DANTE-12GAM card, and read its firmware version. Record the CARD firmware here, not the AJA software version -- AJA number those separately. name: AJA OG-DANTE-12GAM (openGear card) vendor: AJA Video Systems category: audio criticality: high installed: source: kind: websearch query: "AJA OG-DANTE-12GAM firmware version release notes" check_url: https://www.aja.com/family/software#opengear coupled_with: - {id: dante-controller, relation: must_be_at_least, note: "the card's Dante module is flashed by Dante Updater, which ships with Controller"} - {id: opengear-frame-controller, relation: host_of, significant: any, note: "the frame controller and DashBoard version gate what the card is offered"} risk_queries: - "AJA OG-DANTE-12GAM firmware problem" - "AJA Dante card audio dropout after update" - "openGear card firmware update DashBoard failed" notes: >- Confirmed by the user (part AJA-601388). openGear 12G-SDI / Dante 64-channel audio embedder-disembedder: dual 12G-SDI in and out, 32 channels embedded and 32 disembedded simultaneously. Also speaks AES67 and SMPTE ST 2110-30. THIS CARD HAS THREE SEPARATE VERSION DOMAINS, which is why it is worth watching closely: 1. AJA card firmware (currently v1.2.2) 2. AJA software / config utility (currently v1.2.9 -- AJA version these separately, so the two numbers never match) 3. The Dante module's own firmware, flashed by Dante Updater rather than by AJA, and therefore moving with the Dante network instead of with this card `installed:` should record the CARD FIRMWARE. Track the Dante module through dante-controller. It bridges SDI audio and the Dante network, so it sits in the service audio path in both directions. - id: opengear-frame version_hint: >- Same DashBoard status page as the controller. name: Ross oGx openGear frame (OGX-FR) vendor: Ross Video category: video criticality: high installed: source: kind: websearch query: "Ross Video OGX-FR oGx frame firmware version release notes" check_url: https://www.rossvideo.com/support/product-documentation/opengear/ risk_queries: - "OGX-FR frame firmware update problem" - "oGx frame cards offline DashBoard" notes: >- Identified from the user's "Ross high power" description: the oGx (OGX-FR) is Ross's high-power openGear frame, and "high power" is exactly what distinguishes it from the OG3-FR -- 23 W per slot against the OG3's 15 W, on a 600 W redundant supply. That headroom is what lets a frame run fully populated with 12G-SDI or IP cards like your OG-DANTE-12GAM. ONE THING TO CHECK: Ross document the oGx as a 2RU frame holding up to 20 openGear cards, but you described it as 22-slot. That may just be how it was sold to you, or it may mean a different frame. Worth a look at the front of the rack. It does not change the firmware either way, so nothing here is wrong because of it. Ross ship the frame in packages with different controllers (OGX-FR-C, OGX-FR-CN, OGX-FR-CNS) -- see opengear-frame-controller, which is the part that actually matters for updates. - id: opengear-frame-controller version_hint: >- Open DashBoard, click the frame in the tree on the left, and read the frame/controller software version on its status page. name: Ross MFC-OGX-N advanced openGear frame controller vendor: Ross Video category: video criticality: high installed: source: kind: websearch query: "Ross MFC-OGX-N openGear frame controller firmware version release notes" check_url: https://www.rossvideo.com/support/product-documentation/opengear/ coupled_with: - {id: aja-og-dante-12gam, relation: carries_firmware_for, note: "the controller is how every card in the frame gets flashed"} risk_queries: - "MFC-OGX-N firmware update problem" - "openGear frame controller update cards offline" notes: >- CONFIRMED: the frame's front screen shows an IP address, which means the networked (Advanced) controller is fitted rather than the basic one. That is the MFC-OGX-N. Older Ross documentation sometimes calls the same part MFC-8322-N, so either name may appear on a download page. WHAT THIS IS: the small control board inside the openGear frame that gives the frame its network connection. It is what lets the DashBoard software on a computer see the cards in the frame and change their settings. Not the AJA card, not the power supply -- the brain of the frame. WHY IT IS TRACKED SEPARATELY: it is also the thing that installs firmware onto every card in the frame. If it goes wrong you do not lose one card, you lose the ability to see or update any of them at once. Same shape of risk as the network switch, one layer down. TO READ THE CURRENT VERSION: open DashBoard, click the frame in the tree on the left, and look for the frame or controller software version on its status page. Record it with `avwatch set-installed opengear-frame-controller `. BECAUSE IT IS NETWORKED: it has a web interface and sits on the network, so it belongs on the production VLAN rather than a general one, and it should not be left on default credentials. Worth confirming whoever manages the network knows it is there. - id: teradek-bolt-6-xt-750 version_hint: >- Bolt Manager utility with the unit connected, or the unit's own display. TX and every RX must be identical. name: Teradek Bolt 6 XT 750 vendor: Teradek category: video criticality: high installed: source: {kind: websearch, query: "Teradek Bolt 6 XT firmware version download"} check_url: https://teradek.com/pages/downloads risk_queries: ["Teradek Bolt 6 firmware issue", "Teradek Bolt pairing problem"] - id: decimator-12g version_hint: >- Decimator's control application over USB, or the unit's front display menu. name: Decimator Design 12G-CROSS vendor: Decimator Design category: video criticality: high installed: source: {kind: websearch, query: "Decimator Design 12G-CROSS firmware current version"} check_url: https://decimator.com/DOWNLOADS/DOWNLOADS.html risk_queries: - "Decimator 12G-CROSS firmware update issue" - "Decimator firmware upload failed" notes: >- Narrowed from "12G decimators": the 12G-CROSS is the only 12G-SDI model Decimator make -- every DMON multiviewer and other mini-converter in their line tops out at 3G. If yours are actually 3G they are more likely MD-HX or MD-LX, so check the front panels. Note also that Decimator ship USB-Mini and USB-C hardware revisions of the 12G-CROSS and you need the matching cable to flash it. In-line format conversion: a mis-set or failed unit silently kills a camera, IMAG or projector feed mid-service. - id: resi-encoder-decoder version_hint: >- The Resi web console lists your encoders and their firmware. Note Resi push encoder firmware themselves, so this is for the record rather than something you install. name: Resi encoder / decoder vendor: Resi (Pushpay) category: video criticality: showstopper installed: source: {kind: websearch, query: "Resi encoder decoder firmware release notes"} check_url: https://resi.io/support/ risk_queries: ["Resi encoder problem", "Resi stream issue update"] notes: Streaming path for the service. Failure here is publicly visible. - id: novastar-vx1000 version_hint: >- VX1000 front panel menu, or NovaLCT once connected -- NovaLCT also shows the receiving-card versions, which have to match. name: NovaStar VX1000 vendor: NovaStar category: video criticality: showstopper installed: source: {kind: websearch, query: "NovaStar VX1000 firmware version download"} check_url: https://www.novastar.tech/downloads/ update_group: novastar coupled_with: - {id: novastar-pro-uhd-jr, relation: must_be_at_least} risk_queries: ["NovaStar VX1000 firmware problem", "NovaStar VX1000 update issue"] notes: >- LED wall controller. NovaStar firmware is version-coupled to receiving cards -- updating the controller alone can black the wall. Treat any update here as a scheduled project, never a quick job. - id: novastar-pro-uhd-jr version_hint: >- Front panel menu, or via NovaLCT / V-Can. name: NovaStar Pro UHD Jr vendor: NovaStar category: video criticality: high installed: source: {kind: websearch, query: "NovaStar Pro UHD Jr firmware version"} check_url: https://www.novastar.tech/downloads/ risk_queries: ["NovaStar UHD Jr firmware issue"] - id: tc-clarity-m name: TC Electronic Clarity M vendor: TC Electronic category: audio criticality: low installed: source: {kind: websearch, query: "TC Electronic Clarity M firmware version"} check_url: https://www.tcelectronic.com/ risk_queries: ["TC Electronic Clarity M firmware"] - id: tascam-da-6400 version_hint: >- DA-6400 front panel: Menu -> Utility -> Information. name: Tascam DA-6400 vendor: Tascam category: audio criticality: high installed: source: {kind: websearch, query: "Tascam DA-6400 firmware version download"} check_url: https://tascam.com/us/product/da-6400/download risk_queries: ["Tascam DA-6400 firmware problem"] notes: Multitrack service recording. A failed record cannot be redone. # =========================================================================== # LIGHTING / MEDIA CONTROL # =========================================================================== - id: vista-3 version_hint: >- Vista: Help -> About, or the splash screen on launch. name: Vista 3 vendor: Chroma-Q / Vista category: lighting criticality: high installed: source: {kind: websearch, query: "Vista 3 lighting software version release notes Chroma-Q"} check_url: https://www.vistabychromaq.com/ update_group: vista coupled_with: - {id: vista-m1, relation: must_match, note: "surface firmware ships with the console software release"} risk_queries: ["Vista 3 lighting software update problem"] - id: vista-m1 version_hint: >- Shown in Vista under the connected surface. Ships with the console software release, so it normally matches Vista 3. name: Vista M1 control surface vendor: Chroma-Q / Vista category: lighting criticality: high installed: source: {kind: websearch, query: "Vista M1 control surface firmware version"} check_url: https://www.vistabychromaq.com/ update_group: vista coupled_with: - {id: vista-3, relation: must_match} risk_queries: ["Vista M1 firmware issue"] notes: Surface firmware is normally tied to the Vista software version. # =========================================================================== # AUDIO -- consoles, interfaces, networking # =========================================================================== - id: x32-compact version_hint: >- X32 front panel: Setup, then the Global tab. The firmware version is printed on that screen. name: Behringer X32 Compact vendor: Behringer category: audio criticality: showstopper installed: source: {kind: websearch, query: "Behringer X32 firmware version current release"} check_url: https://www.behringer.com/product.html?modelCode=0603-AAF risk_queries: ["X32 firmware update problem", "Behringer X32 firmware bricked"] notes: >- X32 firmware is mature and rarely updated; the risk of touching it is usually higher than the benefit. Strong candidate for freeze: true. - id: wing-rack version_hint: >- WING: Setup -> System. Also shown on the boot screen. name: Behringer WING Rack vendor: Behringer category: audio criticality: showstopper installed: '3.1-0' source: {kind: websearch, query: "Behringer WING Rack firmware version release notes"} check_url: https://www.behringer.com/ update_group: wing coupled_with: - {id: wing-edit, relation: must_match, note: "WING Edit must match console firmware to connect"} risk_queries: - "Behringer WING firmware update problem" - "WING Rack firmware issue" notes: >- WING firmware moves faster than X32 and has had genuinely disruptive releases. Worth watching closely. - id: wing-edit version_hint: >- WING Edit: Help -> About, or the title bar. Must match the console. name: WING Edit vendor: Behringer category: audio installed: source: {kind: websearch, query: "Behringer WING Edit software version download"} check_url: https://www.behringer.com/ update_group: wing coupled_with: - {id: wing-rack, relation: must_match} risk_queries: ["WING Edit version compatibility"] notes: WING Edit must match the console firmware version to connect. - id: dp48 name: Behringer P16 / DP48 personal monitor mixers vendor: Behringer category: audio criticality: low installed: source: {kind: websearch, query: "Behringer DP48 personal monitor mixer firmware version"} check_url: https://www.behringer.com/ risk_queries: ["Behringer DP48 firmware"] - id: quantum-225 version_hint: >- On the console: Setup or Diagnostics, then the system/software information page. DiGiCo show it as a Stealth Core software version. name: DiGiCo Quantum 225 vendor: DiGiCo category: audio criticality: showstopper installed: '22.0.2242' source: {kind: websearch, query: "DiGiCo Quantum 225 console software version release notes"} check_url: https://digico.biz/digico-support/ update_group: digico risk_queries: - "DiGiCo Quantum 225 software update problem" - "DiGiCo Stealth Core update issue" notes: >- Confirmed by the user as the main console. DiGiCo console software and DQ Rack firmware are a matched set -- updating the console without the racks can drop I/O entirely. Treat any update as a scheduled project with both halves done together, and never mid-week. - id: dq-rack version_hint: >- Shown on the console's rack or I/O setup page, next to the rack itself -- not on the rack's own front panel. name: DiGiCo DQ Rack vendor: DiGiCo category: audio criticality: showstopper installed: '1.11' source: {kind: websearch, query: "DiGiCo DQ Rack firmware version release notes"} check_url: https://digico.biz/digico-support/ update_group: digico notes: >- Confirmed by the user. All console I/O passes through here, so a failed firmware update takes every input and output with it. Rack firmware and console software are numbered SEPARATELY -- the user reports the rack on 1.11 while the console reports Stealth Core 22.0.2242. So there is deliberately no must_match edge: comparing those numbers would raise a false mismatch on every scan. They share update_group "digico" instead, because DiGiCo ship them as one package and they must be flashed in the same session even though the numbers never match. risk_queries: - "DiGiCo DQ Rack firmware problem" - "DiGiCo rack update I/O offline" notes: >- Confirmed by the user. All console I/O passes through here, so a failed firmware update takes every input and output with it. Version-coupled to the Quantum 225 -- see that entry. - id: dbox-plus name: Dangerous Music D-Box+ vendor: Dangerous Music category: audio criticality: low installed: source: kind: manual note: >- Summing mixer and monitor controller. No field-updatable firmware, so there is nothing for AVWatch to track. check_url: https://www.dangerousmusic.com/product/d-box-plus/ notes: >- Confirmed by the user. Listed for completeness only -- monitor controller in the Pro Tools path with no software to update. - id: dante-controller version_hint: >- Dante Controller: Help -> About. You have this on several Macs, so record the version from whichever machine you would actually use to CHANGE routing or push device firmware -- that is the one that matters. For the DEVICE firmware on each Dante box, use the Device Info tab, which lists them all in one view. name: Dante Controller vendor: Audinate category: network criticality: high installed: source: {kind: websearch, query: "Audinate Dante Controller current version release notes"} check_url: https://www.audinate.com/products/software/dante-controller risk_queries: - "Dante Controller update problem" - "Dante firmware update device offline" notes: >- Installed on several Macs for viewing, confirmed by the user. That is why this is NOT marked showstopper: Dante routing is stored in the devices themselves, so Controller closing or crashing does not stop audio. What you lose is the ability to see and change routing. It is deliberately not coupled to any one machine either, since it lives on several. If those installs drift onto different versions that is normally harmless for viewing -- but the machine you push firmware from should be the newest, because Dante Updater ships with Controller and its version gates which device firmware you are offered. Updating Controller itself is low risk. Updating device firmware across the network is not: do it one device at a time, with a written record of what was on what beforehand. - id: netgear-dante-switch version_hint: >- Switch web interface -> System -> Firmware (or the front LCD cycles through it). Currently on the 13.0.5.x train if it is up to date. name: NETGEAR M4250-26G4XF-PoE+ (AV Line) vendor: NETGEAR category: network criticality: showstopper installed: source: kind: websearch query: "NETGEAR M4250 GSM4230PX firmware version 13.0.5 release notes" check_url: https://www.netgear.com/support/product/gsm4230px coupled_with: - {id: dante-controller, relation: host_of, significant: any, note: "the entire Dante network rides on this switch"} - {id: dq-rack, relation: host_of, significant: any, note: "all console stage I/O crosses this switch"} - {id: focusrite-rednet-tnx, relation: host_of, significant: any} - {id: aja-og-dante-12gam, relation: host_of, significant: any} risk_queries: - "M4250 firmware update Dante network loop" - "Netgear M4250 13.0.5 upgrade problem" - "M4250 PTP clock drift AVB" notes: >- Confirmed by the user as M4250-26G4XF-PoE+, 30 W per port. NETGEAR's model code for this is GSM4230PX; one firmware image covers the whole M4250 PoE family (GSM4230P / PX / UP and GSM4248P / PX / UX), so the exact variant does not change which file applies. THE HIGHEST-CONSEQUENCE UPDATE IN THE FLEET. Bad switch firmware does not degrade the audio network, it removes it -- every Dante device at once, including the DQ Rack carrying all stage I/O. Verified hazards in the current 13.0.5.x train (NETGEAR's own release notes, checked 2026-09-09, latest 13.0.5.26 of 29 Apr 2026): * Dante redundancy ports: upgrading from AVUI 2.2.13.29 can leave access ports with spanning-tree disabled, and NETGEAR warn this "can cause a network loop" where Dante redundancy is wired. A loop takes the network down hard. * SNTP was removed at 13.0.5.10 in favour of NTP. Strip SNTP settings out of any 13.0.4.x config BEFORE importing it onto 13.0.5.x. * Importing an older config silently enables HTTPS, changing how you reach the web UI. * If the switch becomes gPTP clock master, time drift occurs with AVB MILAN devices. Workaround is Local Clock Priority 255. No intermediate firmware version is required to reach 13.0.5.26. Because NETGEAR put all of that in the third version digit, every coupling here uses significant: any -- a "patch" from this vendor is not a patch. Export the running config and record the PoE budget per port before touching it. Schedule with IT, never during a service week. - id: focusrite-rednet-tnx version_hint: >- RedNet Control on the connected machine -- it lists the TNX with its firmware version. name: Focusrite RedNet TNX vendor: Focusrite category: audio criticality: high installed: source: {kind: websearch, query: "Focusrite RedNet TNX Thunderbolt Dante interface firmware version"} check_url: https://downloads.focusrite.com/focusrite/rednet-tnx coupled_with: - {id: rednet-control, relation: must_be_at_least, note: "RedNet Control is the carrier and must be at or above the device"} - {id: dante-controller, relation: must_be_at_least} risk_queries: - "RedNet TNX firmware problem" - "RedNet TNX Dante dropout update" notes: >- Confirmed by photo: the Thunderbolt-to-Dante desktop interface, not the PCIeNX card. This is the Dante bridge for the DAW machine, so it sits in the recording and playback path. Its firmware, RedNet Control and the Dante firmware on the device are three separate versions that need to stay compatible -- check RedNet Control's release notes for the pairing before updating any of them. - id: rednet-control version_hint: >- RedNet Control: Help -> About. Update this before the TNX itself. name: Focusrite RedNet Control vendor: Focusrite category: audio criticality: high installed: source: {kind: websearch, query: "Focusrite RedNet Control current version release notes"} check_url: https://downloads.focusrite.com/focusrite coupled_with: - {id: focusrite-rednet-tnx, relation: carries_firmware_for} risk_queries: ["RedNet Control update issue", "RedNet Control cannot see device"] notes: >- The application that configures the RedNet TNX and pushes its firmware. Update this first, then the device -- doing it the other way round is how you end up with a device the software will not talk to. - id: scarlett-18i20 version_hint: >- Focusrite Control -> Device Settings, or the Focusrite Control About window. name: Focusrite Scarlett 18i20 vendor: Focusrite category: audio installed: source: {kind: websearch, query: "Focusrite Scarlett 18i20 firmware Focusrite Control version"} check_url: https://downloads.focusrite.com/focusrite risk_queries: ["Scarlett 18i20 firmware update problem"] - id: pro-tools version_hint: >- Pro Tools: About Pro Tools (Mac: Pro Tools menu; Windows: Help). name: Pro Tools vendor: Avid category: audio criticality: showstopper installed: source: {kind: websearch, query: "Avid Pro Tools current version release notes"} check_url: https://www.avid.com/pro-tools coupled_with: - {id: waves-plugins, relation: host_of} - {id: uad, relation: host_of} - {id: plugin-alliance, relation: host_of} - {id: autotune-artist, relation: host_of} - {id: slate-digital, relation: host_of} - {id: ilok-license-manager, relation: must_be_at_least} - {id: avid-eucon, relation: must_match} risk_queries: - "Pro Tools update problem plugin" - "Pro Tools version crash" notes: >- Pro Tools updates routinely break third-party plugin compatibility. Given the plugin count in this fleet, treat every Pro Tools update as a plugin compatibility project, not a standalone install. - id: avid-s1 version_hint: >- Shown in EuControl Settings under the surface, or on the S1 itself. name: Avid S1 control surface vendor: Avid category: audio criticality: high installed: source: {kind: websearch, query: "Avid S1 control surface firmware version"} check_url: https://www.avid.com/support coupled_with: - {id: avid-eucon, relation: must_be_at_least} risk_queries: ["Avid S1 firmware issue"] - id: avid-eucon version_hint: >- EuControl: the EuControl Settings window shows its version. Must satisfy both the S1 and Pro Tools. name: Avid EUCON vendor: Avid category: audio criticality: high installed: source: {kind: websearch, query: "Avid EUCON software version release notes"} check_url: https://www.avid.com/support risk_queries: ["Avid EUCON update problem"] notes: EUCON version must match what the S1 and Pro Tools expect. - id: waves-superrack version_hint: >- SuperRack: the About window, or the title bar. name: Waves SuperRack vendor: Waves category: audio criticality: showstopper installed: source: {kind: websearch, query: "Waves SuperRack current version release notes"} check_url: https://www.waves.com/downloads update_group: soundgrid coupled_with: - {id: waves-livebox, relation: must_match, note: "SoundGrid needs driver, server and host on the same version"} - {id: waves-plugins, relation: host_of} risk_queries: ["Waves SuperRack problem update", "SuperRack crash"] notes: Live plugin host. If this stops, the mix stops. - id: waves-livebox version_hint: >- Waves SoundGrid Studio / SuperRack shows the LiveBox firmware once it is connected. name: Waves LiveBox (SoundGrid server running SuperRack) vendor: Waves category: audio criticality: showstopper installed: source: {kind: websearch, query: "Waves LiveBox firmware version"} check_url: https://www.waves.com/downloads update_group: soundgrid coupled_with: - {id: waves-superrack, relation: must_match} - {id: waves-superrack, relation: host_of, significant: any, note: "SuperRack runs ON this LiveBox -- confirmed by the user, so any LiveBox change is a platform change under it"} risk_queries: - "Waves LiveBox firmware issue" - "SuperRack LiveBox version mismatch won't connect" notes: >- Confirmed by the user: SuperRack runs ON this box, so it is not a peripheral -- it is the machine the live plugin rack lives on. Raised to showstopper for that reason; a host cannot be less critical than the thing it hosts, and if this stops, the mix stops. SoundGrid wants driver, server and host on the same version, so treat this and SuperRack as one update, never one at a time. - id: waves-plugins version_hint: >- Waves Central -> installed products. This is the plugin bundle version (e.g. V15), not SuperRack's. name: Waves plugins vendor: Waves category: plugin criticality: high installed: source: {kind: websearch, query: "Waves plugins current version V15 release notes"} check_url: https://www.waves.com/downloads risk_queries: ["Waves plugin update broke", "Waves V15 problem"] notes: >- Waves version changes have historically broken sessions and licences. Check SuperRack compatibility before updating plugins. # =========================================================================== # AUDIO -- amplification and processing # =========================================================================== - id: dbx-venu360 version_hint: >- VENU360 front panel: Utility -> System Info, or the DriveRack control app. BACK UP THE PRESETS before ever updating this -- it holds the house tuning. name: dbx DriveRack VENU360 vendor: dbx category: audio criticality: showstopper installed: source: {kind: websearch, query: "dbx DriveRack VENU360 firmware version download"} check_url: https://dbxpro.com/en/products/driverack-venu360 risk_queries: ["DriveRack VENU360 firmware problem"] notes: >- Holds the house tuning. Back up every preset before any firmware update -- a reset here means re-tuning the room. - id: crown-xli-3500 name: Crown XLi 3500 vendor: Crown / HARMAN category: audio criticality: low installed: source: {kind: manual, note: "XLi series is analogue with no user-updatable firmware."} check_url: https://www.crownaudio.com/en/products/xli-3500 notes: >- Listed for completeness. The XLi series has no network control and no field-updatable firmware, so there is nothing to watch. - id: crown-xti-4002 version_hint: >- HiQnet System Architect over USB. name: Crown XTi 4002 vendor: Crown / HARMAN category: audio criticality: normal installed: source: {kind: websearch, query: "Crown XTi 2 series firmware HiQnet System Architect version"} check_url: https://www.crownaudio.com/en/products/xti-4002 risk_queries: ["Crown XTi firmware update"] - id: crown-itech-9000 version_hint: >- HiQnet Audio Architect / System Architect, with the amp online. name: Crown I-Tech 9000 (OmniDrive) vendor: Crown / HARMAN category: audio criticality: showstopper installed: source: {kind: websearch, query: "Crown I-Tech HD OmniDrive firmware version System Architect"} check_url: https://www.crownaudio.com/ risk_queries: ["Crown I-Tech firmware update problem"] notes: Main system amplification. Carries DSP presets -- back them up first. - id: crown-dci-8-300n version_hint: >- HiQnet Audio Architect, with the amp online. name: Crown DCi 8|300N vendor: Crown / HARMAN category: audio criticality: high installed: source: {kind: websearch, query: "Crown DCi Network series firmware version Audio Architect"} check_url: https://www.crownaudio.com/ risk_queries: ["Crown DCi network firmware problem"] notes: DCi N models update through HiQnet Audio Architect. - id: crown-dci-4-600n version_hint: >- HiQnet Audio Architect, with the amp online. name: Crown DCi 4|600N vendor: Crown / HARMAN category: audio criticality: high installed: source: {kind: websearch, query: "Crown DCi Network series firmware version Audio Architect"} check_url: https://www.crownaudio.com/ risk_queries: ["Crown DCi network firmware problem"] - id: galaxy-nspa name: Galaxy Audio NSPA powered Nano Spot vendor: Galaxy Audio category: audio criticality: low installed: source: {kind: manual, note: "Powered speaker with no field-updatable firmware."} check_url: https://www.galaxyaudio.com/ - id: smaart-suite version_hint: >- Smaart: Help -> About. name: Smaart Suite vendor: Rational Acoustics category: audio installed: source: {kind: websearch, query: "Rational Acoustics Smaart Suite current version release notes"} check_url: https://www.rationalacoustics.com/ risk_queries: ["Smaart Suite update problem"] notes: Measurement tool -- update freely, it is not in the show path. # =========================================================================== # RF -- wireless mics and IEM # =========================================================================== - id: shure-ad4q version_hint: >- AD4Q front panel: Menu -> Device Info (or Utilities -> Device Info). Alternatively Wireless Workbench shows firmware for every device it can see, which is the faster way to do the whole RF fleet at once. name: Shure Axient Digital AD4Q receiver vendor: Shure category: rf criticality: showstopper installed: source: {kind: websearch, query: "Shure Axient Digital AD4Q firmware current version"} check_url: https://www.shure.com/en-US/support/downloads update_group: shure-axient coupled_with: - {id: shure-ad1, relation: must_match, note: "TX and RX firmware must match exactly or they will not link"} - {id: shure-ad2, relation: must_match} - {id: wireless-workbench, relation: must_be_at_least} risk_queries: - "Shure Axient Digital firmware problem" - "Shure AD4Q firmware update issue" notes: >- Axient firmware must match across receivers and transmitters -- a mismatched pair will not link. Update the whole RF system together, never piecemeal, and never on a Saturday. - id: shure-ad2 version_hint: >- Wireless Workbench, or the handheld's own menu -> Device Info. Must match the AD4Q. name: Shure Axient AD2 handheld transmitter vendor: Shure category: rf criticality: showstopper installed: source: {kind: websearch, query: "Shure Axient Digital AD2 transmitter firmware version"} check_url: https://www.shure.com/en-US/support/downloads update_group: shure-axient coupled_with: - {id: shure-ad4q, relation: must_match} risk_queries: ["Shure AD2 transmitter firmware issue"] - id: shure-ad1 version_hint: >- Fastest route: Wireless Workbench, which lists transmitter firmware. On the pack itself: Menu -> Device Info. Must match the AD4Q. name: Shure Axient AD1 bodypack transmitter vendor: Shure category: rf criticality: showstopper installed: source: {kind: websearch, query: "Shure Axient Digital AD1 transmitter firmware version"} check_url: https://www.shure.com/en-US/support/downloads update_group: shure-axient coupled_with: - {id: shure-ad4q, relation: must_match} risk_queries: ["Shure AD1 transmitter firmware issue"] - id: shure-psm900-p9t version_hint: >- P9T front panel menu -> Utilities, or the Shure Update Utility with it connected. name: Shure PSM900 P9T transmitter vendor: Shure category: rf criticality: high installed: source: {kind: websearch, query: "Shure PSM900 P9T firmware version"} check_url: https://www.shure.com/en-US/support/downloads risk_queries: ["Shure PSM900 firmware"] - id: shure-psm1000-p10t version_hint: >- P10T front panel menu -> Utilities, or Wireless Workbench. name: Shure PSM1000 P10T transmitter vendor: Shure category: rf criticality: high installed: source: {kind: websearch, query: "Shure PSM1000 P10T firmware version"} check_url: https://www.shure.com/en-US/support/downloads coupled_with: - {id: wireless-workbench, relation: must_be_at_least} risk_queries: ["Shure PSM1000 firmware issue"] - id: shure-ulxd4 version_hint: >- ULXD4 front panel: Menu -> Utilities -> Device Info, or Wireless Workbench. name: Shure ULXD4 receiver vendor: Shure category: rf criticality: high installed: source: {kind: websearch, query: "Shure ULX-D ULXD4 firmware current version"} check_url: https://www.shure.com/en-US/support/downloads coupled_with: - {id: wireless-workbench, relation: must_be_at_least} risk_queries: ["Shure ULXD firmware update problem"] - id: shure-qlxd4 version_hint: >- QLXD4 front panel: Menu -> Utilities -> Device Info. Or Wireless Workbench. name: Shure QLXD4 receiver vendor: Shure category: rf criticality: high installed: source: {kind: websearch, query: "Shure QLX-D QLXD4 firmware current version"} check_url: https://www.shure.com/en-US/support/downloads update_group: shure-qlxd coupled_with: - {id: shure-qlxd1, relation: must_match} - {id: wireless-workbench, relation: must_be_at_least} risk_queries: ["Shure QLXD firmware update problem"] - id: shure-qlxd1 version_hint: >- Wireless Workbench, or the pack's menu -> Device Info. Must match the QLXD4. name: Shure QLXD1 bodypack transmitter vendor: Shure category: rf criticality: high installed: source: {kind: websearch, query: "Shure QLX-D QLXD1 transmitter firmware version"} check_url: https://www.shure.com/en-US/support/downloads update_group: shure-qlxd coupled_with: - {id: shure-qlxd4, relation: must_match} risk_queries: ["Shure QLXD1 firmware"] - id: wireless-workbench version_hint: >- Wireless Workbench: Help -> About. Update this BEFORE any Shure device firmware, since it is what pushes them. name: Shure Wireless Workbench vendor: Shure category: rf criticality: high installed: source: {kind: websearch, query: "Shure Wireless Workbench 6 current version download"} check_url: https://www.shure.com/en-US/products/software/wireless_workbench coupled_with: - {id: shure-ad4q, relation: carries_firmware_for} - {id: shure-qlxd4, relation: carries_firmware_for} - {id: shure-ulxd4, relation: carries_firmware_for} risk_queries: ["Wireless Workbench update problem"] notes: >- WWB is also how you push device firmware, so its version and the device firmware versions are linked. Update WWB first. - id: rf-venue-combine8 name: RF Venue COMBINE8 vendor: RF Venue category: rf criticality: high installed: source: {kind: websearch, query: "RF Venue COMBINE8 firmware version"} check_url: https://www.rfvenue.com/support risk_queries: ["RF Venue COMBINE8 issue"] - id: rf-venue-distro9 name: RF Venue DISTRO9 HDR vendor: RF Venue category: rf criticality: high installed: source: {kind: websearch, query: "RF Venue DISTRO9 HDR firmware version"} check_url: https://www.rfvenue.com/support risk_queries: ["RF Venue DISTRO9 issue"] # =========================================================================== # KEYBOARDS / INSTRUMENTS # =========================================================================== - id: nord-stage-3 version_hint: >- Hold Shift + press Sound Menu (or power on and read the display -- the OS version shows briefly at startup). name: Nord Stage 3 vendor: Clavia Nord category: audio criticality: high installed: source: {kind: websearch, query: "Nord Stage 3 OS firmware current version"} check_url: https://www.nordkeyboards.com/downloads risk_queries: ["Nord Stage 3 OS update problem"] - id: nord-electro-6d version_hint: >- Same as the Stage 3: the OS version appears on the display at power-on. name: Nord Electro 6D vendor: Clavia Nord category: audio criticality: high installed: source: {kind: websearch, query: "Nord Electro 6 OS firmware current version"} check_url: https://www.nordkeyboards.com/downloads risk_queries: ["Nord Electro 6 OS update issue"] - id: helix-lt version_hint: >- Helix LT: hold the knob under 'Global Settings', or check HX Edit which shows device firmware. name: Line 6 Helix LT vendor: Line 6 category: audio criticality: high installed: source: {kind: websearch, query: "Line 6 Helix firmware current version release notes"} check_url: https://line6.com/software/ risk_queries: ["Line 6 Helix firmware update problem", "Helix update lost presets"] notes: >- Helix major firmware updates can require a preset rebuild. Back up the setlist first. # =========================================================================== # PLUGINS -- lower stakes individually, but they break Pro Tools sessions # =========================================================================== - id: uad name: Universal Audio UAD vendor: Universal Audio category: plugin criticality: high installed: source: {kind: websearch, query: "Universal Audio UAD software current version release notes"} check_url: https://www.uaudio.com/support risk_queries: ["UAD update problem", "UAD plugin not authorized after update"] - id: plugin-alliance name: Plugin Alliance vendor: Plugin Alliance category: plugin installed: source: {kind: websearch, query: "Plugin Alliance installer current version"} check_url: https://www.plugin-alliance.com/ risk_queries: ["Plugin Alliance update issue"] - id: valhalla name: Valhalla DSP vendor: Valhalla DSP category: plugin criticality: low installed: source: {kind: websearch, query: "Valhalla DSP plugin current versions"} check_url: https://valhalladsp.com/ risk_queries: ["Valhalla DSP update issue"] - id: soundtoys name: Soundtoys vendor: Soundtoys category: plugin installed: source: {kind: websearch, query: "Soundtoys 5 current version release notes"} check_url: https://www.soundtoys.com/ risk_queries: ["Soundtoys update problem"] - id: izotope name: iZotope vendor: iZotope / Native Instruments category: plugin installed: source: {kind: websearch, query: "iZotope RX Ozone current version release notes"} check_url: https://www.izotope.com/ risk_queries: ["iZotope update problem"] - id: arturia name: Arturia vendor: Arturia category: plugin installed: source: {kind: websearch, query: "Arturia Analog Lab V Collection current version"} check_url: https://www.arturia.com/support risk_queries: ["Arturia update issue"] - id: omnisphere-3 name: Omnisphere 3 vendor: Spectrasonics category: plugin criticality: high installed: source: {kind: websearch, query: "Spectrasonics Omnisphere current version update"} check_url: https://www.spectrasonics.net/support/updates.php risk_queries: ["Omnisphere update problem", "Omnisphere 3 issue"] - id: autotune-artist name: Antares Auto-Tune Artist vendor: Antares category: plugin criticality: high installed: source: {kind: websearch, query: "Antares Auto-Tune Artist current version release notes"} check_url: https://www.antarestech.com/ risk_queries: ["Auto-Tune Artist update problem", "Auto-Tune crash"] notes: Live vocal path -- a crash here is audible to the whole room. - id: fabfilter name: FabFilter vendor: FabFilter category: plugin installed: source: {kind: websearch, query: "FabFilter plugins current version release notes"} check_url: https://www.fabfilter.com/ risk_queries: ["FabFilter update issue"] - id: soundtheory name: Soundtheory Gullfoss vendor: Soundtheory category: plugin installed: source: {kind: websearch, query: "Soundtheory Gullfoss current version"} check_url: https://www.soundtheory.com/ risk_queries: ["Gullfoss update issue"] - id: wavesfactory name: Wavesfactory vendor: Wavesfactory category: plugin criticality: low installed: source: {kind: websearch, query: "Wavesfactory plugins current version"} check_url: https://www.wavesfactory.com/ risk_queries: ["Wavesfactory update issue"] - id: slate-digital name: Slate Digital vendor: Slate Digital category: plugin installed: source: {kind: websearch, query: "Slate Digital All Access Pass plugins current version"} check_url: https://slatedigital.com/ risk_queries: ["Slate Digital update problem"] - id: slate-trigger-2 name: Steven Slate Trigger 2 vendor: Slate Digital category: plugin installed: source: {kind: websearch, query: "Steven Slate Trigger 2 current version"} check_url: https://slatedigital.com/ risk_queries: ["Slate Trigger 2 update issue"] - id: ilok-license-manager version_hint: >- iLok License Manager: About. If this breaks, every licensed plugin stops at once, which is why it is marked showstopper. name: iLok License Manager vendor: PACE category: plugin criticality: showstopper installed: source: {kind: websearch, query: "PACE iLok License Manager current version"} check_url: https://www.ilok.com/ risk_queries: ["iLok License Manager problem", "iLok update licenses missing"] notes: >- Marked showstopper because when iLok breaks, every licensed plugin stops at once. Historically one of the most disruptive things in this list. # =========================================================================== # OPERATING SYSTEMS # =========================================================================== # Two physically separate Macs, confirmed by the user: one runs # ProPresenter, one runs Pro Tools. They will drift onto different macOS # versions and they have completely different compatibility constraints, so # a single "macOS" row could not represent either of them honestly. # # If you have more machines than this -- a SuperRack machine, a spare, a # streaming Mac -- copy one of these blocks, give it a new id, and point its # host_of edges at whatever that machine actually runs. - id: macos-propresenter version_hint: >- On the PRESENTATION Mac (the one running ProPresenter): Apple menu -> About This Mac. name: macOS - presentation Mac (ProPresenter) vendor: Apple category: os criticality: showstopper installed: source: {kind: websearch, query: "macOS latest version release date current"} check_url: https://support.apple.com/en-us/HT201222 coupled_with: - {id: propresenter, relation: host_of, note: "confirm Renewed Vision support the new macOS before taking it"} - {id: overflow-propresenter, relation: host_of} risk_queries: - "macOS update ProPresenter broken" - "ProPresenter macOS compatibility" notes: >- The presentation machine. Renewed Vision publish which macOS versions each ProPresenter release supports -- check that before any macOS upgrade, not after. Hold major versions for months, not weeks. If this machine also drives a Blackmagic capture card or NDI, its Desktop Video / NDI runtime versions are gated by the macOS version too. - id: macos-protools version_hint: >- On the AUDIO Mac (the one running Pro Tools): Apple menu -> About This Mac. name: macOS - audio Mac (Pro Tools) vendor: Apple category: os criticality: showstopper installed: source: {kind: websearch, query: "macOS latest version release date current"} check_url: https://support.apple.com/en-us/HT201222 coupled_with: - {id: pro-tools, relation: host_of, note: "Avid publish a supported-macOS list per Pro Tools release"} - {id: ilok-license-manager, relation: host_of, note: "a macOS major can block the PACE extension and deauthorise every AAX plugin at once"} risk_queries: - "macOS update Pro Tools compatibility" - "macOS update audio interface broken" - "macOS update iLok not authorized" notes: >- The single most common cause of a broken production Mac, and the widest coupled change in the whole fleet: an OS major moves the ground under Pro Tools, every AAX plugin, the iLok system extension, and any Dante or RedNet driver on the machine at once. Never take a major macOS release before Avid, Waves, Audinate and Focusrite have ALL published compatibility. That is usually months after Apple ship it. Confirmed by the user: SuperRack does NOT run on this Mac (it runs on the LiveBox), and Dante Controller is installed on several Macs for viewing. Neither is coupled to this machine. - id: windows-booth version_hint: >- Press Win+R, type winver, press Enter. name: Windows (booth and video machines) vendor: Microsoft category: os criticality: high installed: source: {kind: websearch, query: "Windows 11 current version build release health"} check_url: https://learn.microsoft.com/en-us/windows/release-health/windows11-release-information coupled_with: - {id: obs-studio, relation: host_of} - {id: resolume-arena, relation: host_of} - {id: bitfocus-companion, relation: host_of} risk_queries: - "Windows update broke audio driver" - "Windows 11 update NDI OBS problem" notes: >- Set these machines to defer feature updates. Security patches are worth taking promptly; feature updates are not.