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

Distorted audio on mono and 32 kHz sampled DAB stations #384

Open
orryverducci opened this issue May 26, 2024 · 2 comments
Open

Distorted audio on mono and 32 kHz sampled DAB stations #384

orryverducci opened this issue May 26, 2024 · 2 comments

Comments

@orryverducci
Copy link

Describe the bug
Tuning in to DAB stations that broadcast either mono audio or audio using a 32 kHz sample rate results in distorted audio playback. Mono stations have stuttery audio, as if samples are regularly missing. 32 kHz stations play sped up and then drop out.

To Reproduce
Tune in to the frequency of a DAB multiplex containing a mono or 32 kHz samples station. Enable the DAB decoder, then select a mono or 32 kHz sampled station form the program list.

Expected behavior
Clean audio playback, as experienced when listening to a 48 kHz stereo DAB station.

Installation method
Docker image on a Raspberry Pi 4.

Versions
Latest tagged Docker image.

Log messages
None

Additional context
Mono and 32 kHz sampled stations are common in the UK, so many stations received from the UK DAB multiplexes are affected.

@jketterl
Copy link
Owner

Yeah this has been confirmed on the mailing list before. Basically, as of now the audio data coming out of dablin is unqualified, and the best (most common) option is to interpret them as 48kHz stereo. There has been work on dablin towards adding a header (Opendigitalradio/dablin#74) but this still needs to be integrated. See also #155 for some additional information.

At least we finally have an issue now ;)

@orryverducci
Copy link
Author

Thanks for the additional context. I did search through the mailing list but somehow missed this, so that's useful to know.

It's good to see that the dablin team are making changes to provide this information.

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

2 participants