Originally Posted by Crazy*Carl
Ok, I understand foobar and ASIO/WASPI alot better now, but there is still to many reasons not to switch to it. I am sure the audio difference at least for me is negligible. Its sorta like the flac vs 320kbit mp3 debate.
I too question the audio difference, iTunes itself is the dealbreaker for me. I'm working on a list of reasons to use J. River:
"iTunes will work fine for a basic user with a static collection. Not for anyone frequently adding, modifying, downloading, and changing their collection frequently."
1. Custom tag fields for metadata.
2. For video MC blows iTunes out of the water for support of file formats.
3. For photos MC blows iTunes out of the water because it handles photos.
4. Native FLAC support.
5. Stream lossless audio over LAN or WAN to another instance of MC gui (Library Server).
7. Playing different music on different sound cards at the same time (using zones).
8. Rename files from properties (metadata).
9. Use of complex expressions to sort, edit, rename, etc.
10. Define and backup more than one library
11. Native file conversion (multi-threaded)
12. Secure ripping (on the fly encoding from multiple drives)
13. High quality 32bit audio engine.
14. MC lets you use whatever tags you want and also lets you define database fields that aren't based on a tag in the music files. Classical music is about 2/3 of my library. So being able to fully use Composer and other tags is very important. iTunes will make limited use of the Composer tag won't let me put it in a browser pane.
15. 15mb download
17. Last.FM plugin
18. Display View and Theater View for HTPCs
19. DirectShow filters full customizable.
20. Uncompressed AIFF audio (*.aif, *.aiff, *.aifc) files can be played natively in "J. River audio engine (using input plug-in)
21. Access to Gracenote & FreeDB in addition to J. River's YADB using 2 free 3rd party apps to import cd.ini.
22. Access the web and auto-tag covert art to files from within MC.