The thesis includes an AES67 controller based on Python3, Websockets and JSON objects. As discovery library, Avahi shall be used. All setup as a Docker container. Thus, it should be platform independent.

Am 20. Dezember 2017 10:37:46 MEZ schrieb Christoph Kuhr <>:

have a look at:

There you can find the entire AVB driver stack and subsystem. Along with
some Gstreamer and Jack Audio examples.


On 12/20/2017 07:45 AM, Happy wrote:

Just received two of these (HP) I-210 "PCI 2.1" cards (from Amazon).
Installed one of them in and old PC with a PCI-e 2.0 x 4 slot (thus only
using part of the slot). Initially windows reported an error and it did
not work. Went back to Ubuntu 17.10 on the same machine and it worked
fine. (Same result as another person before me). Disabled the internal
NIC and started Windows again. Voila, it worked ! Re-enabled the
on-board NIC and it kept Working in windows. Just for reference.  Don't
have a AVB audio device so cannot really test them. Looking if there is
any AVB test software out there to use these two cards to transmit AVB
based audio from one to the other.

From talking to Focusrite regarding AES67 and the Rednet series and
firmware support, got the following:  "With regards to AES67
compatibility, this is possible for devices using the 'Brooklyn 2' Dante
chipset. RedNet 3s ship with a 'Brooklyn 1' chipset, though it's
possible to upgrade to a Brooklyn 2 (this would be chargeable). All of
our devices using Brooklyn 2 modules have AES67 compliance following the
latest firmware update available from RedNet Control"  (Focusrite
Rednets use the Bonjour/mDNS protocol for discovery)

In conclusion, the 3 parts needed for full functionality on Linux
[1] Discovery - mDNS should be doable in Linux, right ?
[2] AoIP  / clocking - This AES67 project
[3] Control (of the device) - Windows/Mac for the moment. Hopefully
suppliers will support some kind of new standard in the future for that
as well ( HTML XML, JSON  or other open messaging over IP to configure
the unit). The Rednet3 will keep the routing/configuration after power
cycling thus until then that should be done under Windows.

Looking forward on the progress  of this project !

On 10/1/2017 4:32 PM, Christoph Kuhr wrote:
A few years back there had been a AES67/Ravenna implementation. But
the developer and ALX Networks could not agree on the license. The
developer wanted to publish it under GPL, which ALX Networks did not
want. So the implementation was dumped. Well, that is the story how I
know it.
The developer was Florian Faber, but he is no member of the jack-devel
or linux-devel list anymore. Perhapes, he might have some useful
insights, if you manage to find a contact. ;-)

On 09/30/2017 06:12 AM, happy musicmaker wrote:
There are some different I210 card versions it seems, any
recommendations ?

They are all ok. I have different versions myself: Intel I210, HP
I210TI. But make shure it is no I217, because they have no traffic
shaping queues. Although they suport HW PTP timestamping.


On Thu, Sep 28, 2017 at 6:11 PM, Christoph Kuhr
< <>> wrote:

    With an Intel I210 NIC you can already have AVB in combination with
    Jack. But you have to do some coding yourself to fit your purposes..

    I would never recommend buying MOTU.


    On 09/28/2017 08:33 AM, happy musicmaker wrote:

        MOTU just released the 828es with AVB and USB standard compliant
        and two ADAT I/O and Web based (not ALSA) mixer. That would be,
        for now, the ultimate (AVB)  interface for Linux,  if it works.

        On Thu, Sep 28, 2017 at 11:31 AM, happy musicmaker
        < <>
        <>>> wrote:

             That is such good news.  What(low cost)  hardware would
             development be used on to support the developers with
             testing/debugging and maybe even development ?

             * MOTU LP32 (Preferred)
             * MiniDSP
<>> (I think
             MOTU's switch uses midDSP switch hardware)

             I hope someday it will be possible to connect 4 or more 8
             ADAT modules (32 channels) to a PC under Ubuntu via AVB
        with low
             latency. The only option to get this done under Windows
is a
             Focursrite DANTE based Rednet 3 right now because
        Thunderbolt is not
             really available there as well. Plan to get Rednet3,  but
        that does
             not solve the Linux environment which I prefer. Would love
        to be
             able to use the Rednet 3 under Linux but since DANTE is
             , so unlikely.

             My two wishes:
                [a] Multi (16+) channel low latency audio I/O using ADAT
        audio AD/DA
                [b[ Bitwig  supporting LV2 plugins.

             With those two,  the Linux Audio environment would be
        perfect and
             the world a better place.

             *(Apology for the re-sends and ignore the previous edits.
        Web based
             Gmail is such a annoyance and un-logically structured)*

        Jack-Devel mailing list

    Jack-Devel mailing list

Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.