-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
compatible devices #40
Comments
I didn't elaborate such a list. I created the project for fun and I own just a bunch of devices. |
yes of course, I understand. RJD32A3-0050 |
Apparently no one has ever tested with this device. Since it looks like it's compatible with Dante you can give it a try ;-) |
@bondagit we tried at a friend's and they seem to work. But one thing I don't understand, aes67 has a 48Hz frequency limit? |
Dante has a 48k limit in AES67 mode. AES has options to support 96 or even more, but no obligation to do so. |
The daemon is not limited to 48Khz but the sample rate configuration is a global setting.
|
Which device do you use to get AES67 sound at 96khz ??? |
Two deamons on two different boards or via loopback test (platform test) |
Ok. I understand. Then it seems that "Dante seems to support L24 / 48Khz only in AES67 mode" is confirmed with my Dante device. |
Hi, Thanks for the implementation |
Thanks for your message. The daemon and the driver don't limit the usable DSCP values, so adding more values is just a matter of patching the WebUI. I will do that soon. Thanks for the suggestion and for sharing your results. |
Is this daemon implementation fully compatible with Ravenna? As per the other issue, now closed, I have confirmed AES67 interoperability with Dante in my system, but I do not see any Ravenna transmit/receive channels available for mapping using the ANEMAN utility. The AES67 Daemon device does show up in the device list. |
I have tested the Ravenna implementation in the daemon with the Merging Butler and with the Hasseb audio receiver.
If this the case, |
Avahi support is enabled, and the messages are displayed properly on daemon startup. I am seeing mDNS announcements on WireShark. Could be that ANEMAN supports only specific manufacturers' Ravenna devices. Will seek an alternate way to test. Thanks! |
Hi,
Indeed ANEMAN support is manufacturer specific. Although I have no time for the support myself, the SDK is free, open and I can coach anyone willing to try to code it.
—
Nicolas Sturmel
… Le 3 déc. 2021 à 20:14, synapse-md ***@***.***> a écrit :
Avahi support is enabled, and the messages are displayed properly on daemon startup. I am seeing mDNS announcements on WireShark.
Could be that ANEMAN supports only specific manufacturers' Ravenna devices. Will seek an alternate way to test.
Thanks!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Hello @nicolassturmel, I would like to give this a try. |
Hi,
Sorry for the late reply.
I checked three times, you should have a read only access (it's open to
everyone),
For further coaching (in 2022 ;) ), we can have a talk: skype, whatsapp,
meet... choose your GAFAM privacy intrusion tool
Basically, the idea is a data formatting endpoint: it is a C++ plugin for
ANEMAN that connects to the device (the driver on your linux) and builds a
JSON tree. It is expected for the plug-in to respond to some actions as
well (create receiver, create sender etc...)
If you write it multiplatform (I encourage you to do so), I can put it in
the compilation for every release. So choose a LGPL or other permissive
license please.
N.
Le lun. 13 déc. 2021 à 03:00, Alexander M. ***@***.***> a
écrit :
… Hi, Indeed ANEMAN support is manufacturer specific. Although I have no
time for the support myself, the SDK is free, open and I can coach anyone
willing to try to code it. — Nicolas Sturmel
Hello @nicolassturmel <https://github.com/nicolassturmel>,
I would like to give this a try.
The link for the SDK on the ANEMAN page points to a private Google Drive
file
<https://drive.google.com/drive/folders/0B5BM-5YFliDiLU1kOGtrVlFYNlk?usp=sharing>
.
I've requested access but would be grateful to receive any further
coaching on this.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#40 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AET6KZUQ7C3R3AUO56WWLK3UQVHTLANCNFSM444YSANQ>
.
|
Yamaha MY16-2 does not seem to acccept connections from AES67 source. Connection to DANTE AVIO seems to work (have not listened to it but green Icons do show). Are there any settings I can provide? TIC frame size is 48 (1 ms). Edit: I got it to work by assigning the RTP Address to the source. manually. This might be an important hint. |
Is there a list of compatible devices, i.e. tested and working with aes67 daemon?
The text was updated successfully, but these errors were encountered: