WavPack 4.75 Release Candidate Reply #25 – 2015-05-08 19:55:01 Quote from: bryant on 2015-05-08 19:04:41The fact that my optimizations improve the speed on your CPU in some circumstances by over 50% will have to be enough for me right now. The bar that I set for myself before was that I didn't want situations where the new code was worse than before, and we've still met that goal.Well, one of my CPUs anyway But yes, it's always good to see some improvements, else all that work would have been for nothing...QuoteI usually just run the programs directly in the cli directory (and never install except for a final release). The build will create a tiny script there for each command-line program that runs the executable linked to the correct libwavpack. The cleanest way is to add --disable-shared on the configure line and then when you build it will create stand-alone binaries in the cli directory that have libwavpack built in (so there's no doubt about what's what). I would not install after building like that though.I did not install it after building it, but I'm running the cli\.libs\wavpack.exe, because the cli\wavpack.exe is only 36kb small and doesn't seem to do anything.I've rebuilt wavpack with --disable-shared and now it reports as 4.75-rc correctly, thanks.