Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: LossyWAV and/or WavPack (Read 6441 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

LossyWAV and/or WavPack

I just realized I have WavPack support on every tech device I have, from my old cell phone (in TCPMP and Coreplayer) to my new one (Android) to my linux box to my windows box (foobar et al). Since I'd never even noticed this shockingly ubiquitous format before, I decided to give it a shot (is it still under development? Bryant?). But because it is often heralded as a "lossless" format (which it is), and given my successes with LossyFLAC, I thought I'd put two and two together to make LossyWV as described in the HA wiki.

But then it hit me. WavPack is a hybrid format already. So then why is coupling it to "LossyWV" suggested on the main LossyWAV page? Does this mean LossyWV is potentially better at, say, 320kbps, than native hybrid-mode WavPack? Should the two be used together (horrific images of lossy transcoding come to mind)?
Copy Restriction, Annulment, & Protection = C.R.A.P. -Supacon

 

LossyWAV and/or WavPack

Reply #1
Wavpack lossy mode is tied to the format. Lossywav is portable between supported formats - you can transcode between them lossless and create 'future proof lossy encodings'

Wavpack allows better integration with correction files and its tools are much more supported across all OS.

Lossywav has a true quality mode while wavpack use ABR and auto-noise shaping. Lossywav has the advantage of constant quality without slowing encoding / decoding. Despite this, Wavpack ABR is more stable @ 256 ~ 320k and also considered truly transparent at very high bitrate with high compression modes ( -b485hx4 or better). The bitrate would match lossywav Q5 or 6.

At middle bitrates 350~400k both should be extremely good and here lossywav Q2 ~3  has an advantage of very fast encoding with constant quality. Disadvantage is that bitrate may be unpredictable and also high. Wavpack could increase quality here too without inflating bitrate unlike modern encoders. This is done at the expense of more encoding complexity without affecting decoding (-x) Or: increased encoding / decoding complexity (-h -x )

LossyWAV and/or WavPack

Reply #2
This is certainly the first time I have heard WavPack described as “shockingly ubiquitous”, but I certainly will not propose any fierce rebuttal. It is definitely still being developed, and in fact I plan on doing some significant work on it during the latter half of this year.

As shadowking points out, both LossyWAV and WavPack’s hybrid mode have advantages and disadvantages. I would someday like to add a VBR “quality based” mode to WavPack hybrid (which would counter one advantage of LossyWAV) but it would never have the very elegant “future proof” feature of LossyWAV. The advantages of WavPack hybrid are that it provides higher quality at an equivalent bitrate and that the correction files are actually usable in some (but not all) playback situations.

Finally, I would certainly not recommend encoding LossyWAV files with WavPack lossy. You would basically get the disadvantages of both formats and none of the advantages of either!