More > JRiver Media Center 19 for Windows
NEW: Improved memory playback
bulldogger:
--- Quote from: Matt on July 15, 2013, 11:45:13 am ---Overview
Memory playback now holds decoded data in memory instead of encoded data.
This means playing any form of lossless (WAV, FLAC, APE, ALAC, etc.) will have identical data in memory and identical resource usage.
Benefits
The theoretical benefits of memory playback are that no disk or network I/O occurs while playing and that CPU load during playback could be reduced.
Memory playback will use up to 1GB of memory for cache (capped at 80% of available system memory to avoid swap usage
Some files like DSD played as PCM have very large decoded data so that they might require more memory to cache than (most) any system has. In these cases, the program will cache 1GB, play it mostly out, then cache another 1GB, etc.
With memory playback enabled, the player will no longer report a real-time bitrate (ie. 872 kbps) during playback. This is because asking the decoder its current bitrate is not possible when the decoder has finished with the current track completely in the first couple seconds of playback.
Sound Quality
JRiver is unaware of any test that shows a sound quality advantage to memory playback.
The option was added due to popular demand.
How to Use
You enable or disable memory playback in Options > Audio > Play files from memory instead of disk.
It is off by default.
--- End quote ---
So 1 GB is the most that would be in memory regardless of how muck memory I have? If so adding a large amount of memory like 16GB or 32GB would offer no improved capability beyond the 1GB?
Hendrik:
--- Quote from: bulldogger on July 22, 2013, 08:18:39 pm --- So 1 GB is the most that would be in memory regardless of how muck memory I have? If so adding a large amount of memory like 16GB or 32GB would offer no improved capability beyond the 1GB?
--- End quote ---
MC is a 32-bit application and as such its total memory usage is limited, it would never be able to use this much memory.
6233638:
--- Quote from: Vincent Kars on July 22, 2013, 04:38:30 pm ---Nice to see JRiver having true memory playback
--- End quote ---
It already did have "true" memory playback, playing from a buffer of decoded audio. But it now buffers 1GB which will allow most(?) tracks to be fully decoded into memory.
--- Quote from: Vincent Kars on July 22, 2013, 04:38:30 pm ---Can imagine that a user run Win64 with 8 GB could use a higher value.
--- End quote ---
If I recall correctly, a 32-bit application should be able to use ~3GB on a 32-bit OS and ~4GB on a 64-bit OS.
Moving to 64-bit would likely add a number of issues and incompatibilities. (e.g. no high quality video playback, lower compatibility with VST plugins)
--- Quote from: Vincent Kars on July 22, 2013, 04:38:30 pm ---Why not making it a user configurable parameter?
--- End quote ---
I agree, it would be nice if this were user configurable.
Vincent Kars:
--- Quote ---It already did have "true" memory playback
--- End quote ---
Are you sure? See Matt's opening post, the decoding before playback started is one of the new features IMHO
rayooo:
--- Quote from: Vincent Kars on July 23, 2013, 10:11:48 am ---Are you sure? See Matt's opening post, the decoding before playback started is one of the new features IMHO
--- End quote ---
Agreed..that's what I thought as well... The "old" play from memory cached the raw disk data in ram, then, decoding, resampling etc. was performed during playback.
The new play from memory does all decoding, DSP operations etc, caches this result in ram .. And then begins playback. Do I have this roughly correct???
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version