Audio output over HDMI #7

Open
opened 2026-08-11 05:09:44 +00:00 by gerry · 6 comments
Owner

At COSCUP the idea was to hook up their own recording solution behind ours, and we'd just send them a copy of what we mixed. For audio, this was a bit of an issue, as they were counting on having the audio embedded into what we feed out of the HDMI.

At COSCUP the idea was to hook up their own recording solution behind ours, and we'd just send them a copy of what we mixed. For audio, this was a bit of an issue, as they were counting on having the audio embedded into what we feed out of the HDMI.
Owner

Some notes on what was done until now:

The quickest/easiest thing that I was able to look into was to use dsnoop devices and then alsaloop from the audiomixer to the audio device of the HDMI output. It seemed to work, but we were not able to verify it.

Doing this in the ffmpeg in sink.sh would induce too large a latency. We did not test this, though.

We do not seem to have a way to wire the mixer into the radxa to do this directly.

Some notes on what was done until now: The quickest/easiest thing that I was able to look into was to use `dsnoop` devices and then `alsaloop` from the audiomixer to the audio device of the HDMI output. It seemed to work, but we were not able to verify it. Doing this in the `ffmpeg` in `sink.sh` would induce too large a latency. We did not test this, though. We do not seem to have a way to wire the mixer into the radxa to do this directly.
Owner

Also note that this MUST be configurable, otherwise this would create feedback loops in a lot of places, as so many projectors and screens have some kind of built-in sound.

Also note that this MUST be configurable, otherwise this would create feedback loops in a lot of places, as so many projectors and screens have some kind of built-in sound.
Member

I got the latency down to about 5ms with pipewire, but this is on top of whatever the HDMI receiver gives and the USB buffering, so realistically it is about 25ms which is a lot

I got the latency down to about 5ms with pipewire, but this is on top of whatever the HDMI receiver gives and the USB buffering, so realistically it is about 25ms which is a lot
Owner

25ms is 8.2m distance, which should be livable/acceptable, I've played guitar with that latency. We should test.

25ms is 8.2m distance, which should be livable/acceptable, I've played guitar with that latency. We should test.
Author
Owner

Slap me if I'm wrong; but isn't the part of the latency we actually care about the difference between the video and audio over HDMI? The video already has some latency, as long as the audio is in sync with that, we should be good? From what I understand, that would be 5ms which I guess is pretty much in sync?

Slap me if I'm wrong; but isn't the part of the latency we actually care about the difference between the video and audio over HDMI? The video already has some latency, as long as the audio is in sync with that, we should be good? From what I understand, that would be 5ms which I guess is pretty much in sync?
Member

If the HDMI audio gets used for PA then the absolute latency also matters. Like the COSCUP setup.

If the HDMI audio gets used for PA then the absolute latency also matters. Like the COSCUP setup.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
4 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
video/fazantix#7
No description provided.