Skip to content
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

Channel List Not Displaying All Channels #27

Open
muzicman82 opened this issue Oct 18, 2024 · 7 comments
Open

Channel List Not Displaying All Channels #27

muzicman82 opened this issue Oct 18, 2024 · 7 comments

Comments

@muzicman82
Copy link

Hi, I have a Yamaha Rio3224-D2 and when I list channels, the list stops at RX channel 16 and there are 24. As a result, I can't issue commands to the channels that netaudio doesn't see.

Suggestions?

@chris-ritsen
Copy link
Owner

OK, yeah I definitely haven't tested with that device. I'm going to guess it uses a Audinate Dante Brooklyn II. I have a Shure AD4D, which also uses one. I mention this because it's the only device where I had weird reported channel counts that I had to find workarounds for to get the actual count. What kind of settings do you have on the device (specifically, the sample rate)? But anyway, without packet captures of the device responding to commands to list the channels/subscriptions, I'm not going to know what's going on with it enough to fix it.

@muzicman82
Copy link
Author

Hey! I can get you whatever packet captures you need. I posted on the Gearspace thread about my latest progress. I'm very interested in how you got the long commands out of Dante Controller reduced by several bytes.

It does use a Brooklyn II.

@chris-ritsen
Copy link
Owner

chris-ritsen commented Oct 18, 2024

Maybe I could come up with a workaround. The channel request command is split up into pages, but you could go out of bounds with the page index on requests until it errors. I'm checking for device reported channel counts and sample rate to calculate how many pages there should be and only doing that. In my case, the device reports more channels than it actually has.

@muzicman82
Copy link
Author

Interesting. What should I capture for you that might help? I may be able to get your AnyDesk acess to the system if you want to mess with it directly.

@chris-ritsen
Copy link
Owner

chris-ritsen commented Oct 19, 2024

I responded on gearspace. All I would need would be the responses to these two:

Channel count query: 27ff000aad5d10000000
Get receiver info: 27ff0010732a20100000000100010000

That receiver info command has an argument which determines the page being requested. My get_rx_channels function has this loop:

for page in range(0, max(int(self.device.rx_count / 16), 1)):

Max per page in the response is always 16 channels. So if it's not trying to get the second page, then the channel count query is responding with something weird. Would be helpful to know the sample rate you're using, as it affects channel count and I haven't tested that much with anything other than 48K.

@doughecka
Copy link

I've got access to Brooklyn 2 and 3 modules (and Ultimo/ultimox & DEP) ... One of the BKII modules has 64 channels. 😁 I should be able to test multiple samples rates as well.

I've not tried using this project before, so I'll need to get up to speed on how to use it.

@chris-ritsen
Copy link
Owner

chris-ritsen commented Oct 19, 2024

The only real way I'm going to support every device with this project is to add some optional debug logging that gets reported somewhere I can see. Haven't even thought about how that's going to happen. There's no way I could ever personally test all of these expensive devices.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants