The reason is that most of them use HQPlayer specific control interface (thy are not usable with general UPnP renderers) and on the other side mConnect Player and BubbleUPnP on phone are general UPnP control points able to connect to any compatible UPnP or DLNA renderer and they don't implement HQPlayer specific control interface. I would create 2 groups out of the blue ones with a bit different blue color. Instead of 'HQPlayer Control' I would use something like 'User Interface application'. Am I correct that this 'big pre-caching to RAM ' topic is related only to Embedded version (UPnP case), when whole tracks are pre-cached? Or is it related also to Qobuz / HRA streaming with Desktop version? Can HQPlayer pre-load the whole track quickly before playback from these streaming services? How does this caching into RAM affect almost 'gapeless' albums like The Dark Side Of The Moon, where a real pause between tracks does not exist?Ĭorrections or additions I accept with pleasure. Then it looks to me that one cannot get high HQPLayer RAM usage with the Desktop version, since it does not support UPnP. Pre-caching bigger amount of data to RAM also does not apply to endless streams like radio streams or 'playback stream capture' from foobar2000 (expect those abouit 10 seconds you mentioned). So that 'big' pre-caching to RAM does not apply for album mode and I assume the same also for playlist mode, both are local playback (even if you can access content from mounted drives). For regular hires FLAC we are usually talking about tens of megabytes, not gigabytes. So biggest RAM usages are for streaming something like DXD WAV or DSD256 DSF from UPnP server, however these are specifically capped at 4 GB. Generally for streaming you can expect to need as much RAM as single compressed track takes.
Album mode doesn't apply to streaming and it doesn't really affect RAM usage anyway.
0 kommentar(er)
