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.
Last post by Porcus -
A few more tests on floats with and without --optimize-32bit. All downloaded from https://soundcloud.com/soundchaotic 11 .wav files, ran on default, -hx, -hx4, -hhx6 --threads, all four with and without --optimize-32bit
Actually, --optimize-32bit makes every file bigger. Depending on how it was implemented, that may indicate (1) nope, not worth it - or (2) not implemented optimally yet. Maybe both. For example, I have no idea whether the optimize-32bit choice can be made per frame or has to be made per file - but looks like fat chance that even a a per-frame brute-force-select between "integer algorithm" and "float algorithm" could make big impact on this corpus.
If we postulate that 32-bit integer is "kinda stupid anyway", then it might be a good idea to stick to handling the waste those create, keeping compatibility for everything else.
Does WavPack's compatibility policy extend to 5.70 decoding whatever 5.66 can encode?
Sounds like the Accurate Rip that dBpoweramp offers.
Well maybe it does sound like dBpoweramp's "partial match" feature?
Which from memory works like this: If a track has an AR entry, and upon ripping twice none match and are different, dBpoweramp can sometimes get a match by combining frames from rip#1 with frames from rip#2.
Accurate ripping verification of partially damaged tracks
I quickly browsed their github to get what this is supposed to mean, didn't find it ... anyone?
Sounds like the Accurate Rip that dBpoweramp offers. "AccurateRip compares results with other peoples rips, a match is a 100% certainty it was without error, no other secure ripping method can get this close to verifying error free rips. Once a month AccurateRip will request to send your results to help populate the database."
Honestly, reading about cyanrip sounds like it's trying to copy most everything dBpoweramp does—but lesser in every way.
Last post by Porcus -
I recall I tested --optimize-32bit on float "by mistake", I thought it was an integer-only thing and then a wildcard sent it off on more files than I intended. The files were different, so I realized then it does make a "difference" - but the size savings were small indeed. I tested one now for 0.002 percent size difference, and then (using fb2k bitcompare, uses an official WavPack that doesn't read those 5.6.6 corrections) I infer that --optimize-32bit was invoked in 79 percent of the samples.
So I am not sure this warrants any --optimize-32bit=<0 for none, 1 for integer, 2 for float, 3 for both, defaulting to 1> except in a version for testing. If we postulate that 32-bit integer is "kinda stupid anyway", then it might be a good idea to stick to handling the waste those create, keeping compatibility for everything else.
Spoiler (click to show/hide)
Hm hm hm but can the same way of hiding stuff can be for a 64-bit files extension? Because bragging rights and silencing the requests. Hm, are there any tools that use an 80-bit format?
resizing works but it does nothing good for me. If I shrink the windowI can't see the whole content so I still can't accept the changes (as I do not see the OK button). The window is bigger than the previous one so it is even worse.
But if you shrink it from the top you can move it so that the OK button becomes accessible.
Unfortunately not. Shrinking always hides the bottom part of the window, no matter if I shrink from the top or from the bottom. So the more I shrink the less of the bottom settings I see. Always see the upper part.
Hi all! I found that in clean installed windows 10 22h2 with latest updates and windows 11 23h2 plugin not working. Resampling not working. VC_redist_x64 installed on both systems. In build windows 11 22h2 plugin working ok.
Please confirm if you are sitll facing this issue with v5.6.0
