More > JRiver Media Center 19 for Windows
NEW: Improved memory playback
MrC:
You can quickly search the build notes here:
http://wiki.jriver.com/index.php/Release_Notes
Search "memory" in the 18 and 19 releases.
kstuart:
--- Quote from: rayooo on September 06, 2013, 10:30:43 am ---depends on what your definition of "better" is.
sound quality: if you are in the "Objectivist" camp, sound quality will be identical in 18 and 19.
if you are in the Subjectivist camp, then surely there will be 10 opinions for every 5 people. These opinions will cover any and all possible combinations of better/worse/the same sound quality.
--- End quote ---
So far, the Subjectivist camp opinions are better or the same. I have not heard anyone who says "it sounds worse".
And if you want to know how, in theory, it can sound better, read:
http://www.audiostream.com/content/qa-john-swenson-part-1-what-digital
6233638:
--- Quote from: kstuart on September 06, 2013, 04:05:29 pm ---I have not heard anyone who says "it sounds worse".
--- End quote ---
Yes—to be clear—I don't think it sounds worse. I don't think it sounds better either.
And I think it should have to sound better to justify the increased CPU usage, increased memory usage, and reliance on disk/network I/O compared to MC18's implementation.
gabeg:
Here's a question:
When accessing a another library, does the client side still load a decoded file into memory if you also choose to have everything already decoded to wav from the library server? In other words is the library server taking a flac, decode it and then send to the client where the client then stores the wav to memory?
JimH:
This thread should not be used for other topics. Thanks.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version