Some info from my tests. Playback of DSD compressed with wavpack is gapless in foobar2000! Unlike foo_input_sacd (1.0.2) which adds noticeable clicks between tracks when playing separated dff files. Also, some multichannel DSD files which are unplayable with foo_input_sacd, become playable in foobar2000 when compressed with wavpack. Example of such file: https://www.dropbox.com/s/ezsichx10tah9yp/short.dff?dl=0And good old frontend from 2002 still works even for DSD compression

Great to see this new release!! I spent a bit of effort a while ago adding Wavpack support to the Linux command line audio CD ripper / encoder and old and new versions are working there beautifully .

A little aside from this: I am wondering if I am the only person who cannot get the new Wavpack running with qaac under Wine and Linux? A slightly rambling bug report here... Nice to know if I am the only one.

A little aside from this: I am wondering if I am the only person who cannot get the new Wavpack running with qaac under Wine and Linux? A slightly rambling bug report here... Nice to know if I am the only one.

I looked over that issue thread a couple months ago and never really had a clue why you were seeing what you were seeing. Some weird interaction of mingw / qaac / wine / wavpack? It would be interesting to find out what was going on, but it's good that the official DLLs seem to work well.

Also, thanks again for the support in abcde...I'm finally going to be able to give that a shot now that 5 is out!

Hi , I've tried wavpack 5.0 to compress dsd to wv.The compression ratio is really good.But I have a question for the playback.While playing in foobar2000, it recognize the wv(dsd high) in a 352800khz 24bit pcm music,is it normal?And does it still lossless for dsd playback?Because in dsf format it show 2822400 Hz in foobar2000 so I`m a little confused.

In foobar2000, the WavPack library is converting the DSD to 24-bit 352.8 kHz and that's what foobar2000 is playing. I thought that they were going to display the actual DSD sample rate (I even provided an API for this specifically), but it might be that they didn't get around to that, or there's a bug somewhere.

But I do know that whether you play a WavPack DSD or a DSF file directly, they are lossless, but the conversion to PCM is done as the file is read (before the DSP and everything else). Foobar2000 cannot handle DSD internally, and cannot write DSD to a DAC (DoP).

foobar2000 can handle DSD as DSD stream and output it to a DAC… but not natively. The foo_input_sacd allows this. And it works well. The external DAC may indicate what kind of stream is decoded (PCM, DSD, resolution…) and it confirms that DSD playback is possible with DSF, DFF, SACD-ISO.I can not try anymore, because my DAC is dead. But I'm sure there must be a way to handle Wavpack DSD as DSD

foobar2000 can handle DSD as DSD stream and output it to a DAC… but not natively. The foo_input_sacd allows this. And it works well. The external DAC may indicate what kind of stream is decoded (PCM, DSD, resolution…) and it confirms that DSD playback is possible with DSF, DFF, SACD-ISO.I can not try anymore, because my DAC is dead. But I'm sure there must be a way to handle Wavpack DSD as DSD

Yes, I'm using foo_input_sacd and I have a dac that can play dsd natively.But foobar2000 play wavpack-dsd just as a pcm.While playing dsf that't no problem.(Sorry for my English)

Ah yes, you guys are right. I thought that foo_input_sacd worked just like foo_input_dsdiff except that it handled ISO files, but I just tried it and it can output directly to a compatible DAC. Thanks for clearing that up!

Since foo_input_sacd works so well, it might make sense to add WavPack support to that. I don't know enough about the foobar internals to know how that would work with respect to plugin priority and tagging, but it seems like one way to go.

When you created the WavPack-dsd Foobar, than this is the mistake. In Foobar it is not possible to convert a dsf-file to a dsd-wv preserving the dsd-content. Everything gets converted to PCM. Look here.

You have to convert the dsf-file with the command-line interface to preserve dsd.

When you created the WavPack-dsd Foobar, than this is the mistake. In Foobar it is not possible to convert a dsf-file to a dsd-wv preserving the dsd-content. Everything gets converted to PCM. Look here.

You have to convert the dsf-file with the command-line interface to preserve dsd.

Yes , I use command-line to convert dsf to wavapck-dsd with this command: wavpack.exe "input.dsf" -hh Does it correct? Or some other command need for specific dsd that I missed?

What conta69 was explaining is that you cannot use foobar to do the encode using the converter tool because it will make a PCM WavPack file, which you don't want.

Thanks for the explanation.I doesn't use the foobar2000 to do the encoding. Just use Command Prompt to encode.But Foobar2000 with foo_sacd_input still doesn't recongonize the wavpack-dsd as a dsd file.If need I'll make some screenshots.

But Foobar2000 with foo_sacd_input still doesn't recongonize the wavpack-dsd as a dsd file.If need I'll make some screenshots.

I do not think screenshots are needed, because I think what you are seeing is exactly what is expected.

Foobar2000 is recognizing the WavPack-DSD file as DSD, but it is not playing it as a DSD file because it does not know how to do that. Only the foo_input_sacd plugin knows how to play a DSD file natively, but foo_input_sacd does not know about WavPack.

If you look in Foobar2000 properties for the DSD WavPack file, it should show <DSD_SAMPLERATE> and <DSD_BITSPERSAMPLE> at the bottom in the “other” section. It does not show that with WavPack PCM files.

It would require changes in the foobar2000 itself to enable foo_input_sacd to take over WavPack DSD handling. And native DSD hangling would also require a lot of core changes. I know Peter isn't interested in the latter at all.

Real DSD samplerates and bitdepths are reported in special fields in foobar2000 because of compatibility. Internal alpha version reported things correctly and a few components broke down.

I bought a DSD capable DAC to prepare for possible future special DSD support testing. Audio quality wise there's absolutely no difference if DAC is fed PCM or DSD but for me usability with PCM is way superior. Seeking is instant, playback is gapless, you can use DSPs and ReplayGain. DSD is just an absolutely awful transport format.

This may not be the correct place, in which case apologies. I was using Wavpack as my preferred lossless format with the Bass library from Un4seen. In my programme, I completely scan a loaded track for level before presenting it to the user for playing. I only recently found that it was much quicker (at least 3 times) to scan an identical Flac track. Is there anything that can be done about the Wavpack seeking speed. All my files are encoded -h direct from my CD's with dBpoweramp.

But Foobar2000 with foo_sacd_input still doesn't recongonize the wavpack-dsd as a dsd file.If need I'll make some screenshots.

I do not think screenshots are needed, because I think what you are seeing is exactly what is expected.

Foobar2000 is recognizing the WavPack-DSD file as DSD, but it is not playing it as a DSD file because it does not know how to do that. Only the foo_input_sacd plugin knows how to play a DSD file natively, but foo_input_sacd does not know about WavPack.

If you look in Foobar2000 properties for the DSD WavPack file, it should show <DSD_SAMPLERATE> and <DSD_BITSPERSAMPLE> at the bottom in the “other” section. It does not show that with WavPack PCM files.

Yes, It showes <DSD_SAMPLERATE> and <DSD_BITSPERSAMPLE>.Thanks a lot!I'll try to add feature request to the author of foo_input_sacd for wavpack-dsd handling.

Well that's a very good point. I now realise that either could affect the scan speed. I just tested a 4min track and in flac it took 0.43sec to scan & load. The same track in WavPack took 1.35secs. Now these are not particularly long times, however with long tracks DJ's seem to get antsy if the track doesn't appear in the display almost instantly.

Yesterday i tested some DSD128 and DSD256 dsf-files.--> the converting to wavpack worked out without any problem. Also the playback of the songs on my quite weak and outdated system was perfect! (... and gapless!!)

Then i converted them back to dsf with wvunpack. The dos "comp"-command gave me the result: no differences. Thats what i call real lossless converting!

One point at last, which does not work out as hoped for - it is written, that wavpack can compress dsd in DSDIFF and thats correct. But very often DSDIFF (dff-files) contain DST-content and this can NOT get converted. The input-file may not be compressed with DST.

EDIT:Interestingly the compression-rate is very different in DSD64/128/256.DSD64/256 have a rate between 45 and 50% --> very goodDSD128 has a rate between 20 and 25% --> not that good...Is there a reason for this behaviour?