Using your MOTU AVB device as a Mac audio interface over AVB Ethernet. When operating as an audio interface, MOTU AVB devices can be connected to a Mac with USB or Thunderbolt (if available). With firmware update 1.2.5 or later, and macOS El Capitan (10.11), a third option is available: AVB Ethernet.
You can subscribe to this list.2012JanFebMarAprMayJunJulAugSepOctNovDec2013JanFebMarAprMayJunJulAugSepOctNovDec2014JanFebMarAprMayJunJulAugSepOctNovDec2015JanFebMarAprMayJunJulAugSepOctNovDec2016JanFebMarAprMayJunJulAugSepOctNovDec2017JanFebMarAprMayJunJulAugSepOctNovDec2018JanFebMarAprMayJunJulAugSepOctNovDec2019JanFebMarAprMayJunJulAugSepOctNovDec2020JanFebMarAprMayJunJulAugSepOctNovDecSMTWTFS031. Hi,I am working on the Intel AVB library, I was trying to run the simpletalker/listener application from thesample apps provided by intel.My Host machine is Ubuntu 12.04 (32 bit machine) with Linux kernelversion 3.9. Attachments:Hi Eric,Thanks for your response.One more quick question,what is the interoperability between gPTP andlinuxptp(1588 PTP)?' .For Ethernet full-duplex links, gPTP requires the use of the peer delaymechanism, while 1588 also allows the use of end-to-end delay measurement.' Jriver media center review 2018.
Based on this I can conclude that i can cannot run gPTP on machine andLinuxptp on the other. Please let me know what you think on this.(FYIalready tried this and wasn't successful)You can find the difference between gPTP and 1588 PTP in the below link,Regards,Praveen.On Mon, Jul 8, 2013 at 6:37 PM, Mann, Eric wrote: HI Praveen –. I’ll answer the 2nd question first. I have heard about implementations which use static reservations, but I personally haven’t seen one myself. I believe you can fairly easily modify simpletalker to use ‘static reservations’ by skipping all of the SRP-related steps such as getting and registering a domain, registering the VLAN, reserving bandwidth by advertising a stream, and skipping the step of ‘waiting’ for a listener to arrive. The app would just start streaming packets with or without listeners. As to the 1st question – I may not fully understand your question about ‘verify the sync’.
Do you mean measuring the quality of the gPTP time? Or measuring the quality of the recovered media clocks?.
Simple talker made a simplifying assumption the stream is a synthetically (mathematically) generated ‘sine wave’ of a fixed frequency. The audio experts can certainly chime in on this comment – but I believe well designed systems seek to avoid SRC and rather adjust a PLL to the ADCs (if you can) to standardize the sampling media clock rate (e.g.
All devices share the same “48KHz” sampling rate). Since the simpletalker stream itself is synthetic – there are no PLLs available to adjust. Note: that the current simpletalker design assumed it is also the clock master – we need to modify the gptp daemon to use the linux kernel ‘adjtime’ API to adjust the frequency on the underlying LAN reference clock used to transmit the frames otherwise you will likely get eventually underruns. You could also locally adjust the transmit launchtimes instead but requires simpletalker to understand the rate ratio of the LAN interface. Most I210 adapters I have seen can be off +/- 240 nsec / sec under normal conditions (25 deg C). This means eventually an overrun or underrun every 8-9 minutes. The linuxptp daemon already implements the adjtime functionality.
The listener needs to implement some form of media clock recovery - either adjust a DAC media clock PLL (if you can) or implement SRC to convert from the talker’s rate to the local listener’s rate. The ‘simplelistener’ example application ignores the timestamps (for synchronization) since it is storing the data to disk. The 1st level problem to avoid is overrun/underruns (where the frequency between the talker and listener is ‘off’). Attachments:Hi,I'm trying to stream raw video, so I use 1500B packets and reserve various bandwidth (10-60MB/s). Everything goes well, but sometimes the video freezes a moment. So i try to find out what happend. I measure for eg.
30MB/s streams packet sending stats (talker side). The time between packets is usually 50us as it should be, but sometimes there is a 500ms gap. I read about launch time in the datasheet.
It says the calculated launch time is compared against the SYSTIML register, and there are some definitions about comaring rules. I suspect 'integrated' launch time (always inceased by PACKETIPG) somehow lose consistency and the difference between launch time and SYSTIML overflow the 500ms limit, so it must wait another 500ms to sync.I tried to check this theory and read the SYSTIML, but its always 0:uint16t nsechw;igbreadreg(dev,0xB600,&nsechw);If i increase the reserved bandwidth (and reduce the PACKETIPG), the number of gaps increase too. So the average (measured) bandwidth never goes beyond 30MB/s.Can somebody help me to find out the reason or read correctly the SYSTIML register?Can anyone stream faster then 30MB/s?Thanks,Dani.
Attachments:HI Praveen -I'll answer the 2nd question first. I have heard about implementations which use static reservations, but I personally haven't seen one myself. I believe you can fairly easily modify simpletalker to use 'static reservations' by skipping all of the SRP-related steps such as getting and registering a domain, registering the VLAN, reserving bandwidth by advertising a stream, and skipping the step of 'waiting' for a listener to arrive. The app would just start streaming packets with or without listeners.As to the 1st question - I may not fully understand your question about 'verify the sync'.
Do you mean measuring the quality of the gPTP time? Or measuring the quality of the recovered media clocks?Simple talker made a simplifying assumption the stream is a synthetically (mathematically) generated 'sine wave' of a fixed frequency. The audio experts can certainly chime in on this comment - but I believe well designed systems seek to avoid SRC and rather adjust a PLL to the ADCs (if you can) to standardize the sampling media clock rate (e.g. All devices share the same '48KHz' sampling rate). Since the simpletalker stream itself is synthetic - there are no PLLs available to adjust. Note: that the current simpletalker design assumed it is also the clock master - we need to modify the gptp daemon to use the linux kernel 'adjtime' API to adjust the frequency on the underlying LAN reference clock used to transmit the frames. Otherwise you will likely get eventually underruns.
You could also locally adjust the transmit launchtimes instead but requires simpletalker to understand the rate ratio of the LAN interface. Most I210 adapters I have seen can be off +/- 240 nsec / sec under normal conditions (25 deg C).
This means eventually an overrun or underrun every 8-9 minutes. The linuxptp daemon already implements the adjtime functionality.The listener needs to implement some form of media clock recovery - either adjust a DAC media clock PLL (if you can) or implement SRC to convert from the talker's rate to the local listener's rate. The 'simplelistener' example application ignores the timestamps (for synchronization) since it is storing the data to disk. The 1st level problem to avoid is overrun/underruns (where the frequency between the talker and listener is 'off'). Attachments:Hi Everyone,I need to implement AVB feature in an Automobile.Since the number oftalker and listener are fixed, i don't need SRP, rather i can just dostatic reservation for the streams.I'm planning to do the following using Open-AVB without the SRP support,1) Run gPTP on 2 more X86 machine and verify the sync.2) Run gPTP as master on IMX platform and gPTP slave on multiple X86machines to verify the sync.Questions:.1) we have 'simpletalker' application to test IEEE1722 protocol. How do ireceive the stream at the other end and verify the synchronization?2) Will 'simpletalker' work if SRP Daemon is not run?
Hi Eric,On Thu, Jul 4, 2013 at 1:07 AM, Mann, Eric wrote: The official IEEE 1733 standard can be downloaded from. Attachments:Aman -The igb library, the igbavb kernel-mode driver, and at present the 'simpletalker' example application (which uses the igb library) are all dependent on Intel I210 hardware.The gPTP and MRP daemons are not dependent on Intel hardware. The gPTP daemon does require the LAN hardware to implement the PHC timer interfaces for 1588 support. You could in theory also use the linuxptp daemon instead.The MRP daemon is used for the stream reservation protocol (SRP).
It pretty much requires a LAN interface which can transmit and receive multicast Ethernet frames.A basic AVB stack requires a few other components, like encapsulation libraries (e.g. 1722), media clock encoding and recovery (e.g. Attachments:Hi Aman,go forregards,MathiasFrom: Aman Sharma mailto:amansh.sharma5@.Sent: Friday, July 05, 2013 1:47 PMTo: Krause, MathiasCc: open-avb-devel@.Subject: Re: Open-avb-devel open Source AVBHi Krause,Thanks for your Reply.But is there any way to port Open-AVB on Linux machine.-RegardsAmanOn Fri, Jul 5, 2013 at 4:42 PM, Krause, Mathias wrote:Hi Aman,xcore is for the xmos technology (www.xmos.comSent: Friday, July 05, 2013 1:09 PMTo: open-avb-devel@. Attachments:Hi Aman,xcore is for the xmos technology (www.xmos.com. The challenge may be figuring out the correct astimestamp to put in thereif the file is stored on disk.
I'm not sure that mp4 files are stored at aconstant bitrate.On 7/3/2013 3:37 PM, Mann, Eric wrote: The official IEEE 1733 standard can be downloaded from. The official IEEE 1733 standard can be downloaded from.
Hi Eric,Thanks for the response.On Wed, Jul 3, 2013 at 6:55 PM, Mann, Eric wrote: Regarding 1733 vs 1722. I haven't seen a 1733 implementation yet, and I haven't looked at 1733 to determine an opinion as to which is better suited to specific usages. I suspect if you have an existing installed (legacy) application base which uses RTP, then using 1733 would be an easier transition than going to 1722. I will point out the existing simpletalker example application should be easily modified to open a file, grab samples, and packetize (like what you are suggesting).
The existing simplelistener application already receives the stream and stores to a file. The igbavb driver doesn't enforce any restrictions over what is transmitted over the 'AVB' queues - so yes, you can transmit 1733 frames just as easily as the existing 1722 example applications.
I also believe you can use the existing daemons to reserve bandwidth, as effectively the bandwidth reservations through the switches boil down to filtering on the multicast MAC addresses (and user priority/vlan) used.Ok I'll try it out, are there any links pointing to 1733 AVBTP packet structure.Thanks and Regards,-Frank S. Regarding 1733 vs 1722. I haven't seen a 1733 implementation yet, and I haven't looked at 1733 to determine an opinion as to which is better suited to specific usages. I suspect if you have an existing installed (legacy) application base which uses RTP, then using 1733 would be an easier transition than going to 1722.I will point out the existing simpletalker example application should be easily modified to open a file, grab samples, and packetize (like what you are suggesting).
The existing simplelistener application already receives the stream and stores to a file.The igbavb driver doesn't enforce any restrictions over what is transmitted over the 'AVB' queues - so yes, you can transmit 1733 frames just as easily as the existing 1722 example applications. Hi All,On Wed, Jun 26, 2013 at 2:32 PM, Frank Schimer wrote: Hi Eric, Is it possible to use 1733 protocol with Intel Open AVB? What i am actually trying out is try to take a stored media (mp4 file) packetize it as AVB send on the client side and de-packetize it and play it.
I believe to do so RTP (RTCP) would be a good protocol or can the same be achieved using 1722. Any pointers would be very much helpful.gentle ping.Thanks and Regards,-Frank S.
Microsoft Sidewinder Force Feedback 2 now has a special edition for these Windows versions: Windows 7, Windows 7 64 bit, Windows 7 32 bit, Windows 10, Windows 10 64 bit, Windows 10 32 bit, Windows 8,Windows 10 IoT 32bit, Windows 10 Pro Education 32bit, Windows Vista Enterprise (Microsoft Windows NT 6.0.6000.0) 32bit, Windows 10 Mobile 64bit, Windows 10 Enterprise LTSB 64bit, Windows Vista Home Basic 32bit, Windows 7 Home Basic 64bit, Windows Vista Home Premium 32bit, Windows 8 Pro 64bit, Windows 7 Service Pack 1 (Microsoft Windows NT) 32bit.
- Author: admin
- Category: Category
Using your MOTU AVB device as a Mac audio interface over AVB Ethernet. When operating as an audio interface, MOTU AVB devices can be connected to a Mac with USB or Thunderbolt (if available). With firmware update 1.2.5 or later, and macOS El Capitan (10.11), a third option is available: AVB Ethernet.
You can subscribe to this list.2012JanFebMarAprMayJunJulAugSepOctNovDec2013JanFebMarAprMayJunJulAugSepOctNovDec2014JanFebMarAprMayJunJulAugSepOctNovDec2015JanFebMarAprMayJunJulAugSepOctNovDec2016JanFebMarAprMayJunJulAugSepOctNovDec2017JanFebMarAprMayJunJulAugSepOctNovDec2018JanFebMarAprMayJunJulAugSepOctNovDec2019JanFebMarAprMayJunJulAugSepOctNovDec2020JanFebMarAprMayJunJulAugSepOctNovDecSMTWTFS031. Hi,I am working on the Intel AVB library, I was trying to run the simpletalker/listener application from thesample apps provided by intel.My Host machine is Ubuntu 12.04 (32 bit machine) with Linux kernelversion 3.9. Attachments:Hi Eric,Thanks for your response.One more quick question,what is the interoperability between gPTP andlinuxptp(1588 PTP)?' .For Ethernet full-duplex links, gPTP requires the use of the peer delaymechanism, while 1588 also allows the use of end-to-end delay measurement.' Jriver media center review 2018.
Based on this I can conclude that i can cannot run gPTP on machine andLinuxptp on the other. Please let me know what you think on this.(FYIalready tried this and wasn't successful)You can find the difference between gPTP and 1588 PTP in the below link,Regards,Praveen.On Mon, Jul 8, 2013 at 6:37 PM, Mann, Eric wrote: HI Praveen –. I’ll answer the 2nd question first. I have heard about implementations which use static reservations, but I personally haven’t seen one myself. I believe you can fairly easily modify simpletalker to use ‘static reservations’ by skipping all of the SRP-related steps such as getting and registering a domain, registering the VLAN, reserving bandwidth by advertising a stream, and skipping the step of ‘waiting’ for a listener to arrive. The app would just start streaming packets with or without listeners. As to the 1st question – I may not fully understand your question about ‘verify the sync’.
Do you mean measuring the quality of the gPTP time? Or measuring the quality of the recovered media clocks?.
Simple talker made a simplifying assumption the stream is a synthetically (mathematically) generated ‘sine wave’ of a fixed frequency. The audio experts can certainly chime in on this comment – but I believe well designed systems seek to avoid SRC and rather adjust a PLL to the ADCs (if you can) to standardize the sampling media clock rate (e.g.
All devices share the same “48KHz” sampling rate). Since the simpletalker stream itself is synthetic – there are no PLLs available to adjust. Note: that the current simpletalker design assumed it is also the clock master – we need to modify the gptp daemon to use the linux kernel ‘adjtime’ API to adjust the frequency on the underlying LAN reference clock used to transmit the frames otherwise you will likely get eventually underruns. You could also locally adjust the transmit launchtimes instead but requires simpletalker to understand the rate ratio of the LAN interface. Most I210 adapters I have seen can be off +/- 240 nsec / sec under normal conditions (25 deg C). This means eventually an overrun or underrun every 8-9 minutes. The linuxptp daemon already implements the adjtime functionality.
The listener needs to implement some form of media clock recovery - either adjust a DAC media clock PLL (if you can) or implement SRC to convert from the talker’s rate to the local listener’s rate. The ‘simplelistener’ example application ignores the timestamps (for synchronization) since it is storing the data to disk. The 1st level problem to avoid is overrun/underruns (where the frequency between the talker and listener is ‘off’). Attachments:Hi,I'm trying to stream raw video, so I use 1500B packets and reserve various bandwidth (10-60MB/s). Everything goes well, but sometimes the video freezes a moment. So i try to find out what happend. I measure for eg.
30MB/s streams packet sending stats (talker side). The time between packets is usually 50us as it should be, but sometimes there is a 500ms gap. I read about launch time in the datasheet.
It says the calculated launch time is compared against the SYSTIML register, and there are some definitions about comaring rules. I suspect 'integrated' launch time (always inceased by PACKETIPG) somehow lose consistency and the difference between launch time and SYSTIML overflow the 500ms limit, so it must wait another 500ms to sync.I tried to check this theory and read the SYSTIML, but its always 0:uint16t nsechw;igbreadreg(dev,0xB600,&nsechw);If i increase the reserved bandwidth (and reduce the PACKETIPG), the number of gaps increase too. So the average (measured) bandwidth never goes beyond 30MB/s.Can somebody help me to find out the reason or read correctly the SYSTIML register?Can anyone stream faster then 30MB/s?Thanks,Dani.
Attachments:HI Praveen -I'll answer the 2nd question first. I have heard about implementations which use static reservations, but I personally haven't seen one myself. I believe you can fairly easily modify simpletalker to use 'static reservations' by skipping all of the SRP-related steps such as getting and registering a domain, registering the VLAN, reserving bandwidth by advertising a stream, and skipping the step of 'waiting' for a listener to arrive. The app would just start streaming packets with or without listeners.As to the 1st question - I may not fully understand your question about 'verify the sync'.
Do you mean measuring the quality of the gPTP time? Or measuring the quality of the recovered media clocks?Simple talker made a simplifying assumption the stream is a synthetically (mathematically) generated 'sine wave' of a fixed frequency. The audio experts can certainly chime in on this comment - but I believe well designed systems seek to avoid SRC and rather adjust a PLL to the ADCs (if you can) to standardize the sampling media clock rate (e.g. All devices share the same '48KHz' sampling rate). Since the simpletalker stream itself is synthetic - there are no PLLs available to adjust. Note: that the current simpletalker design assumed it is also the clock master - we need to modify the gptp daemon to use the linux kernel 'adjtime' API to adjust the frequency on the underlying LAN reference clock used to transmit the frames. Otherwise you will likely get eventually underruns.
You could also locally adjust the transmit launchtimes instead but requires simpletalker to understand the rate ratio of the LAN interface. Most I210 adapters I have seen can be off +/- 240 nsec / sec under normal conditions (25 deg C).
This means eventually an overrun or underrun every 8-9 minutes. The linuxptp daemon already implements the adjtime functionality.The listener needs to implement some form of media clock recovery - either adjust a DAC media clock PLL (if you can) or implement SRC to convert from the talker's rate to the local listener's rate. The 'simplelistener' example application ignores the timestamps (for synchronization) since it is storing the data to disk. The 1st level problem to avoid is overrun/underruns (where the frequency between the talker and listener is 'off'). Attachments:Hi Everyone,I need to implement AVB feature in an Automobile.Since the number oftalker and listener are fixed, i don't need SRP, rather i can just dostatic reservation for the streams.I'm planning to do the following using Open-AVB without the SRP support,1) Run gPTP on 2 more X86 machine and verify the sync.2) Run gPTP as master on IMX platform and gPTP slave on multiple X86machines to verify the sync.Questions:.1) we have 'simpletalker' application to test IEEE1722 protocol. How do ireceive the stream at the other end and verify the synchronization?2) Will 'simpletalker' work if SRP Daemon is not run?
Hi Eric,On Thu, Jul 4, 2013 at 1:07 AM, Mann, Eric wrote: The official IEEE 1733 standard can be downloaded from. Attachments:Aman -The igb library, the igbavb kernel-mode driver, and at present the 'simpletalker' example application (which uses the igb library) are all dependent on Intel I210 hardware.The gPTP and MRP daemons are not dependent on Intel hardware. The gPTP daemon does require the LAN hardware to implement the PHC timer interfaces for 1588 support. You could in theory also use the linuxptp daemon instead.The MRP daemon is used for the stream reservation protocol (SRP).
It pretty much requires a LAN interface which can transmit and receive multicast Ethernet frames.A basic AVB stack requires a few other components, like encapsulation libraries (e.g. 1722), media clock encoding and recovery (e.g. Attachments:Hi Aman,go forregards,MathiasFrom: Aman Sharma mailto:amansh.sharma5@.Sent: Friday, July 05, 2013 1:47 PMTo: Krause, MathiasCc: open-avb-devel@.Subject: Re: Open-avb-devel open Source AVBHi Krause,Thanks for your Reply.But is there any way to port Open-AVB on Linux machine.-RegardsAmanOn Fri, Jul 5, 2013 at 4:42 PM, Krause, Mathias wrote:Hi Aman,xcore is for the xmos technology (www.xmos.comSent: Friday, July 05, 2013 1:09 PMTo: open-avb-devel@. Attachments:Hi Aman,xcore is for the xmos technology (www.xmos.com. The challenge may be figuring out the correct astimestamp to put in thereif the file is stored on disk.
I'm not sure that mp4 files are stored at aconstant bitrate.On 7/3/2013 3:37 PM, Mann, Eric wrote: The official IEEE 1733 standard can be downloaded from. The official IEEE 1733 standard can be downloaded from.
Hi Eric,Thanks for the response.On Wed, Jul 3, 2013 at 6:55 PM, Mann, Eric wrote: Regarding 1733 vs 1722. I haven't seen a 1733 implementation yet, and I haven't looked at 1733 to determine an opinion as to which is better suited to specific usages. I suspect if you have an existing installed (legacy) application base which uses RTP, then using 1733 would be an easier transition than going to 1722. I will point out the existing simpletalker example application should be easily modified to open a file, grab samples, and packetize (like what you are suggesting).
The existing simplelistener application already receives the stream and stores to a file. The igbavb driver doesn't enforce any restrictions over what is transmitted over the 'AVB' queues - so yes, you can transmit 1733 frames just as easily as the existing 1722 example applications.
I also believe you can use the existing daemons to reserve bandwidth, as effectively the bandwidth reservations through the switches boil down to filtering on the multicast MAC addresses (and user priority/vlan) used.Ok I'll try it out, are there any links pointing to 1733 AVBTP packet structure.Thanks and Regards,-Frank S. Regarding 1733 vs 1722. I haven't seen a 1733 implementation yet, and I haven't looked at 1733 to determine an opinion as to which is better suited to specific usages. I suspect if you have an existing installed (legacy) application base which uses RTP, then using 1733 would be an easier transition than going to 1722.I will point out the existing simpletalker example application should be easily modified to open a file, grab samples, and packetize (like what you are suggesting).
The existing simplelistener application already receives the stream and stores to a file.The igbavb driver doesn't enforce any restrictions over what is transmitted over the 'AVB' queues - so yes, you can transmit 1733 frames just as easily as the existing 1722 example applications. Hi All,On Wed, Jun 26, 2013 at 2:32 PM, Frank Schimer wrote: Hi Eric, Is it possible to use 1733 protocol with Intel Open AVB? What i am actually trying out is try to take a stored media (mp4 file) packetize it as AVB send on the client side and de-packetize it and play it.
I believe to do so RTP (RTCP) would be a good protocol or can the same be achieved using 1722. Any pointers would be very much helpful.gentle ping.Thanks and Regards,-Frank S.
Microsoft Sidewinder Force Feedback 2 now has a special edition for these Windows versions: Windows 7, Windows 7 64 bit, Windows 7 32 bit, Windows 10, Windows 10 64 bit, Windows 10 32 bit, Windows 8,Windows 10 IoT 32bit, Windows 10 Pro Education 32bit, Windows Vista Enterprise (Microsoft Windows NT 6.0.6000.0) 32bit, Windows 10 Mobile 64bit, Windows 10 Enterprise LTSB 64bit, Windows Vista Home Basic 32bit, Windows 7 Home Basic 64bit, Windows Vista Home Premium 32bit, Windows 8 Pro 64bit, Windows 7 Service Pack 1 (Microsoft Windows NT) 32bit.