ThePulse
AV-over-IP · Networks · Broadcast
// about

Signal, packets, and the craft of AV

A working knowledge base and learning journal for AV-over-IP and network engineering.

What this is

ThePulse is where AV meets IT. It covers the messy, version-specific, multi-vendor reality of getting audio and video reliably across a network — Dante, AES67, Q-SYS, NDI, SDVoE, DM NVX and ST 2110 — and the network engineering underneath that actually makes them work: multicast, IGMP snooping, QoS, VLAN segmentation, and PTP clocking.

It is written in the open, partly as a reference and partly as a learning journal. Some posts are field-tested playbooks; others are notes worked out while wiring up a lab, breaking something, and figuring out why. The mistakes are left in on purpose, because that is usually where the useful part is.

Why AV-over-IP, why now

Point-to-point AV is over. The industry has consolidated around IP as the transport layer for both commercial AV and broadcast, and enterprise IT teams are now in the room for AV decisions they never used to touch. That convergence created a real skills gap: audio and video people who need to learn switching and multicast, and network engineers who suddenly own a Dante deployment they were never trained for. Demand for people who can speak both languages is outpacing supply, especially across Asia, the Middle East, and other fast-growing markets.

This site sits squarely in that gap. Not vendor marketing, not a product datasheet rehash — the connective tissue between the AV rack and the network closet.

What you'll find here

Seven areas structure the archive. AV over IP — architecture, transport choices, multicast address planning. Audio Networking — Dante, AES67, clocking and interop. Video & Streaming — NDI, SDVoE, DM NVX, ST 2110, IPMX. Control & DSP — Q-SYS and Crestron control, automation, signal processing. Network Engineering — switch configuration, IGMP, QoS, VLANs, PTP, the IT fundamentals AV depends on. Certifications — practical routes through AVIXA CTS, Dante, Q-SYS, and networking credentials. Troubleshooting — diagnostics, field fixes, and the war stories that teach the most.

How posts are written

Where a post describes a configuration or a fix, it reflects real testing in a lab or on a live system — not a paraphrase of a manufacturer PDF. Version numbers, firmware quirks, and exact settings matter in this field, so they are stated explicitly rather than glossed over. When something is theory rather than tested, it says so.

Manufacturer documentation is cited where it is the authority, and corrected in the open when field behaviour differs from the datasheet. If you spot an error, reporting it is genuinely welcome — accuracy is the whole point of a reference.

On gear links and independence

Some posts link to hardware — switches, test tools, cabling, interfaces. Where those are affiliate links, a purchase may earn a small commission at no extra cost to you. That never determines what gets recommended. A switch is recommended because it handles IGMP and PTP correctly for the job, not because of a referral rate, and posts will say plainly when a cheaper or non-affiliate option is the better call.

Who writes it

ThePulse is written by a practitioner working in and studying AV-over-IP and network engineering — learning the stack deeply enough to deploy it, and documenting the path along the way. The perspective is deliberately hands-on rather than academic: what actually works on a real network, in a real rack, under a real deadline.

Contact

Corrections, questions, topic requests, or war stories worth writing up: reach out via the contact page. Technical corrections get priority.