Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Manfred]

I have an audio BD ripped to mkv and then converted to audio DSD format. DSD file size is 8.6 GB.

I have enabled "load full file into memory".
It seems MC can not process the complete file only a certain part.

I have MC 24 latest version 64 bit.

Is there a limit of DSD file size MC could process? (Disabling memory playback ->plays with no problems, but I don't want to disable memory playback only for a few files , Load decoded file into mem works also but leads to high CPU utilization ~50%)

[Awesome Donkey]

There's a maximum file size limit in the MC 64-bit builds which is 4GB for memory playback (or 1GB in the MC 32-bit builds). I'd recommend splitting the DSD file into separate tracks if possible to avoid hitting that limit - it's probably the only way to avoid it, other than disabling memory playback.

[Manfred]

Sorry it was my fault - On the client I have only 8 GB of mem. From the server (16 GB RAM) it is playing correctly.

[Manfred]

Sorry, Sorry - I was too fast on the server - Load decoded file to mem was enabled. So the same problem appears.

[Awesome Donkey]

Yeah, like I said it's probably hitting the limit and causing this issue. The only ways around it is to split the file into individual tracks or disable memory playback.

It's worth noting that it doesn't make sense for JRiver to further increase the memory playback limit. At bare minimum most 64-bit PCs these days have at least 8GB RAM - honestly if you're running a 64-bit Windows OS on an older machine with only 4GB RAM, you should use the 32-bit version of MC instead of the 64-bit version of MC. If the memory playback limit was increased to 8GB and a client only has 8GB of RAM, you risk crippling your performance on the client by using all of the system's resources (which the system needs some of it to perform correctly) if you attempt to load a very large file into memory.

There is one idea that comes to mind that might also workaround this issue (I can't recall if MC already does this): if memory playback is enabled, and a user is trying to load a file that's larger than the 4GB (or 1GB) limit, MC shouldn't attempt loading the file into memory and just playback the file as-if memory playback was disabled. Another idea would be changing the not-zone specific memory playback to where it can be disabled in zones. But I suspect it's an "all or nothing" type of deal.

[Manfred]

I think not many people have large DSD files and MC could have another option ->Load full file into memory for systems with 16 GB Memory or more.

By the way I currently run the DSD file from my server with mem playback disabled through Devialet AIR, which I don't usually use because it stops working when it must switch sample frequency if MC is playing the next file. (AIR sounds the best but it is really buggy->that is why i have a MR for audio with usb cable and isolator to my D220 Pro)