Thank you for your donation!


Cloudsmith graciously provides open-source package management and distribution for our project.


Issue with oversampling. AirPlay plugin
#1
Hello!

Starting from version 9, problems began with AirPlay plugin, glitches occur periodically, and randomly, but there is already a separate thread about this.

I don’t know if this is specifically my problem or a general one, but if I select any other value instead of 32 bits, there is no sound. Sound appears only at 32 bits and any sampling rate. I checked on all file formats (16 bit, 24 bit) from local disk that the problem is not related to my sound card.

The option to completely disable the oversampling algorithm has also disappeared; perhaps it wasn’t there before, I didn’t notice.

Thank you.
Reply
#2
What audio device are you using?
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
Reply
#3
(09-18-2024, 08:10 PM)Tim Curtis Wrote: What audio device are you using?

I am using Combo 384 Amanero USB.
RPi 4b
Reply
#4
The Amenero probably only accepts 32-bit word length.
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
Reply
#5
(09-18-2024, 09:42 PM)Tim Curtis Wrote: The Amenero probably only accepts 32-bit word length.

This is weird. After all, in version 8 everything was fine. And also files of any bit depth and frequency play on this sound card.

Specifications of the card:
PCM: 16/24/32 bit; 44,1/48/88,2/96/176,4/192/352,8/384 kHz
DSD: 64/128/256
Reply
#6
In the Audio configuration section of the startup log"Audio formats:" lists the supported bit depths for the attached device. You can also use moodeutl -f
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
Reply
#7
(09-19-2024, 10:26 AM)Tim Curtis Wrote: In the Audio configuration section of the startup log"Audio formats:" lists the supported bit depths for the attached device. You can also use moodeutl -f

moodeutl -f indicates
S32_LE, DSD_U32_LE

Doesn't this mean maximum values? Thank you!


Attached Files Thumbnail(s)
   
Reply
#8
(09-19-2024, 11:48 AM)svitalya Wrote:
(09-19-2024, 10:26 AM)Tim Curtis Wrote: In the Audio configuration section of the startup log"Audio formats:" lists the supported bit depths for the attached device. You can also use moodeutl -f

moodeutl -f indicates
S32_LE, DSD_U32_LE

Doesn't this mean maximum values? Thank you!

Not maximum bit depths but each individual bit depth that ALSA detects.

Here's an example from a system that has an Allo Boss DAC.
Code:
pi@moode9:~ $ moodeutl -f
S16_LE, S24_LE, S32_LE

The underlying command thats used by moodeutl is below.
Code:
alsacap

#Example from system with Boss DAC

pi@moode9:~ $ alsacap
*** Scanning for playback devices ***
Card 0, ID `vc4hdmi0', name `vc4-hdmi-0'
  Device 0, ID `MAI PCM i2s-hifi-0', name `MAI PCM i2s-hifi-0', 1 subdevices (1 available)
Error opening sound device for card 0, device 0: Unknown error 524.  Skipping.
Card 1, ID `vc4hdmi1', name `vc4-hdmi-1'
  Device 0, ID `MAI PCM i2s-hifi-0', name `MAI PCM i2s-hifi-0', 1 subdevices (1 available)
Error opening sound device for card 1, device 0: Unknown error 524.  Skipping.
Card 2, ID `BossDAC', name `BossDAC'
  Device 0, ID `Boss DAC HiFi [Master] pcm512x-hifi-0', name `Boss DAC HiFi [Master] pcm512x-hifi-0', 1 subdevices (1 available)
    2 channels, sampling rate 8000..384000 Hz
    Sample formats: S16_LE, S24_LE, S32_LE
    Buffer size range from 8 to 131072
    Period size range from 4 to 65536

      Subdevice 0, name `subdevice #0'
pi@moode9:~ $ 
 
Most modern USB receivers for example XMOS only accept 32 bit word length. Linux/ALSA simply zero-pads lower bit depths to 32. This operation preserves the original bits and is completely transparent when the samples are processed by the audio device.
Enjoy the Music!
moodeaudio.org | Mastodon Feed | GitHub
Reply
#9
(09-19-2024, 11:58 AM)Tim Curtis Wrote:
(09-19-2024, 11:48 AM)svitalya Wrote:
(09-19-2024, 10:26 AM)Tim Curtis Wrote: In the Audio configuration section of the startup log"Audio formats:" lists the supported bit depths for the attached device. You can also use moodeutl -f

moodeutl -f indicates
S32_LE, DSD_U32_LE

Doesn't this mean maximum values? Thank you!

Not maximum bit depths but each individual bit depth that ALSA detects.

Here's an example from a system that has an Allo Boss DAC.
Code:
pi@moode9:~ $ moodeutl -f
S16_LE, S24_LE, S32_LE

The underlying command thats used by moodeutl is below.
Code:
alsacap

#Example from system with Boss DAC

pi@moode9:~ $ alsacap
*** Scanning for playback devices ***
Card 0, ID `vc4hdmi0', name `vc4-hdmi-0'
  Device 0, ID `MAI PCM i2s-hifi-0', name `MAI PCM i2s-hifi-0', 1 subdevices (1 available)
Error opening sound device for card 0, device 0: Unknown error 524.  Skipping.
Card 1, ID `vc4hdmi1', name `vc4-hdmi-1'
  Device 0, ID `MAI PCM i2s-hifi-0', name `MAI PCM i2s-hifi-0', 1 subdevices (1 available)
Error opening sound device for card 1, device 0: Unknown error 524.  Skipping.
Card 2, ID `BossDAC', name `BossDAC'
  Device 0, ID `Boss DAC HiFi [Master] pcm512x-hifi-0', name `Boss DAC HiFi [Master] pcm512x-hifi-0', 1 subdevices (1 available)
    2 channels, sampling rate 8000..384000 Hz
    Sample formats: S16_LE, S24_LE, S32_LE
    Buffer size range from 8 to 131072
    Period size range from 4 to 65536

      Subdevice 0, name `subdevice #0'
pi@moode9:~ $ 
 
Most modern USB receivers for example XMOS only accept 32 bit word length. Linux/ALSA simply zero-pads lower bit depths to 32. This operation preserves the original bits and is completely transparent when the samples are processed by the audio device.

Now I understand. Thank you for your patience!
Reply


Forum Jump: