12-29-2018, 11:26 AM
Si je comprends bien (ce qui est loin d'être sûr), il y a 2 types de buffers :
* celui utilisé par Squeezelite (pour les traitements de type codage, échantillonnage...) avant envoi du flux à ALSA
* celui dans ALSA pour la sortie audio.
Ils ne se paramètrent pas au même endroit et pas avec les mêmes unités.
Dans son blog https://soundcheck-audio.blogspot.com/20...art-2.html donne plutôt les valeurs suivantes. Avez-vous essayé ?
"3. Alsa setting
The chosen buffer value of "65536" (=2^16) bits will be divided into "4" chunks (=periods)
For USB DACs you might want to try "160" instead.
The 3rd field - if empty - lets Alsa decide what bitdepth towards the DAC to choose.
Most modern dacs and HAT dacs run usually 32bit.
MMAP allows squeezelite to access the device memory directly
4. Buffer size settings
These shouldn't be mixed up with the Alsa buffer settings.
There are two buffers we're looking at.
1. The stream buffer
2. The output buffer (output from squeezelite to Alsa!)
squeezelite puts the received audio data into the stream buffer first.
The internal processing stages e.g. flac-pcm conversion, resampling or
volume control will then be executed and the result gets stored in the output buffer.
Data will be stored at 32bit in that output buffer.
If you look at below setup proposal, you'll see 20000:500000.
That means we look at a 20MBytes stream buffer and a 500MB output buffer.
What happens is that squeezelite reads and processes the entire file
as soon as you push the start button. You'll see a high peak load
in the first couple of seconds of playback and then the fully processed file
is played back from a RAM buffer. A typical CPU load will be below 1%."
* celui utilisé par Squeezelite (pour les traitements de type codage, échantillonnage...) avant envoi du flux à ALSA
* celui dans ALSA pour la sortie audio.
Ils ne se paramètrent pas au même endroit et pas avec les mêmes unités.
Dans son blog https://soundcheck-audio.blogspot.com/20...art-2.html donne plutôt les valeurs suivantes. Avez-vous essayé ?
"3. Alsa setting
The chosen buffer value of "65536" (=2^16) bits will be divided into "4" chunks (=periods)
For USB DACs you might want to try "160" instead.
The 3rd field - if empty - lets Alsa decide what bitdepth towards the DAC to choose.
Most modern dacs and HAT dacs run usually 32bit.
MMAP allows squeezelite to access the device memory directly
4. Buffer size settings
These shouldn't be mixed up with the Alsa buffer settings.
There are two buffers we're looking at.
1. The stream buffer
2. The output buffer (output from squeezelite to Alsa!)
squeezelite puts the received audio data into the stream buffer first.
The internal processing stages e.g. flac-pcm conversion, resampling or
volume control will then be executed and the result gets stored in the output buffer.
Data will be stored at 32bit in that output buffer.
If you look at below setup proposal, you'll see 20000:500000.
That means we look at a 20MBytes stream buffer and a 500MB output buffer.
What happens is that squeezelite reads and processes the entire file
as soon as you push the start button. You'll see a high peak load
in the first couple of seconds of playback and then the fully processed file
is played back from a RAM buffer. A typical CPU load will be below 1%."
Système : Teac UD701N > Brinkmann > PeLeon Caprice
A vendre (MP) : tubes NOS-NIB (6B4G black bottle - 1 KenRad, 1 Hudson - et 2 x Mullard GZ37), paire de 6B4G Sovtek neufs, paire de 6SN7 JAN CKR VT231
A vendre (MP) : tubes NOS-NIB (6B4G black bottle - 1 KenRad, 1 Hudson - et 2 x Mullard GZ37), paire de 6B4G Sovtek neufs, paire de 6SN7 JAN CKR VT231