INTERACT FORUM
More => Old Versions => JRiver Media Center 24 for Windows => Topic started by: Ha The Lang on March 01, 2019, 04:06:06 am
-
JR 24.0.75 cannot play the following SACD iso file from 5th track 0f 2 channels (Bailero track) in "Load full file (not decoded) into memory" mode. Thank you very much.
https://1drv.ms/u/s!As78vBR6Uewtgb8WHlAOkA5BbcMxqA
-
I actually wouldn't recommend using memory playback with SACD ISOs as it's very well possible a SACD ISO might go beyond the size limit of memory playback, which is 4GB if I recall correctly in the 64-bit version of MC24 (1GB for the 32-bit version).
-
I actually wouldn't recommend using memory playback with SACD ISOs as it's very well possible a SACD ISO might go beyond the size limit of memory playback, which is 4GB if I recall correctly in the 64-bit version of MC24 (1GB for the 32-bit version).
My Pc has 16GB of Ram and it play well this iso file in "Load decoded file into memory" mode.
-
My Pc has 16GB of Ram and it play well this iso file in "Load decoded file into memory" mode.
My JR 24 is 64-bit version
-
Even though you have 16GB of RAM, the memory playback feature for the 64-bit build is limited to only 4GB (if I recall correctly). If the SACD ISO's file size exceeds that 4GB limit, that might be the issue.
I mean, it works without memory playback enabled, right?
-
Even though you have 16GB of RAM, the memory playback feature for the 64-bit build is limited to only 4GB (if I recall correctly). If the SACD ISO's file size exceeds that 4GB limit, that might be the issue.
I mean, it works without memory playback enabled, right?
That's right. It works.
-
The memory limit has been increased:
23.0.61 (9/19/2017)
7. Changed: Increased the cap for memory playback track loading to 2GB on 32-bit and 16GB on 64-bit.
But I don't know if that means SACD ISO's will fit in memory.
-
The memory limit has been increased:
23.0.61 (9/19/2017)
7. Changed: Increased the cap for memory playback track loading to 2GB on 32-bit and 16GB on 64-bit.
But I don't know if that means SACD ISO's will fit in memory.
For my mentioned iso file it works well for for 4 first tracks in all "memory play" modes.
-
The memory limit has been increased:
23.0.61 (9/19/2017)
7. Changed: Increased the cap for memory playback track loading to 2GB on 32-bit and 16GB on 64-bit.
But I don't know if that means SACD ISO's will fit in memory.
Looks like it was changed again in MC24.
24.0.45 (7/26/2018)
8. NEW: The maximum memory playback size allocated is expanded to 4 GB from 1 GB on 64-bit builds.
As far as I know, right now it's 1GB for the 32-bit build, 4GB for the 64-bit build. Going higher than this would likely either require a manual setting to set a limit or have MC detect how much RAM is in the system, how much is being used by the system and have it use up to like 60% remaining or something like that. And even then it doesn't seem like a good idea to me to go beyond 4GB. What if a system only has 4GB or even 8GB if the limit was increased again and you load a VERY large file (nearly maxing out the limit or going beyond it, which is also as much RAM as the system has)... would the system become bogged down, slow or even unstable because of all memory being used? Just seems to me there needs to be a sensible limit, and 4GB seems good (since most systems have more than this these days). But right now it's files larger than 4GB (or specifically large SACD ISOs) that might have issues, so again, I'd recommend just disabling memory playback as a workaround. For another workaround I suppose you could use a tool (e.g. ISO2DSF) to extract the music from the SACD ISO into individual files (I'd recommend DSF) to workaround that limitation. That's what I do and my SACD ISO derived DSF files work fine with memory playback.
Or I guess a couple ideas would be that JRiver could automatically disable memory playback for ISO files in general and/or set it to disable memory playback for the file when attempting to load a file that's over 4GB. It would actually make sense to as this isn't the first time this has been mentioned, likely won't be the last either.
-
Or I guess a couple ideas would be that JRiver could automatically disable memory playback for ISO files in general and/or set it to disable memory playback for the file when attempting to load a file that's over 4GB. It would actually make sense to as this isn't the first time this has been mentioned, likely won't be the last either.
The latter would make sense as I have only about 70 files of 4Gb or more (up to 14.5Gb) that are not ISO. Ideally, MC could examine and assess system memory and use what is effective (I have 32Gb) but that would not be, imho, a major priority for so few files.
-
Looks like it was changed again in MC24.
24.0.45 (7/26/2018)
8. NEW: The maximum memory playback size allocated is expanded to 4 GB from 1 GB on 64-bit builds.
My bad. I missed that one.
There was some discussion about what those limits meant at some stage, and now I think of it, why that change above was NEW rather than just a change. That's probably what prompted me to look for the change in the Release Notes.