How to initialize endpoint and connect streams (I210, open-avb)

[owenfmurphy]

Hello,
Is there any tutorial for using the command line program to initialize the machine as an endpoint (acquire entity number, etc)? Currently I have an Ubuntu PC with an I210 PCI card, and I am trying to get it to connect to my AVB network. I have enabled the open-avb drivers, and I am running the open-avb daemons. The rest of the network consists of:
(1) Mac Mini (latest OS, AVB compatible ethernet chip)
(1) MOTU AVB interface
(1) DSP4You OEM AVB endpoint
(1) MOTU AVB Switch

When I run the command line program, I can see the Mac Mini, the Motu interface, and the endpoint when I type "view all" and "list", but the ubuntu machine does not appear. Is there an command I need to issue that allows the ubuntu machine to connect to the network?

There is another strange issue I noticed regarding the mac mini. When I type "view all", none of the parameters for the mac mini show up the way they do for the other endpoints. The streams are available though, because I can connected them to the motu interface using motu's browser based controller. Does anyone know if OS X follows the AVDECC protocol exactly? I am having problems using my mac mini with the switch, so it's possible they don't implement it the protocol properly. I just wanted to see if anyone else had issues, or has any information on the matter.

Thanks for the help!
Owen

[jdkoftinoff]

At this point the OpenAVB code does not include an AVDECC entity implementation. The starting point for writing one is my 1722.1 reference C code; I had started an entity model implementation for constrained devices at https://github.com/jdkoftinoff/jdksavdecc-mcu <https://github.com/jdkoftinoff/jdksavdecc-mcu> but it is incomplete. macOS Sierra includes full compliant AVDECC protocol implementation. The default mode will allow you to see compatible AVB Audio devices in the “Audio MIDI Setup” application in the “Network browser” window. But there is more powerful options with the “avbutil” command line tool. To see how to create a virtual AVB audio device and manage streams, run: man avbutil Specifically the “ --virtual-audio enable” and “--controller launch” options are useful! Jeff

…

On Dec 27, 2016, at 11:22, owenfmurphy ***@***.***> wrote: Hello, Is there any tutorial for using the command line program to initialize the machine as an endpoint (acquire entity number, etc)? Currently I have an Ubuntu PC with an I210 PCI card, and I am trying to get it to connect to my AVB network. I have enabled the open-avb drivers, and I am running the open-avb daemons. The rest of the network consists of: (1) Mac Mini (latest OS, AVB compatible ethernet chip) (1) MOTU AVB interface (1) DSP4You OEM AVB endpoint (1) MOTU AVB Switch When I run the command line program, I can see the Mac Mini, the Motu interface, and the endpoint when I type "view all" and "list", but the ubuntu machine does not appear. Is there an command I need to issue that allows the ubuntu machine to connect to the network? There is another strange issue I noticed regarding the mac mini. When I type "view all", none of the parameters for the mac mini show up the way they do for the other endpoints. The streams are available though, because I can connected them to the motu interface using motu's browser based controller. Does anyone know if OS X follows the AVDECC protocol exactly? I am having problems using my mac mini with the switch, so it's possible they don't implement it the protocol properly. I just wanted to see if anyone else had issues, or has any information on the matter. Thanks for the help! Owen — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#323>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAMgDfCHeMrCRll1vIwMrF2K3drummHHks5rMWV3gaJpZM4LWdhi>.

[owenfmurphy]

Thanks for the quick reply, Jeff!

Since Open-AVB does not include entity implementation, does that mean you can only use the prewritten examples with with each other ("simpler_talker" <-> "simple_listener") and not with a standard AVB device ("simple talker" <-> off the shelf AVB interface)?

Thanks for the info on avbutil in OS X. Do you have any idea why the parameters for my Mac don't appear when I use the command "view all" in the avdecccmdline program? Virtual audio entity is enabled, and there is AVB audio data being transferred between the Mac and the interface. But for some reason, I can't see any of the parameters.

When I type "view all", this is what I get this for the DSP4YOU endpoint and MOTU interface:

End Station: 0 (DSP4YOU AVB Dongle) Descriptor Type Descriptor Index Descriptor Name ------------------------------------------------------------------------------
`ENTITY 0 DSP4YOU AVB Dongle
CONFIGURATION 0 Configuration 0

Top Level Descriptors
AUDIO_UNIT 0 Audio Unit 0
STREAM_INPUT 0 Input 0`
etc etc

Only this shows up for the Mac:

End Station: 2 (Owen’s Mac mini) Descriptor Type Descriptor Index Descriptor Name ------------------------------------------------------------------------------

and nothing else.

I have two several other AVDECC programs (Pivitec AVDECC Controller and AudioScience Hono Controller) and both of them also don't show available streams from the Mac.

I have another issue that is unrelated to this software, but I thought maybe you'd have some insight. When I connect my interface directly to the Mac, I am able to use three AVB streams in each direction (the maximum allowed by the interface). When I put a switch in between the Mac and the interface, I can only use one stream. I don't think the switch is the issue, since I've used both a MOTU switch and a DSP4YOU switch, both of which are designed for handling AVB traffic. I talked to the interface manufacturer and they basically said it was on Apple's end, but didn't really clarify. This issue is actually the whole reason I started looking into these open source AVB resources, hoping to figure out the problem. Do you have any idea why that could be? The interface AVB connections on the interface appear to be locked so I can't use this utility to manually connect streams.

Thanks again,
Owen

[jdkoftinoff]

How did you connect the streams between the virtual audio entity and the interface? As for your secondary issue: What are the dimensions of the 3 streams? 48 kHz 8 channel AM824? Jeff

…

On Dec 27, 2016, at 17:42, owenfmurphy ***@***.***> wrote: Thanks for the quick reply, Jeff! Since Open-AVB does not include entity implementation, does that mean you can only use the prewritten examples with with each other ("simpler_talker" <-> "simple_listener") and not with a standard AVB device ("simple talker" <-> off the shelf AVB interface)? Thanks for the info on avbutil in OS X. Do you have any idea why the parameters for my Mac don't appear when I use the command "view all" in the avdecccmdline program? Virtual audio entity is enabled, and there is AVB audio data being transferred between the Mac and the interface. But for some reason, I can't see any of the parameters. When I type "view all", this is what I get this for the DSP4YOU endpoint and MOTU interface: End Station: 0 (DSP4YOU AVB Dongle) Descriptor Type Descriptor Index Descriptor Name ------------------------------------------------------------------------------ `ENTITY 0 DSP4YOU AVB Dongle CONFIGURATION 0 Configuration 0 Top Level Descriptors AUDIO_UNIT 0 Audio Unit 0 STREAM_INPUT 0 Input 0` etc etc Only this shows up for the Mac: End Station: 2 (Owen’s Mac mini) Descriptor Type Descriptor Index Descriptor Name ------------------------------------------------------------------------------ and nothing else. I have two several other AVDECC programs (Pivitec AVDECC Controller and AudioScience Hono Controller) and both of them also don't show available streams from the Mac. I have another issue that is unrelated to this software, but I thought maybe you'd have some insight. When I connect my interface directly to the Mac, I am able to use three AVB streams in each direction (the maximum allowed by the interface). When I put a switch in between the Mac and the interface, I can only use one stream. I don't think the switch is the issue, since I've used both a MOTU switch and a DSP4YOU switch, both of which are designed for handling AVB traffic. I talked to the interface manufacturer and they basically said it was on Apple's end, but didn't really clarify. This issue is actually the whole reason I started looking into these open source AVB resources, hoping to figure out the problem. Do you have any idea why that could be? The interface AVB connections on the interface appear to be locked so I can't use this utility to manually connect streams. Thanks again, Owen — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#323 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAMgDeV02XXM43QJNC-ZzoCrZAzJsgleks5rMb6XgaJpZM4LWdhi>.

[owenfmurphy]

The interface has a web browser based controller that lets you connect streams with pulldown menus. The virtual audio entity streams connected automatically to the interface streams. (In fact they were locked, so I was unable to disconnect them...)

The three streams are 8 channels each at 48kHz, 24-bit depth

[owenfmurphy]

This is the browser based controller

[jdkoftinoff]

I don’t think you actually used the macOS virtual entity; When the mac sees a directly connected AVB interface (without a switch in between) the built in controller in macOS tries to automatically connect all the streams. Run “Audio MIDI Setup” and open the “Network Device Browser” window to see. If you were using your macOS virtual audio entity then you would have had to connect the streams manually via a Controller; either the avdecccmdline tool running on a different computer, or the built in macOS GUI AVB Controller via the cmdline "avbutil --controller launch" Regards, Jeff

…

On Dec 27, 2016, at 19:07, owenfmurphy ***@***.***> wrote: The interface has a web browser based controller that lets you connect streams with pulldown menus. The virtual audio entity streams connected automatically to the interface streams. (In fact they were locked, so I was unable to disconnect them...) The three streams are 8 channels each at 48kHz, 24-bit depth — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#323 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAMgDfOPYfq04i1qBpbmfRdnvFkjpIeNks5rMdKIgaJpZM4LWdhi>.

[owenfmurphy]

Everything looks like it's enabled with the virtual entity. Is there something else to check?

[jdkoftinoff]

No, that is not the virtual entity as created by “avbutil --virtual-audio enable [interface_name]” What you are seeing is the mirror entity that is auto-generated by the mac to match the MOTU device. This device is not controllable by an external controller. What does “avbutil --virtual-audio list” report? And what does “avbutil --controller launch” show? Jeff

…

On Dec 27, 2016, at 19:19, owenfmurphy ***@***.***> wrote: Everything looks like it's enabled with the virtual entity. Is there something else to check? <https://cloud.githubusercontent.com/assets/24628294/21513064/2649c6ec-cc82-11e6-8894-1596931b50c1.png> — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#323 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAMgDZqMeVXc81UAi__m3LjbGtrtum7Tks5rMdVJgaJpZM4LWdhi>.

[owenfmurphy]

Owens-Mac-mini:~ owenfmurphy$ avbutil --virtual-audio list
avbutil 500.19

Virtual Audio Entities enabled on interface(s):
en0

Owens-Mac-mini:~ owenfmurphy$ avbutil --controller launch
avbutil 500.19

[jdkoftinoff]

Ah, ok! I see. At this point with the mac connected to the switch you should be able to enumerate the “Owen’s Mac Mini” entity with the audioscience command line tool. Can you try disconnect the streams via the web interface and try connect them via the audioscience command line tool, or try use the avbutil controller GUI to connect. Jeff

…

On Dec 27, 2016, at 19:29, owenfmurphy ***@***.***> wrote: Owens-Mac-mini:~ owenfmurphy$ avbutil --virtual-audio list avbutil 500.19 Virtual Audio Entities enabled on interface(s): en0 Owens-Mac-mini:~ owenfmurphy$ avbutil --controller launch avbutil 500.19 <https://cloud.githubusercontent.com/assets/24628294/21513203/ddd11800-cc83-11e6-8c80-92443181cae4.png> — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#323 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAMgDQoBfUv2XBC-r7ECTn3wemG3E6LQks5rMdeugaJpZM4LWdhi>.

[owenfmurphy]

The web interface actually won't let me disconnect the streams. They are grayed out and I can't click on them.

When I used another graphical AVDECC tool (AudioScience Hono Controller I believe), it told me the MOTU device was locked, and would not let me unlock it. Is there a way to unlock an AVB device with the command line tool?

[jdkoftinoff]

How exactly did you create the virtual entity?

…

On Dec 27, 2016, at 19:38, owenfmurphy ***@***.***> wrote: The web interface actually won't let me disconnect the streams. They are grayed out and I can't click on them. When I used another graphical AVDECC tool (AudioScience Hono Controller I believe), it told me the MOTU device was locked, and would not let me unlock it. Is there a way to unlock an AVB device with the command line tool? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#323 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAMgDXxvrg1UKG04ApoeHWhKRzWouYobks5rMdmmgaJpZM4LWdhi>.

[owenfmurphy]

It happens automatically. I have a MOTU "discovery app" on the machine that tells you when there is a MOTU device connected. It's possible that the discovery app creates the virtual entity when it detects a MOTU device.

[jdkoftinoff]

Right, so this is not the virtual entity that can be controlled by an external controller. First step is to use a switch. Second step is to de-select MOTU from the Audio MIDI setup window (to un-acquire it). Third step is to create a virtual entity manually with the avbutil command. Fourth step is to use an external controller (either the avbutil controller running locally on the Mac or avdecccmdline tool running on a separate linux box) to enumerate the entities and connect the streams. Jeff

…

On Dec 27, 2016, at 19:45, owenfmurphy ***@***.***> wrote: It happens automatically. I have a MOTU "discovery app" on the machine that tells you when there is a MOTU device connected. It's possible that the discovery app creates the virtual entity when it detects a MOTU device. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#323 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAMgDUY2k0YsKD8NbFgz0Fu--vYEgvnrks5rMds9gaJpZM4LWdhi>.

[owenfmurphy]

Ok great! I performed steps 1-3 and managed to disconnect the all the streams. How do I enumerate the entities and connect the streams using avbutil and/or avdecccmdline (I have the ability to do both)