Last post by zwolamed2 -
Massacre. Final 1.4 update completely broken the player. foo_input_reverse and foo_wave_seekbar was responsible for failed attempt of updating, which resulted in broken launch. When I deleted them manually, I updated the app again, but needed to close it manualy in task manager during working of installer. Then it somehow started to work, but once, probably before, I needed even to run as admin only from direct location to make it work. Very strange. Eventually I ended up with Visual C++ R6034 runtime error on every startup of the app, but everything works. I found similar error related to old WInamp version not installed in the system, but it didn't resolve the problem. And, sticking to topic, I still have freezes during using the app. I think it intesfied. On beta 15, later I found some occasional instabilities in this case. Maybe in later version(s) it intesfied further. I'd really want to get the stable player back... Last good version for me was 1.3, but now few componets are updated to work with 1.4, and I will have some problems with reverting them to 1.4 along with settings, etc. I will investigate further if it is not some particular component. Foobar in safe mode works fine.
Last post by jaynyc -
I just tried Stop After Queue in v1.4, and it did not appear to work. I had 3 tracks in the Playback Queue, and when the last one finished, Foobar proceeded to play tracks from my library.
If you're fine with that bitrate you may as well just use a time domain subband codec like MusePack or hell, even MP2, and enjoy the perfect temporal resolution. Throwing more bits at a transform codec doesn't do much to fix their fundamental shortcomings beyond 192 kbps.
Is there any recent blind test which indicates superiority of MPC over other codecs?