Qobuz.com streaming plugin

[mherger]

> 1) Is there anyway to map these entries (title, artist, album) to LMS? I
> am even wondering to learn how to program LMS ….

That's the one dream feature I've been thinking about a log in the past.
A unified music collection. No matter whether local or remote. The one
feature that would make me bump the version number to 8. Alas... I still
have to figure out how this could be done.

> 2) What approach are you guys taking to manage this BIG DATA issue?

I don't have a big collection :-D

--

Michael

[ajstrother]

Hi Michael,
New Qobuz subscriber (Studio). I am running LMS 7.9.1, Qobuz plugin 1.531, Squeezebox Touch. The first day with Qobuz on LMS was flawless. A few days later tracks are skipping forward 30 to 90 seconds into the song, 16/44 or 24/96. Tidal streams fine and the Qobuz app streams fine, so I doubt it is a bandwidth issue. Any ideas?

Thanks!
ajstrother

[mherger]

> New Qobuz subscriber (Studio). I am running LMS 7.9.1, Qobuz plugin
> 1.531, Squeezebox Touch. The first day with Qobuz on LMS was flawless. A
> few days later tracks are skipping forward 30 to 90 seconds into the
> song, 16/44 or 24/96. Tidal streams fine and the Qobuz app streams fine,
> so I doubt it is a bandwidth issue. Any ideas?

I'd update to 7.9.2 as a first step. If they moved to using https for
the streams, you might be missing some necessary changes.

--

Michael

[jmsent]

> New Qobuz subscriber (Studio). I am running LMS 7.9.1, Qobuz plugin
> 1.531, Squeezebox Touch. The first day with Qobuz on LMS was flawless. A
> few days later tracks are skipping forward 30 to 90 seconds into the
> song, 16/44 or 24/96. Tidal streams fine and the Qobuz app streams fine,
> so I doubt it is a bandwidth issue. Any ideas?

I'd update to 7.9.2 as a first step. If they moved to using https for
the streams, you might be missing some necessary changes.

--

Michael

I'm having the exact same problem. It worked fine for the past week, and then yesterday it would start skipping tracks. I especially noticed it at the first track of any album I picked. Played for 10 seconds than skipped to the next track. After that it often worked ok. But choose another album, and the same thing happened. Hope this can be fixed.
Edit: I just installed 7.9.2. Will report if there are further problems.

[jmsent]

Tried it with 7.9.2. Same results. Skips to the next track. Could this be an issue with an interrupted data stream from Qobuz? Not seeing any problems like this at all on Tidal.
Also tried listening to the same albums directly off the Qobuz app. Absolutely no skips or stutters.

[dysonapr]

Playing Savall's new "Messiah" via the plugin, the last few seconds of the tracks were being skipped. The Qobuz web player streaming to a Chromecast Audio device plays the same album OK. LMS 7.9.2 - 1573685519 + Linux 5.0.0-36-generic #39~18.04.1-Ubuntu SMP x86_64.

[ericj]

Playing Savall's new "Messiah" via the plugin, the last few seconds of the tracks were being skipped. The Qobuz web player streaming to a Chromecast Audio device plays the same album OK. LMS 7.9.2 - 1573685519 + Linux 5.0.0-36-generic #39~18.04.1-Ubuntu SMP x86_64.

I am a studio subscriber, and have similar issues. Just adding that also happens, i believe in 320k mp3, but nearer to the end of each piece. Perhaps some changes in buffering ofn Qobuz's part.
Thanks.

[kjg]

Hi Michael,

I'm seeing similar behavior with tracks ending prematurely on about 20% of the tracks I play. Logging in debug mode, after the premature track end the log displays:

[19-11-23 19:27:29.9383] Plugins::Qobuz::Reporting::__ANON__ (155) got http://www.qobuz.com/api.json/0.2/tr...p_id=xxxxxxxx: { status => "success" }

Could this be a problem on Qobuz's end?

I'm using Logitech Media Server Version: 7.9.2 - 1574315728, Qobuz plugin version 1.531, macOS 10.14.6

Thanks!

Ken

[telackey2]

Playing Savall's new "Messiah" via the plugin, the last few seconds of the tracks were being skipped. The Qobuz web player streaming to a Chromecast Audio device plays the same album OK. LMS 7.9.2 - 1573685519 + Linux 5.0.0-36-generic #39~18.04.1-Ubuntu SMP x86_64.

Same here with 7.9.2 and 1.531. A recent subscriber, and it was working perfectly until yesterday. The most common case is it skipping the last ~10 seconds or so of some tracks. If I seek to that location, it plays fine, however.

I am a software and network engineer, so I can help debug if any help is needed.

I took a glance at the Qobuz API docs and the plugin code, and did not see any smoking gun. My completely random guess is that something about the pre-fetching of the next track is triggering the unhappiness, like Qobuz being more restrictive on simultaneous connections on the account, such that the new streaming connection terminates the old. If the buffer has enough to finish out the track, that works, but if it doesn't...

But, again, that is not something I have dug into sufficiently to affirm, just a guess.

[mherger]

> I'm seeing similar behavior with tracks ending prematurely on about 20%
> of the tracks I play. Logging in debug mode, after the premature track
> end the log displays:
>
> [19-11-23 19:27:29.9383] Plugins::Qobuz::Reporting::__ANON__ (155) got
> http://www.qobuz.com/api.json/0.2/tr...p_id=xxxxxxxx:
> { status => "success" }

No, this reporting should be totally out of line. I bet you'd get this
line in the cases where you don't get the track change, too.

--

Michael