The officially official Devuan Forum!

igorzwx

Member

Registered: 2024-05-06

Posts: 370  

Re: [HowTo] audacious_4.5-devel-1_amd64.deb (meson+samu and muon+samu)

Try to play .dsf with Audacious

Free samples are available
_https://dev1galaxy.org/viewtopic.php?id=6716

$ audacious 2>&1 *.dsf
Input:  1411200 Hz, 2 ch, 's32_le' (0xa): dummy = 0, period = 56448
Output: 48000 Hz, 2 ch, 's16_le' (0x2): dummy = 0, period = 1920
Rates:  1411200 --> 48000 (J: 0.00%, T: FFT, W: Vorbis)
Ok.

Last edited by igorzwx (Yesterday 20:13:10)

kapqa

Member

Registered: 2019-01-02

Posts: 522  

Re: [HowTo] audacious_4.5-devel-1_amd64.deb (meson+samu and muon+samu)

don't think this work with DAC > this one only 24b/192.000
another one accepts up to the same but output/upsample to 32b/384.000?

maybe internal HD Intel/AMD can play 32b .dsf? i doubt it;

will have to wait for a better soundbard, probably.

EDIT

audacious 2>&1 08-Faust\ -\ Funeral\ March\ Of\ A\ Marionette\ -\ 24bit.flac 
ERROR ../audacious-plugins/src/alsa/config.cc:238 [guess_element]: No suitable mixer element found.
Input:  352800 Hz, 2 ch, 's32_le' (0xa): dummy = 0, period = 14112
Output: 192000 Hz, 2 ch, 's32_le' (0xa): dummy = 0, period = 7680
Rates:  352800 --> 192000 (J: 0.00%, T: FFT, W: Vorbis)
Ok.

audacious 2>&1 08-Faust\ -\ Funeral\ March\ Of\ A\ Marionette\ -\ 32bit.wav 
ERROR ../audacious-plugins/src/alsa/config.cc:238 [guess_element]: No suitable mixer element found.
Input:  352800 Hz, 2 ch, 's32_le' (0xa): dummy = 0, period = 14112
Output: 192000 Hz, 2 ch, 's32_le' (0xa): dummy = 0, period = 7680
Rates:  352800 --> 192000 (J: 0.00%, T: FFT, W: Vorbis)
Ok.

audacious 2>&1 08-Faust\ -\ Funeral\ March\ Of\ A\ Marionette\ -\ DSD256.dsf 
ERROR ../audacious-plugins/src/alsa/config.cc:238 [guess_element]: No suitable mixer element found.
WARNING ../audacious-plugins/src/ffaudio/ffaudio-core.cc:207 [dsf]: <0x7f32000cb680> Estimating duration from bitrate, this may be inaccurate
WARNING ../audacious-plugins/src/ffaudio/ffaudio-core.cc:207 [dsf]: <0x7f32000cb680> Estimating duration from bitrate, this may be inaccurate
Input:  1411200 Hz, 2 ch, 's32_le' (0xa): dummy = 0, period = 56448
Output: 192000 Hz, 2 ch, 's32_le' (0xa): dummy = 0, period = 7680
Rates:  1411200 --> 192000 (J: 0.00%, T: FFT, W: Vorbis)
Ok.

audacious 2>&1 08-Faust\ -\ Funeral\ March\ Of\ A\ Marionette\ \[Tuncated\,\ No\ Dither\].flac 
ERROR ../audacious-plugins/src/alsa/config.cc:238 [guess_element]: No suitable mixer element found.
Input:  352800 Hz, 2 ch, 's32_le' (0xa): dummy = 0, period = 14112
Output: 192000 Hz, 2 ch, 's32_le' (0xa): dummy = 0, period = 7680
Rates:  352800 --> 192000 (J: 0.00%, T: FFT, W: Vorbis)
Ok.

Last edited by kapqa (Yesterday 20:47:19)

igorzwx

Member

Registered: 2024-05-06

Posts: 370  

Re: [HowTo] audacious_4.5-devel-1_amd64.deb (meson+samu and muon+samu)

Everything works, fftrate can resample everything

I had already explained you that 24bit means 32bit in this particular case

The 32-bit representation serves as a larger, more flexible "container" to preserve the higher precision of the 24-bit data and prevent clipping during internal mixing or editing, especially in professional digital audio workstations (DAWs). The 24-bit data is stored within the 32-bit format, ensuring its precision is maintained without needing resampling.

Why 32-bit is Used as a Container
DAWs and audio servers use 32-bit internally to avoid the complexities of dithering and exporting to fixed-point formats like 24-bit...
When 24-bit integer data is stored in a 32-bit container, the 24-bit precision is preserved within the larger format, similar to storing a number like 0100 in a longer string of zeros, like 00000100.

...the data buffers which these descriptors define will contain the actual sound samples (or have samples written into them) structured like the content of .wav files (though 20 and 24-bit samples must be padded out with zeros at the LSB end to make them all 32-bits long).
_https://wiki.osdev.org/Intel_High_Definition_Audio

Everything works, fftrate can resample everything

You still have a problem with pulseaudio:

ERROR ../audacious-plugins/src/alsa/config.cc:238 [guess_element]: No suitable mixer element found.

Read this thread
_https://www.linuxquestions.org/questions/linux-software-2/alsa-error-no-suitable-mixer-element-found-and-can%27t-connect-to-pulseaudio-4175623535/

_https://www.linuxquestions.org/questions/linux-software-2/alsa-error-no-suitable-mixer-element-found-and-can%27t-connect-to-pulseaudio-4175623535/#post5818488
The issue was permission-based. I logged into x as root briefly and pavucontrol opened with no problem, as did Audacious.

So I then went to my user account and tried, as my user name

chown -R lysander /home/lysander

It told me that there are quite a few folders not owned by me, but by root. One of them was /home/lysander/.config/pulse, whose ownership changed to root around the time I was doing the install of alsaequal.

I changed the ownership to my user whilst inside the folder with

#chown -R lysander pulse

Now pavucontrol opens fine and Audacious doesn't show any errors.

I should be careful in the future with installions and using root.

lysander - is the username of that person,

chown means change ownership

Last edited by igorzwx (Yesterday 21:46:48)

kapqa

Member

Registered: 2019-01-02

Posts: 522  

Re: [HowTo] audacious_4.5-devel-1_amd64.deb (meson+samu and muon+samu)

getting error but it seems benigne

chown -R rich /home/rich
chown: cannot read directory '/home/rich/.local/share/containers/storage/overlay/c69cfad00e0494e0583d81f403c86b24ca668638f0ad98dfc7b5c91af4f274a4/work/work': Permission denied
chown: cannot read directory '/home/rich/.local/share/containers/storage/overlay/3a449042a448f8f26b071123d4169c8335065e21687488c1f7b2c8a6faf8b615/work/work': Permission denied
chown: cannot read directory '/home/rich/.local/share/containers/storage/overlay/05e375d18aa1adb9d18d33112253d319f5df02cc7fe6cbba917e4da665055fe8/work/work': Permission denied
chown: cannot read directory '/home/rich/.local/share/containers/storage/overlay/4523f8c8574bf58b45c8e3c1537e46103e73d68701e4c432f11366bcc92e32c5/work/work': Permission denied

maybe it is because of DAC; it has no volume knob;

thank you so much;
good night.

Last edited by kapqa (Yesterday 22:03:58)

igorzwx

Member

Registered: 2024-05-06

Posts: 370  

Re: [HowTo] audacious_4.5-devel-1_amd64.deb (meson+samu and muon+samu)

you have a container installed in your home folder, which you are not allowed to read

chown: cannot read directory '/home/rich/.local/share/containers/storage/overlay/.../work/work': Permission denied

Install mc, navigate to that container and check who is owner, which permissions

➤ apt show mc
Package: mc
...
Homepage: https://www.midnight-commander.org
...
Description: Midnight Commander - a powerful file manager
...

Do you have a sort of Podman installed?

Last edited by igorzwx (Yesterday 23:16:11)

kapqa

Member

Registered: 2019-01-02

Posts: 522  

Re: [HowTo] audacious_4.5-devel-1_amd64.deb (meson+samu and muon+samu)

yes, i may have botched the linux install by evoking some commands during "boinc" install

like

sudo usermod --add-subuids 100000-165535 --add-subgids 100000-165535 boinc

but there is no de-installation routine offered (for podman); it functioned well on devuan 5.0, but now will try to uninstall.
https://boinc.berkeley.edu/linux_instal … ild=stable

maybe the error (so suitable mixer) because during audacious there were two "red flags" for jack; and i let the install go through nevertheless?

Last edited by kapqa (Today 10:24:54)