When using the library integration feature with Qobuz, FLAC tracks would always report the maximum available samplerate/-size, not the actual values. When playing from the Qobuz menus directly this doesn't happen. This is due to storing the data at scan time in the library.db. LMS would prefer that stored data over the data provided by the plugin at playtime.
The problem was actually due to LMS not passing the updated sample rate/size metadata to clients in status query responses. That problem has been fixed in LMS PR #898.
When using the library integration feature with Qobuz, FLAC tracks would always report the maximum available samplerate/-size, not the actual values. When playing from the Qobuz menus directly this doesn't happen. This is due to storing the data at scan time in the
library.db
. LMS would prefer that stored data over the data provided by the plugin at playtime.See https://forums.slimdevices.com/forum/user-forums/3rd-party-software/94305-qobuz-com-streaming-plugin?p=1643707#post1643707.
Data is imported here:
https://github.com/pierrepoulpe/SqueezeboxQobuz/blob/788b16a9f640d22cce6f6976336242874fdad428/Importer.pm#L359-L361
But it would be correctly reported by the API at playtime here:
https://github.com/pierrepoulpe/SqueezeboxQobuz/blob/788b16a9f640d22cce6f6976336242874fdad428/API.pm#L572-L586
And consumed here:
https://github.com/pierrepoulpe/SqueezeboxQobuz/blob/788b16a9f640d22cce6f6976336242874fdad428/ProtocolHandler.pm#L377-L385
We might be able to update the stored record here using something like the following (not really tested):
To be followed up...