Maybe I was not clear, so here in other words:
1. Server Instance of MC 20, holding the library, mostly 24/96 material. All source material has been tested before conversion / transfer
2. Client Instance of MC 20, connected to the Server library
3. Handheld on Client Instance, requesting converted (flac, 16/44.1) versions of the source material
4. Conversion in this scenario is done at the server, converted files to be found in a local folder at the server instance. All converted files tested before transfer
5. After conversion, files get transferred to the Client, using MC 20 internal means
6. After transfer, an arbitrary number of files is corrupted. Flac test yields in "truncated" as error. Which means that the transfer has been silently interrupted with not error to be found in the logs...
Just for the hell of it I'd still try unloading the Bubbleplugin ... why would it be showing up in the log during a conversion?
There is no unloading of it, as it is no "plugin". It is a DLNA proxy, running at the same machine as the MC 20 Server instance. But for heaven's sake I did a test of the affair with the BuppleUPNP Server deactivated. No change in behaviour...
You might of course be right about the flac files being responsible especially because most of them worked. You can test the files for corruption. [...]
When claiming in my first message that the FLAC files on the source are OK, I did this because I verified with flac commandline the integrity of both the sources (mostly 24bit / 96 kHz material) and the converted material (16bit / 44.1 kHz)...
Are you converting from a local drive to the same local drive out of curiosity or over a network share?