Good find.
If you do bulk copies, you can't avoid high peak loads in a very short time frame.
Still however, I don't think anything played to a DLNA device should be spooled into memory first.
Logitech is caching 30s of music on their renderers. And there's a reason for it.
In my case I get the distortions when copying the file from a network share into the RAMbuffer. I'm running a local MC installation
on that device. And it only happens when switching tracks.
No FullFile caching with DLNA- as streaming scenario - fair enough. But why not if possible.
In any case the ram cache option should be automatically disabled on DLNA servers for that particular server without changing my local setup.
You should put an option into the Music config for each DLNA server to enable/disable it. That one overrides the generic option.
General comment: At this point we again (subtitles/languages/audio-channels?) have a conflict of generic local and DLNA server options. (I think the whole DLNA
parametrization area needs to be reviewed - each DLNA server needs it's own profile - and there are quite some parameters that are available
in the generic section only. I can't ( don't want to) change my generic options all the time to get each of my DLNA renderers working.)
It shouldn't be a big deal to get this done.
Back to the caching:
Caching the file from a network share should work without any hickups on a local MC install at least.