#aes67 — Public Fediverse posts

Here's Taruntej Kanakamalla, walking us through his experience building a real-time network audio application in Windows.

#linux #multimedia #windows #realtime #audio #aes67 #Dante #gstconf2024

Here's Taruntej Kanakamalla, walking us through his experience building a real-time network audio application in Windows.

#linux #multimedia #windows #realtime #audio #aes67 #Dante #gstconf2024

Here's Taruntej Kanakamalla, walking us through his experience building a real-time network audio application in Windows.

#linux #multimedia #windows #realtime #audio #aes67 #Dante #gstconf2024

Here's Taruntej Kanakamalla, walking us through his experience building a real-time network audio application in Windows.

#linux #multimedia #windows #realtime #audio #aes67 #Dante #gstconf2024

Here's Taruntej Kanakamalla, walking us through his experience building a real-time network audio application in Windows.

#linux #multimedia #windows #realtime #audio #aes67 #Dante #gstconf2024

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?

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?

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?

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?

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?

#OSX #Nerds, insofern das kein Oxymoron ist, ich brauch eine Idee:

So ca. alle 15 Minuten stört ein Prozess auf #macOS #Ventura meine #AES67 Audio-Übertragung via #Merging #VirtualAudioDevice.

Das ist hörbar, aber auch sichtbar im #DanteController – die Übertragung läuft mit einem #Dante-fähigen Mischpult

Wie kann ich nun diesen Prozess finden?

Auf Verdacht mittels Kommandozeile / Endlosschleife und ps mitschreiben ist meine einzige Idee. Die ist aber dürftig, denn es geht um ca. 10 bis 20 verschusselte Audio-Samples, das verursachende Event ist also sehr kurz. Außerdem kann ich es im Dante Controller nicht loggen, also nicht irgendwie mittels Timestamps zusammenbringen.

Rechner ist ein #MacMini #M1, ich hab nach Anleitung von Merging alle möglichen Dinge wie Updates, Spotlight, Bluetooth etc. deaktiviert.

Vorgestern habe ich mal wieder mit einer Windose und WAVES Soundgrid (statt Dante/AES67) gearbeitet und da gibt's schon 2 bis 5 leckere Plugins von #Waves, die mir live im eigenen Setup fehlen.

#OSX #Monterey auf gebrauchtem #MacMini #M1 von USB-Stick installiert. Vorher mittels #Festplattendienstprogramm den #Apple geplättet.

(Tipp von @ulfhenrich – danke.)

Kann nun, wie schon auf #BigSur, keinen Account anlegen.

Nach einem Timeout wird gemeldet, das Anlegen sei gescheitert, der Account existiert hernach, aber hat kein gültiges Passwort.

Da das Installationsprogramm meine WLAN-Zugangsdaten wusste, ist davon auszugehen, dass Apple unlöschbare Informationen im Gerät ablegt, die das Anlegen eines Accounts sabotieren.

Das war jetzt mal wieder ein teurer Briefbeschwerer, dieser Apple-Rechner.

Ein neuer M2 würde mir aber nichts nützen, da dessen 10gbps Netzwerkkatte nicht von der Software unterstützt wird, die ich brauche (#Merging #AES67 #VirtualAudioDevice).

Vielleicht funktionieren jetzt die Anleitungen im Netz, wie in dem Fall zu verfahren sei. Ich glaube nicht mehr daran.

Die vielen Fehlversuche treiben die #TotalCostOfOwnership (#tco) ins Unermessliche.

Der olle #Cisco #SG250 #Switch kann's: #Ravenna / #AES67 mit #Dante Geräten verknüpfen, ohne dass alles kollabiert.

Denn sobald AES67 in Betrieb ist, befindet man sich im dunklen Land des #Multicast, während Dante alleine auch nur im #Unicast Modus betrieben werden kann (insofern man nicht zu viel 1:n Verbindungen routen muss etc.).

Allerdings ist bei ihm die #PTPclock nicht besonders sicher in der Übertragung, so liest man.

#IGMPsnooping und #QoS etc. machen es möglich, insb. muss der Switch ein #IMGPquerier sein. Und leider: Man kann dann auch nur noch solche Switches nutzen, denn: Mischen impossible gleich im doppelten Sinn.

Die meisten fellow #Tontechniker nun so: Ah, Bahnhof, bahnhof, bahnhofts du bahnhof. Kauf einfach #Luminex Switches dann geht alles, Homepage von denen: „Set-up a pro AV network without any IT knowledge.“

Money money money, must be funney…

#AudioOverIP #veranstaltungstechnik

Auf der Kampf- und Spielwiese #Ravenna / #AES67 #Mergin #VirtualAudioDevice gelernt:

Das #MacBookPro 2017 zieht keine Wurst vom Teller. Eigentlich wusste ich schon, dass es eines der schlechtesten Laptops out there ist.

Aber die Netzwerk-Performance mit diesem Adapter-Wahnsinn über USB 3 verkleidet als Donnerbolzen ist einfach zu schlecht für #AudioOverIP mit niedriger Latenz.

Und wenn es ihm zu warm wird, drosselt es sich einfach so, dass alles abkackt.

#Apple #Gläubige sagen: Du brauchst unbedingt nen M2 dingstralla für $Schweinegeld und ich denk: Ich brauch was, das mich nicht aufregt und günstig ist.

Let's see… https://blog.inagaki.in/en/post/linux-waves-plugins/

#linux #waves #audio

Okay, diese ganze Geschichte mit #Dante und #Waves und #Plugins fürs #Mischpult nutzen, wo ich herumlaboriere mit #Ravenna und #AES67, die lässt sich lösen.

Mit der #SuperRack #Livebox, neu auf dem Markt. Easy.

Nur halt leider 7.000$ schwer.

Das wären dann um am Ende um die 7k€ für eine einzige Funktion, die mir fehlt, nämlich die von Waves #PSE.

Hätte so mancher Kapelle gut getan, die ich unlängst mischte, aber bezahlen will niemand dafür.

Also die richtige, gute und stabile Lösung gibt's dann halt nicht.

https://www.waves.com/hardware/superrack-livebox

#Tontechnik #Veranstaltungstechnik #WSG

Die Erleichterung des Aufgebens ist vielleicht nicht so manchen Nerdes liebstes Gefühl. Und jetzt: #Atmen, #Loslassen.

Ich entferne das #MerginAudioDevice (#MAD) vom #Windows Rechnerlein. Nach vielen Stunden des Versuchens habe ich mit diesem virtuellen #ASIO #AudioInterface für #AES67 / #Ravenna keine Verbindung zu meinem #Dante-System im AES67-Modus hinbekommen.

Und das alles wegen ein paar erhofften Millisekunden weniger Latenz an einer kleinen Ecke. Ich geb's auf, ich lasse es los, so geht's eben nicht.

So bleibt nur #WAVES direkt für mein Vorhaben. Also die Erweiterungskarte fürs Pult, ca 900€, dann noch die Bridge auf Dante, das macht weitere 3200€. Oder das größere Mischpult (#AllenHeath #Avantis anstatt #SQ5) für, erm, naja. 18500€

Oder halt die Vocals 8msec zu spät via wackeligem USB und den Recorder über #DanteVirtualSoundcard mit noch einem Laptop mehr.

Oder eben keinen #PrimarySourceExpander und weniger perfekten Sound.

Die Kunden wollen sowieso eigentlich alles für 0€ haben.

@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.

@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.

@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.

@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.

@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.

@pkw @screwtape @fishfinger that’s interesting! I’m trying to figure out a good platform for building #aes67 - based networked #audio gadgets - thus far mainly looked at alsa-based #linuxaudio stuff, like (GPLed) Ravenna drivers, etc. Will have a closer look.

@pkw @screwtape @fishfinger that’s interesting! I’m trying to figure out a good platform for building #aes67 - based networked #audio gadgets - thus far mainly looked at alsa-based #linuxaudio stuff, like (GPLed) Ravenna drivers, etc. Will have a closer look.

@pkw @screwtape @fishfinger that’s interesting! I’m trying to figure out a good platform for building #aes67 - based networked #audio gadgets - thus far mainly looked at alsa-based #linuxaudio stuff, like (GPLed) Ravenna drivers, etc. Will have a closer look.

@pkw @screwtape @fishfinger that’s interesting! I’m trying to figure out a good platform for building #aes67 - based networked #audio gadgets - thus far mainly looked at alsa-based #linuxaudio stuff, like (GPLed) Ravenna drivers, etc. Will have a closer look.

@pkw @screwtape @fishfinger that’s interesting! I’m trying to figure out a good platform for building #aes67 - based networked #audio gadgets - thus far mainly looked at alsa-based #linuxaudio stuff, like (GPLed) Ravenna drivers, etc. Will have a closer look.

Has anyone had luck playing with the #aes67 on #pipewire yet? Would very much like to pick your brain if it is so. #linuxaudio

Has anyone had luck playing with the #aes67 on #pipewire yet? Would very much like to pick your brain if it is so. #linuxaudio

Has anyone had luck playing with the #aes67 on #pipewire yet? Would very much like to pick your brain if it is so. #linuxaudio

Has anyone had luck playing with the #aes67 on #pipewire yet? Would very much like to pick your brain if it is so. #linuxaudio

Has anyone had luck playing with the #aes67 on #pipewire yet? Would very much like to pick your brain if it is so. #linuxaudio

Schöne Grüße aus dem Studio #podcast #thisweekinradiotech #twirt #aufnahme #studio #radiostudio #vmix #axiaaudio #livewire #aes67

Schöne Grüße aus dem Studio #podcast #thisweekinradiotech #twirt #aufnahme #studio #radiostudio #vmix #axiaaudio #livewire #aes67

Schöne Grüße aus dem Studio #podcast #thisweekinradiotech #twirt #aufnahme #studio #radiostudio #vmix #axiaaudio #livewire #aes67

Schöne Grüße aus dem Studio #podcast #thisweekinradiotech #twirt #aufnahme #studio #radiostudio #vmix #axiaaudio #livewire #aes67

Also Audinate has indicated they are not interested in porting their stuff to Linux. #Ableton as well. I’ve used #bitwig on #Linux in a theatre performance and it works just great! Now if I could only directly connect to existing #Dante / #AES67 systems without extra hardware, like the USB dongle.

Also Audinate has indicated they are not interested in porting their stuff to Linux. #Ableton as well. I’ve used #bitwig on #Linux in a theatre performance and it works just great! Now if I could only directly connect to existing #Dante / #AES67 systems without extra hardware, like the USB dongle.

Pretty high on my #LinuxAudio wishlist would be #aes67 support for #jack and/or #pipewire. That would open up (most) #dante devices in compatibility mode, and a whole new world of professional #audio. Most pieces of the puzzle are there already, but require a lot of tinkering to get working. The discovery / routing side of Dante is not that hard but it is encumbered by patents, afaik.

Pretty high on my #LinuxAudio wishlist would be #aes67 support for #jack and/or #pipewire. That would open up (most) #dante devices in compatibility mode, and a whole new world of professional #audio. Most pieces of the puzzle are there already, but require a lot of tinkering to get working. The discovery / routing side of Dante is not that hard but it is encumbered by patents, afaik.