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

a52 plugin not working with PipeWire #37

Open
sjnewbury opened this issue Oct 21, 2021 · 4 comments
Open

a52 plugin not working with PipeWire #37

sjnewbury opened this issue Oct 21, 2021 · 4 comments

Comments

@sjnewbury
Copy link

sjnewbury commented Oct 21, 2021

Using the lastest code since v1.2.5 I can successfully get AC3 output through HDMI when using speaker-test. Defaults use a huge buffer and gives terrible latency, but it works.

PulseAudio also works fine with fairly low-latency using "tsched=1 tsched_buffer_size=32768 tsched_buffer_watermark=8192 fixed_latency_range=yes mmap=1". This doesn't need the rate kludge any more.

When I try pipewire using mmap I get the below messages in the log, no audio:

spa.alsa: alsa-pcm a52hdmi: mmap_commit wrote 512 instead of 1024

With mmap disabled, no errors are reported, but still no sound.

Is there a configuration for pipewire which works with the a52 plugin, a pipewire bug, or is this another a52 plugin bug?

@sjnewbury
Copy link
Author

sjnewbury commented Oct 21, 2021

Another issue with a52/pipewire which also applies to PulseAudio, is the a52 plugin doesn't support config functions for the slavepcm which makes it impossible to have automatically generated profiles for AC3 output. WIth the dca plugin, just adding confdir:pcm/dca.conf to asound.conf makes DTS profiles selectable from pavucontrol.

perexg added a commit to perexg/alsa-plugins that referenced this issue Nov 2, 2021
Make Pulseaudio and PipeWire to find the A52 devices.

BugLink: alsa-project#37
Signed-off-by: Jaroslav Kysela <[email protected]>
@perexg
Copy link
Member

perexg commented Nov 2, 2021

Another issue with a52/pipewire which also applies to PulseAudio, is the a52 plugin doesn't support config functions for the slavepcm which makes it impossible to have automatically generated profiles for AC3 output. WIth the dca plugin, just adding confdir:pcm/dca.conf to asound.conf makes DTS profiles selectable from pavucontrol.

Can you test this config ? perexg@9a74090

@perexg
Copy link
Member

perexg commented Nov 2, 2021

When I try pipewire using mmap I get the below messages in the log, no audio:

spa.alsa: alsa-pcm a52hdmi: mmap_commit wrote 512 instead of 1024

This should be probably harmless, but yes, it appears like another minor issue in the a52 plugin. I suspect that the end PCM device does not consume the samples in the right time.

Is there a configuration for pipewire which works with the a52 plugin, a pipewire bug, or is this another a52 plugin bug?

You may try to enable the debug log level in PW and check the input from PW to the plugin.

@DocMAX
Copy link

DocMAX commented Aug 3, 2024

how did you set up a52 on pipewire?

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