To eliminate the influence of the platform and processor launched wtfplay on the 775 platform (core2duo). The result has not changed. Problem in audio driver
Attachments
Not the problem with the driver. Just as phofman says - the driver is it picky about the parameters.
Basically, it looks like RME96 requires parameters to match a fixed audio buffer of 64KB. Furthermore, the period size is limited to two values: 2KB and 8KB. Hopefully I am reading the code right.
If we take those constraints and convert them into frames then we would get:
For 16bit stereo frame size is 4 bytes, so we would get:
period size = 512, period count = 32, or
period size = 2048, period count = 8
For 24 bit stereo the frame size is 8 bytes (RME uses S32_LE for that) and then we would get:
period size = 256, period count = 32, or
period size = 1024, period count = 8
Or I missed something
Please try passing the above parameters player:
Please note that the default number of periods in wtfplay is 3. I still do not know how a WAV file could be played while FLAC could not.
F
Basically, it looks like RME96 requires parameters to match a fixed audio buffer of 64KB. Furthermore, the period size is limited to two values: 2KB and 8KB. Hopefully I am reading the code right.
If we take those constraints and convert them into frames then we would get:
For 16bit stereo frame size is 4 bytes, so we would get:
period size = 512, period count = 32, or
period size = 2048, period count = 8
For 24 bit stereo the frame size is 8 bytes (RME uses S32_LE for that) and then we would get:
period size = 256, period count = 32, or
period size = 1024, period count = 8
Or I missed something
Please try passing the above parameters player:
Code:
wtfplay -d hw:0 -f 2048 -n 8 /pah/to/your/16bit_audio.flacPlease note that the default number of periods in wtfplay is 3. I still do not know how a WAV file could be played while FLAC could not.
F
Last edited:
Not the problem with the driver. Just as phofman says - the driver is it picky about the parameters.
Basically, it looks like RME96 requires parameters to match a fixed audio buffer of 64KB. Furthermore, the period size is limited to two values: 2KB and 8KB. Hopefully I am reading the code right.
If we take those constraints and convert them into frames then we would get:
For 16bit stereo frame size is 4 bytes, so we would get:
period size = 512, period count = 32, or
period size = 2048, period count = 8
For 24 bit stereo the frame size is 8 bytes (RME uses S32_LE for that) and then we would get:
period size = 256, period count = 32, or
period size = 1024, period count = 8
Or I missed something
Please try passing the above parameters player:
Code:wtfplay -d hw:0 -f 2048 -n 8 /pah/to/your/16bit_audio.flac
Please note that the default number of periods in wtfplay is 3. I still do not know how a WAV file could be played while FLAC could not.
F
With these parameters I heard a sound!
many thanks! I listen carefully and compare with the cmp2 project
Last edited:
frd__: Typically alsa players adjust the requested period/buffer values with the xxx_near alsalib calls to make sure the pcm device will accept the hw params. E.g. sox/alsa.c at master * jacksonh/sox * GitHub , mpv/ao_alsa.c at master * mpv-player/mpv * GitHub , MPD/HwSetup.cxx at 256cfc545ddf05ed72784922f3ec038da6747032 * MusicPlayerDaemon/MPD * GitHub
Or the plug plugin is used (e.g. hardcoded in java alsa plugin ).
Or the plug plugin is used (e.g. hardcoded in java alsa plugin
).Hi frd_ .
On my setup, using 0.7.3-core2 version, typing "alsamixer" the answer now is:
"cannot open mixer: No such file or directory". It is not a problem for me, I want only report it to you.
Another feedback:
I like this new version, but I notice that on my setup it appears maybe too much "brite" (I use wtfplay-dsd). So I have restored priority "60", and in my case I think it is better balanced.
Thanks again !
On my setup, using 0.7.3-core2 version, typing "alsamixer" the answer now is:
"cannot open mixer: No such file or directory". It is not a problem for me, I want only report it to you.
Another feedback:
I like this new version, but I notice that on my setup it appears maybe too much "brite" (I use wtfplay-dsd). So I have restored priority "60", and in my case I think it is better balanced.
Thanks again !
You can run console version of Album Player v2.05 with full cue support under Wtfplay OS.
You can read @bodiebill's opinion at AS forum thread (wtfplay - Page 18 - Software - Audiophile Style), post #448.
@frd, could you please add 2 more controls in wtfcui:
1. one key ('C' for instance) : clear the playlist
2. one key ( doesn't matter witch one ) : when pressed on a selected Folder will add to playlist all files from that folder non -recursive. A shortcut for <Enter><Shift+A><Enter>. I usually listen to full albums and I know what files are inside the album folder
1. one key ('C' for instance) : clear the playlist
2. one key ( doesn't matter witch one
) : when pressed on a selected Folder will add to playlist all files from that folder non -recursive. A shortcut for <Enter><Shift+A><Enter>. I usually listen to full albums and I know what files are inside the album folder Sorry for late response.
Thanks for the suggestions regarding the keys in wtfcui. Adding the content of the directory to the playlist without going inside will be pretty easy do do. <Shift+D>?
In terms of making the keys configurable - this is going to be more complex as it requires a bit of refactoring. Requirement noted but It may take a while to implement.
F
Thanks for the suggestions regarding the keys in wtfcui. Adding the content of the directory to the playlist without going inside will be pretty easy do do. <Shift+D>?
In terms of making the keys configurable - this is going to be more complex as it requires a bit of refactoring. Requirement noted but It may take a while to implement.
F