![]() Some reasons to choose JRiver over others: Both JRiver and MusicBee let you know that there is a database style backend that is managing your music files. MusicBee demonstrates a more modern influenced UI that keeps the database style features and views. Very functional and a popular style of database oriented UI design back then. The JRiver UI is still stuck in the late 90s (although it has updated to do panels for web and Gizmo for mobile). Something with the features and depth of JRiver Media Center but with the user interface and look of MusicBee. ![]() My ideal media player software would be a cross between JRiver Media Center and MusicBee. One reason I started using it way back then (early 2000s) is that it was one of the few players back then that did true gapless playback. Not free, but if you need or prefer some of its features the cost is well worth it. Started using it when it was called Media Jukebox 8. I've been using JRiver for over a decade. MusicBee: MusicBee - The Ultimate Music Manager and Player It has a much nicer interface than Foobar. It can do WASAPI exclusive and bit-perfect. 24-bit is usually the best for most DACs. In order to do WASAPI exclusive in Foobar you need to install the WASAPI exclusive mode component: foobar2000: Components Repository - WASAPI output support In shared mode Foobar will resample everything to a common sample rate that is set by the sound card driver. Foobar also has an option to do WASAPI Shared mode. But you need to use WASAPI Exclusive mode. Then if the next track is 24/96 the DAC will get sent 24/96 data. So if you play a 16/44.1 track the DAC will get sent 16/44.1 data (or more likely 24/44.1). Foobar can automatically change the sample rate that is sent to the DAC based on what the sample rate is of the file being played.
0 Comments
Leave a Reply. |