frd__

Release 0.8.2 is now available. It fixes another bug that caused incomplete loads of WAV files greater than 2GB. Release notes: http://wtfplay-project.org/rnotes.html Enjoy, F

HI, wtfplay-live 0.8.1 is available for download. It includes a fix for a serious wav loading problem. Apparently the author (me) forgot how to do basic maths ;)

Hi Mark, OK - then maybe you can share with me a sample hi-rez file that you use? F

Hi, Yes, version 0.8 is out. I was going to post announcement this weekend. Thanks for letting me know about 705k/768k issue. Very interesting. I do not think I touched that part of the code. Would you mind making a small experiment? Could you encode your hi-rez file into FLAC and try playing that? Another option is that the large WAV support does not work as expected and cannot load your files not because of FS but because of size :/ F

Mark, Just one more question: what are the largest wav files that you use?

Hi Mark, I think I know what's going on. The player loads only the first chunk of data from the WAV file. Those data chunks are limited to 2GB in size. 2GB of 2ch/24bit/768kHz makes approx 7 minutes and 46 seconds, which is very close to what you are observing. I know how to fix the issue. F

Hi Mark, Many thanks for the update. I can see the pattern here. No need to send me the track. I will be able create such file myself and see what happens. I will let you know once I find something. Kind Regards, Fryderyk

Hi LowOrbit, Thanks for bringing this issue up. May I ask you for a few additional details? How large is that WAV file that you have trouble with (in Megabytes)? Does the playback of this file stops always at the same place? For example, playback stops always after 100 seconds? Or is more or less random? Have you tried playing that file without wtffui? I mean running wtfplay directly from the command line? If not, would you be able to do that? I am curious if there any messages printed on the screen when the playback fails? For example: "Segmentation fault" would be a pretty good indication that the player crashes :) F

@ArmsanAny core* should boot fine Xeon CPUs without any problems. PS. I am sorry for late reply. I was not looking at the forum for a while.

Hi, Sorry for late reply. This may be related to way that wtfplay handles the sound device in Linux. When used via wtfcui, wtfplay plays a single file at the time. This means that the sound device is opened before the file is played and closed after the playback is finished. I suspect that AP keeps the sound device open all the time (as long as it is running). To be honest a lot of those unwanted artifacts depend on the design of USB DAC itself. There are DACs that are completely resistant and silent when switching clocks, switching between DSD/PCP modes, etc... F

@pm325: I have literally zero experience with Focusrite devices and all information based on sources that I was able to find in the internet. The official statement from the manufacturer is that none of the Focusrite devices are supported under Linux: https://support.focusrite.com/hc/en-gb/articles/208530735-Is-my-Focusrite-Product-compatible-with-Linux- However, the interface is UAC 2.0 compliant will be detected by the generic USB audio driver, which is included in wtfplay-live. This is what the snd command is telling you. Using this driver for playback may or may not work. More specifically, you may be able to send the audio data to the Focusrite interface without issues, but it does not mean that you may get any analogue audio out. Apparently Focusrite interfaces require specialized mixer application and are not compatible with alsamixer. It appears that there is some work-in-progress to implement that specific mixer interface in Linux. Please check out the link below. https://www.audio “science” review/forum/index.php?threads/focusrite-forte-in-linux-and-a-bit-on-the-scarletts.7582/ I hope that this will help. F

HI, A new maintenance release of wtfplay-live is now available for download. The details are here: http://wtfplay-project.org/rnotes.html Enjoy! F

@a333bt: It may sound silly, but did you try unplugging the adapter and plugging it again after the system has booted? I remember having similar issues in a slightly different circumstances. It was a machine with DP output, through DP->HDMI adapter, through HDMI->VGA adapter, into VGA input of a KVM switch. I was getting a blank screen whenever a video output resolution/color depth was changed. Unplugging and re-plugging the HDMI->VGA adapter was always helping. May help in your case too. Another option worth is trying is changing the boot mode: UEFI vs BIOS mode. It may make a difference. F

Legacy BIOS boot is available. Nothing changed there. I just double checked and works normally. Check out your BIOS/firmware settings - maybe it is disabled there.