Hi @john - I have a support thread elsewhere talking about how one of my devices that has chromecast built-in doesn’t seem to have MQA Core fire on roon prior to having any output sent it’s way - i.e MQA authenticate is in the pipeline but no MQA Core and then signal seems to go straight to the device which does not have MQA support so I guess it gets the 16-bit-padded-to-24 tidal mqa flac track ? (I can work around by grouping this device with another CC btw in which case the MQA Core fires
Here’s the thread : CC Built-In Device / MQA Core not triggering prior to transport
I mention this here because this device does not even have a toggle for Enable MQA Core Decoder on it’s Device Setup page. What does that mean ? As I say, it’s a CC device that when grouped with another the decoder will fire. It has MQA Capabilities set to No MQA Support. So there seems to be no way to either a) have it handle and MQA Core decoded stream, or b) skip getting the MQA data at all. Quite bizarre. (As a last bit of data btw - no chromecast audio device seems to have the “Enable MQA Decoder” toggle on their settings page - although all my other CC’s actually do fire MQA Core under Roon, I am curious why the omissions. Thanks! and sorry if I am hijacking thread I don’t mean to)