The VideoLAN Forums

Why the 16-bit FLAC has not a similar behaviour to the 16-bit PCM? This would avoid any superfluous dithering.

PipeWire will replace PulseAudio and so the 16-bit FLAC files will be dithered if PipeWire outputs in 16 bits since VLC outputs them in 32 bits whether the sound is modified (for example equalized) or not.

For the 16-bit PCM files, VLC outputs them in 16 bits and so will not be dithered by PipeWire.

For lowering the sample format, I believe that dithering is preferred to truncating. For example, PulseAudio does not seem to dither but PipeWire seems to dither.

Related to:
https://trac.videolan.org/vlc/ticket/18948

Why does Audacity or Firefox stop the playing when I disable the device output (I do not mute or change the sound, I disable) in Windows (the same thing happens when I start JACK in GNU/Linux)? They had the choice of letting the playing continue or stop it, they chose to stop. Why VLC could not do t...

Related to: https://trac.videolan.org/vlc/ticket/18039 Tested: https://nightlies.videolan.org/build/win64/last/vlc-3.0.0-20171010-0459-git-win64.7z + ubuntu/mint version Hello, I am writing this message because I do not really know if you are notified when the bugs are closed (I feel it is the case)...

That is better but not yet perfect. MPC: 0 to 10 images lost VLC nightly (3.0.0): 78 images lost VLC 2.2.4: 733 images lost Do you have a more or less precise idea of why such a difference between the hardware acceleration of VLC and MPC? Or maybe I can change some things to turn around 0 image lost?

Hello, Around two years ago, I could play Blu-ray files with 95% of images kept with a notebook. Now (VLC 2.2.4), I turn around 60% or worse. I do not remember the version of VLC was OK for me. But it seems not really important because I tried with MPC (1.7.11) and I got the first result which is 95...