More > JRiver Media Center 19 for Windows
NEW: Improved memory playback
Matt:
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.
Technical Considerations
With a modern computer, playback of a standard CD-quality file will have the fully decoded file in memory in around one second.
Memory playback will use up to 1GB of memory for cache (capped at 80% of available system memory to avoid swap usage).
In some cases, the work of decoding and caching a file quickly as a track starts could lead to other problems. For example, when playing over Wi-Fi some machines exhibit high resource usage when reading a file quickly. This resource usage as a track starts could lead to audio playback glitches.
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.
fitbrit:
Nice. I will keep this option off. Hopefully, this will either bust a few myths or let people hear the difference they've been wanting. Win-win.
mojave:
The decoding seems to be almost instantaneous on my PC. This feature will also allow people to see how fast decoding really happens.
rayooo:
Fantastic!!!! thanks. ;D
Vincent Kars:
--- Quote from: Matt on July 15, 2013, 11:45:13 am ---Memory playback will use up to 1GB of memory for cache (capped at 80% of available system memory to avoid swap usage).
--- End quote ---
Nice to see JRiver having true memory playback
I wonder why you put a hardcoded constrain on it.
Can imagine that a user run Win64 with 8 GB could use a higher value.
Why not making it a user configurable parameter?
Navigation
[0] Message Index
[#] Next page
Go to full version