More > JRiver Media Center 19 for Windows
NEW: Improved memory playback
ead1:
--- Quote from: nevcairiel on August 12, 2013, 02:07:29 am ---Last time it came up, 64-bit was not planned yet. Maybe in a future version, but i would not expect it for MC19.
--- End quote ---
Why is that?! isn't it about time to have both 32 bit and 64bit versions??
6233638:
Probably because moving to 64-bit breaks compatibility with a lot of plugins - including madVR - and because there's no audible benefit to using memory playback.
Arindelle:
--- Quote from: 6233638 on August 12, 2013, 04:58:49 am ---and because there's no audible benefit to using memory playback.
--- End quote ---
Just my 2 cents, I was involved in a group ABX testing, which totally backed up what 623 is saying so I never bothered with it anyways (no debate, everybody has a choice of course).
However, I decided to try it on a client playing music remotely on a PC, and although no noticeable audio improvement as expected, but I thought it made my network connection faster ... is this possible or is this a placebo effect, I don't know. Seems obvious when searching within a song. But I also noticed an increase of speed before -- maybe it has more to do with the dev's work to increase this in the last couple of months/versions
Btw, Server is still configured without memory playback and sounds great on my stereo, so I don't see why I would change that.
6233638:
--- Quote from: Arindelle on August 12, 2013, 06:15:16 am ---However, I decided to try it on a client playing music remotely on a PC, and although no noticeable audio improvement as expected, but I thought it made my network connection faster ... is this possible or is this a placebo effect, I don't know. Seems obvious when searching within a song. But I also noticed an increase of speed before -- maybe it has more to do with the dev's work to increase this in the last couple of months/versions
--- End quote ---
The way that memory playback works in MC18 is that it caches the entire file in memory, and then has a buffer of ~40MB for decoded audio during playback.
This means that when you seek through the file, it will be accessing it directly in memory, rather than relying on network access, which explains why it would be faster to seek through a track.
The downside to using memory playback over a network is that you may have a slight delay during track changes if your network is slow to respond, because all the network activity happens at the start of a track.
If you are streaming the track (memory playback disabled) then the connection is in use throughout playback, and should still be "open" when the track changes, so you may have less delay.
Media Center 19 has made a number of changes to the way that memory playback works, that satisfy the audiophile requests for "real" memory playback, but I think it negatively impacts performance in a number of ways, for no audible benefit, and it's now possible for a track to only be partially cached if it exceeds the ~1GB buffer when decoded.
Arindelle:
thanks for the info 623 :)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version