digitalcourage.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Diese Instanz wird betrieben von Digitalcourage e.V. für die Allgemeinheit. Damit wir das nachhaltig tun können, erheben wir einen jährlichen Vorausbeitrag von 1€/Monat per SEPA-Lastschrifteinzug.

Server stats:

861
active users

#aes67

0 posts0 participants0 posts today

Anyone have any experience with #aes67?

I'm working in a theatre to consolidate a bunch of ad-hoc networks into a nice VLAN segregated network. I'm running an #openwrt router with a #cisco 2900-x series switch.

I have a #barco #sp4k projector and #dolby #cp950 audio processor, which uses 8 channels of aes67.

Currently we have a direct link over cat6 between the projector and the processor.

I would like to put the AES on the same trunk line as the rest of the network.

The network setting on the Dolby AES67 has 2 IPs:

1) static source IP: 192.168.1.151
2) destination broadcast IP: 239.81.83.67

The Barco doesn't seem to have any configuration for audio network.

My thinking is I should be able to change the source IP to something on the relevant VLAN: 10.10.11.151 (VLAN 11).

But what about the multicast? It seems common to be on a 239.0.0.0. Do I need another VLAN to cover that network?

@pkw @screwtape @fishfinger Thanks for the pointer. All the doc and references are a bit thin on the sample clock/synchronization side - pretty sure if they'd implemented a standard like #AES67, or used a super accurate sample clock timing like with PTP, then that would've been mentioned. Having AES67 available out-of-the box would be an absolute killer for studio and live audio stuff - especially now that there's some serious DAW offerings out there for #FOSS OS and #linuxaudio in particular.