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.. BTW: I would never recommend buying MOTU. BR, Ck On 09/28/2017 08:33 AM, happy musicmaker wrote: _______________________________________________ Jack-Devel mailing list Jack-Devel(a)lists.jackaudio.org http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

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. ;-)

Thanks all for these helpful comments! I’ve been studying the last days, and I am studying more. I downloaded merging technologies free AES67 virtual sound card for mac already, as well as the Dante Via from audinate (59USD). The latter is also capable of functioning as a master clock on the network I understand. That will do for the testing and development at this time. Thanks for the many other suggestions you made. The gear I found before was more expensive (e.g. digigram has a -very well reputed- ravenna sound card with linux support for about 2K). There is indeed a Ravenna reference implementation with linux support by ALC NetworX. I’m waiting for information regarding conditions for obtaining, using, distributing it. I’m also in contact with people at Merging regarding their VSC driver in progress for Linux. I contacted audinate regarding AES67 patent claims. As said, I’m not really considering implementing AES67 as a virtual sound card driver - I prefer to stay clear of kernel space development. Instead, Im aiming for a jack client application, and perhaps a jack audio driver (like the net drivers). The latter allow to have jack running at AES67 clock, and being fully transparent (no sample rate conversion). But the former, a client application, is probably better if you just want to receive and monitor / send AES67 on / from a computer having a sound card already. Thanks also for the hint about the zita resampler library. I’m keeping you informed about progress and findings. Best, Philippe. On 01 Oct 2017, at 10:32, Christoph Kuhr <christoph.kuhr(a)web.de> wrote: 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. or linux-devel list anymore. Perhapes, he might have some useful insights, if you manage to find a contact. ;-) _______________________________________________ Jack-Devel mailing list Jack-Devel(a)lists.jackaudio.org http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

Bugger, according to this, the I210T1 requires a PCI 2.1 slot. Mine is just a 2.0. https://communities.intel.com/thread/108269. The Intel I210T1 spec states "The interface only supports the PCIe v2.1 (2.5GT/s) rate and is configured to x1." So, this seems to be a showstopper. Most new MB are already PCI Gen 3, like this https://www.msi.com/Motherboard/Z77AG45_Thunderbolt/Specification, So if it ONLY supports PCI 2.1 ... (?) Would the card work on 2.0 and 3.0 ?

On Tue, October 3, 2017 2:19 am, happy musicmaker wrote: PCIe 2.1 was basically an addendum to add additional features, all compliant PCIe devices are required to be backwards compatible with older slots. The PCIe version listed on the specification is the highest version that it can support with full features, not a strict list. Note also that there seems to be a mistake in the specification, PCIe 2 generation should be 5GT/s not 2.5GT/s. Possibly the device supports the register set and software features of PCIe 2.1 but only runs at gen 1.0 speed of 2.5GT/s, but that would be unusual. I would check the list at linuxptp.sourceforge.com for recommended adapters. The linuxptp project takes advantage of the latest linux kernel features and does not limit itself to interfaces available in other OS like ptpd. I don't know if that provides any performance advantage or not, linuxptp project claims that using linux specific kernel API is better than using generic posix API. This is the list of drivers which support hardware time stamping in the MAC layer, but you have to look at the details for the card you want to buy. For example, the tg3 driver supports hardware timestamping on Broadcom Tigon based cards, but I have a broadcom NIC which does not support hardware timestamping, only software. Note that if you have a Windows installation and want to use the ALC Windows virtual sound card you will need an adapater with an 82574L controller. I apologize for the poor formatting, I do not want to use HTML email for the mailing list, see the linuxptp web page for an easier to read table format. 5.3.2 Hardware Timestamping - MAC Driver Hardware Version amd-xgbe AMD 10GbE Ethernet Soc 3.17 bfin_mac Analog Blackfin 3.8 bnx2x Broadcom NetXtremeII 10G 3.18 cpts Texas Instruments am335x 3.8 e1000e Intel 82574, 82583 3.9 fm10k Intel FM10000 3.18 fec Freescale i.mx6 3.8 gianfar Freescale eTSEC PowerPC 3.0 i40e Intel XL710 Family 3.14 igb Intel 82576, 82580 3.5 ixgbe Intel 82599 3.5 mlx4 Mellanox 40G PCI 3.14 ptp_ixp46x Intel IXP465 3.0 ptp_phc Lapis EG20T PCH 3.5 sfc Solarflare SFC9000 3.7 stmmac STM Synopsys IP Core 3.10 tg3 Broadcom Tigon3 PCI 3.8 tilegx Tilera GBE/XGBE 3.12 -- Chris Caudle _______________________________________________ Jack-Devel mailing list Jack-Devel(a)lists.jackaudio.org http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

On Mon, October 2, 2017 5:12 am, Philippe Bekaert wrote: Did you get a copy of the ALSA driver? The current git head does not compile, I waited to see if merging would correct that on their own, but still not corrected after a month, so I need to ask what is happening there. Not encouraging that it is actually getting any attention if the source can go more than a month in a non-buildable state. I recommend a jack audio driver. If you want to monitor from a local sound card you can always load zita-j2a and zita-a2j resampling bridges, that work has been done so no need to implement twice what Fons has already implemented. The advantages of a net driver is that you can in principle collect streams from different devices that are in the same clock domain and have a large virtual sound card. For example, in a home recording environment you could have a Ravenna output device in your room with a computer, have a Ravenna in/out device in a different room with someone playing keyboards, and a Ravenna in/out device in the house large room playing guitar, and all three of those physically separated devices could be treated as one large audio interface. I am not sure if jackd will let a driver load and then change the number of ports at a later time, so how configuration would work is a task that needs to be investigated early (e.g. would you have to discover and configure Ravenna streams first, then load the net driver, or could the net driver be loaded with some arbitrary number of ports declared to jackd, and various Ravenna streams connected and disconnected from those declared ports at run time). I am still struggling to find reasonable cost network connected interfaces. The small device from Hasseb I linked last time is reasonable cost, but very low feature, I would prefer at least a duplex stereo device. Focusrite have a new two channel Dante device which could run in AES67 mode, but it is output only, and I think is around US$400. The 4 input 2 output Cymatic device is still not available yet, and even though the 24 channel Cymatic device has reduced price by 50% lately, that is the base USB version only, so by the time you purchase the Ravenna option card it is still around US$1000. Not a bad price for 24 channels, but still could be considered quite a lot to spend on a hobby investigation project. If a Windows computer is available, the Lawo R3lay virtual sound card for Windows is the best option to get started. I tried it and was able to send audio between two Windows laptops. You will need a PTP master on the network, that VSC will not act as clock master, but I am running a BeagleBone Black as PTP master (uses chronyd to sync time to ntp, then provides the ntp time to the network using linuxptp). You could also use your existing linux machine to act at PTP master, it would just have more jitter in the PTP performance if you do not have hardware timestamping capability (the BeagleBone has hardware timestamp in the MAC layer but not the phy, not ideal but still fairly high performance). -- Chris Caudle _______________________________________________ Jack-Devel mailing list Jack-Devel(a)lists.jackaudio.org http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

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: 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. BR, CK

Hi, have a look at: https://github.com/AVnu/OpenAvnu There you can find the entire AVB driver stack and subsystem. Along with some Gstreamer and Jack Audio examples. BR, CK On 12/20/2017 07:45 AM, Happy wrote: only did internal Don't is AVB Dante of the that configure power I jack-devel with purposes.. compliant be, works. <mailto:happy.musicmaker@gmail.com> would more 8 AVB Windows but love is ADAT edits. structured)* >>> >>> >>> >>> >>>         _______________________________________________ >>>         Jack-Devel mailing list >>>         Jack-Devel(a)lists.jackaudio.org >>>         <mailto:Jack-Devel@lists.jackaudio.org> >>> http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org >>> <http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org> >>> >>> >>>     _______________________________________________ >>>     Jack-Devel mailing list >>>     Jack-Devel(a)lists.jackaudio.org >>> <mailto:Jack-Devel@lists.jackaudio.org> >>> http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org >>> <http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org> >>> >>> >> >

On 16 Jan 2018, at 10:50, zmlopez &lt;zmlopez(a)gmail.com&gt; wrote: Very interesting. I'm working in something similar. My concept is to use gstreamer plugins for AES67 (gstreamer could already use ptp clocks), and AES70 (OCA) for control and discovery: http://www.aes.org/publications/standards/search.cfm?docID=103 https://github.com/DeutscheSoft/OCA.js/tree/master -- Sent from: http://jack-audio.10948.n7.nabble.com/Jackit-f3.html _______________________________________________ Jack-Devel mailing list Jack-Devel(a)lists.jackaudio.org http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

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:

Hi *, long time no update... AES67 for baresip is nearly ready and is now being evaluated by the master student. It will be available two months from now, I think. Did you make some progress? BR, Christoph 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. >> >> >> >> BR, >> CK >> >> >>> >>> >>> On Thu, Sep 28, 2017 at 6:11 PM, Christoph Kuhr >>> &lt;christoph.kuhr(a)web.de <mailto:christoph.kuhr@web.de>> 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.. >>> >>> >>>     BTW: >>>     I would never recommend buying MOTU. >>> >>> >>>     BR, >>>     Ck >>> >>> >>>     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 >>>         &lt;happy.musicmaker(a)gmail.com >>> <mailto:happy.musicmaker@gmail.com> >>>         <mailto:happy.musicmaker@gmail.com >>>         <mailto:happy.musicmaker@gmail.com>>> wrote: >>> >>>              That is such good news.  What(low cost) hardware would >>> this >>>              development be used on to support the developers with >>>              testing/debugging and maybe even development ? >>> >>>              * MOTU LP32 (Preferred) >>>              * MiniDSP >>> https://www.minidsp.com/products/network-audio/avb-dg >>> <https://www.minidsp.com/products/network-audio/avb-dg> >>> <https://www.minidsp.com/products/network-audio/avb-dg >>> <https://www.minidsp.com/products/network-audio/avb-dg>> (I think >>>              MOTU's switch uses midDSP switch hardware) >>> >>>              I hope someday it will be possible to connect 4 or more 8 >>>         channel >>>              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 >>>         proprietary >>>              , 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(a)lists.jackaudio.org >>>         <mailto:Jack-Devel@lists.jackaudio.org> >>> http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org >>> <http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org> >>> >>> >>>     _______________________________________________ >>>     Jack-Devel mailing list >>>     Jack-Devel(a)lists.jackaudio.org >>> <mailto:Jack-Devel@lists.jackaudio.org> >>> http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org >>> <http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org> >>> >>> >> >

MOTU just released the 828es with AVB and USB standard compliant and two