Yes. The 3rd party players would support it without problems I guess.
Announcement
Collapse
No announcement yet.
Qobuz.com streaming plugin
Collapse
X
-
-
This part of the new API describes the different streaming formats:
Seems pretty straightforward. Implementing it on LMS should be doable but not by me...
If somebody does look into this, please consider looking at the handling of Playlists too...thanks!Comment
-
Hmm
could "fixing" the Playlist section be this easy?
looks like we should relace "getPublicPlaylists" with "getFeatured"? I'll have to try it tomorrow...Comment
-
Hello, Qobuz has updated Android Application to be able to stream hi res (iOS to come) :
http://blogsv2.qobuz.com/qobuz-blog-...st-maintenant/ (Official announce in French)
http://www.whathifi.com/news/qobuz-h...w-live-android (in english)
In this article, they indicates that the hi res files have to be downloaded first (can we still called that "streaming" then ?) :
http://www.numerama.com/magazine/334...r-android.html (in French)
> does that mean that real hi-res streaming will not be possible and that for LMS system, only solution will be to implement an "off-line option" (as Qobuz official application does ) to be able to stock it in a secure/crypted area on the NAS running LMS for example ? (Not sure that API allows that...)
Regards,Comment
-
@Michael
Can you please look into this?
If I call this: http://www.qobuz.com/api.json/0.2/pl...ated&limit=100
I get the Playlists (the new ones that I get in the apps and webinterface) and if I use this:
I get different ones. Just replacing the call in the API.pm doesn't do the trick sadly, so I can't just try this out myself.
My idea:
Leave the PublicPlaylists call in the main menu and add a submenu to the genre menu displaying the new "feautred" Playlistst for the corresponding genre there. I believe that would be a great improvement for this Plugin!
Thanks.Comment
-
@Michael
I just realized that you have implemented the SmartMix/Qobuz change I had asked for. Thanks for that! It did not overwrite my self-modified file for some reason, so I only realized it now and added the changes manually...
Thanks!Comment
-
Third and last for now:
It appears that Qobuz made a lot of (substantial) changes to their API about 1 Month ago. There were almost 100 commits. I guess this might require some major reworking of the Squeezebox Plugin. I have no idea how long the "old" endpoints will still work.
Apparently the new API (0.2.1) was completely merged into the master tree?Comment
-
Qobuz.com streaming plugin
> In this article, they indicates that the hi res files have to be
> downloaded first (can we still called that "streaming" then ?) :
> http://www.numerama.com/magazine/334...r-android.html
> (in French)
My guess is that they simply want to make sure your listening experience
doesn't suffer from latency, temporary interruptions and buffer
underruns. This already is a problem with eg. the Transporter and the
flac streams in CD quality.
> does that mean that real hi-res streaming will not be possible and
> that for LMS system, only solution will be to implement an "off-line
> option" (as Qobuz official application does ) to be able to stock it in
> a secure/crypted area on the NAS running LMS for example ? (Not sure
> that API allows that...)
Well, if you're running LMS and buying hi-res music from them which the
plugin would need to download before you can play them, why not download
them right away and store them in your local music folder?
--
Michael
Michael
"It doesn't work - what shall I do?" - "Please check your server.log and/or scanner.log file!"
(LMS: Settings/Information)Comment
-
Qobuz.com streaming plugin
> It appears that Qobuz made a lot of (substantial) changes to their API
Feel free to point me to the substantial changes. There were lots of
changes. But most of what I looked at were documentation updates.
Sometimes even only adding/removing/changing values of the sample output
given. I won't wade through 100 changes just to figure out whether
something might be interesting.
I can take a look at the playlist issue, though.
> Apparently the new API (0.2.1) was completely merged into the master
> tree?
The documentation still says 0.2 was current. Don't know where you got
that 0.2.1 from?
--
Michael
Michael
"It doesn't work - what shall I do?" - "Please check your server.log and/or scanner.log file!"
(LMS: Settings/Information)Comment
-
Thanks Michael.
That's why I put substantial in brackets...😉
They changed most endpoints, but I guess most changes were probanly internal and don't need any client changes. Seems to be a lot of changes to limits and returns, bu I don't read code well enough to tell what they actually affect.
The Playlist thing is one of the changes that actually do require client-side intervention, and if something else shows up I'm sure somebody will be able to pinpoint it and post it here.
Thanks!Comment
-
Oh and I forgot:
API 0.2.1 is a branch in their GitHub where they added all those changes (or most) and then merged them into 0.2 (master)Comment
-
Qobuz.com streaming plugin
> API 0.2.1 is a branch in their GitHub where they added all those changes
> (or most) and then merged them into 0.2 (master)
But even in that branch the documented endpoint is 0.2.
Please point me to changes you think might need some investigations.
Just give me the link to the change in github. I'll do the reading ;-).
--
Michael
Michael
"It doesn't work - what shall I do?" - "Please check your server.log and/or scanner.log file!"
(LMS: Settings/Information)Comment
-
Thanks Michael. I'll attempt that when I have some free time.
From what I've seen so far most of the stuff that was changed should not require any changes on the call to get the "new" responses. Also, some stuff, like the considerably more detailed metadata on Albums and Tracks probably doesn't make much sense on LMS anyway.Comment
-
Oh btw...
Does you Plugin already use this?
Apparently that can show all the new formats. Until (if at all) HighRes Streaming gets added this is probably not important I guess...Comment
-
Qobuz.com streaming plugin
> If I call this:
> http://www.qobuz.com/api.json/0.2/pl...ated&limit=100
> I get the Playlists (the new ones that I get in the apps and
> webinterface) and if I use this:
>
> http://www.qobuz.com/api.json/0.2/pl...ated&limit=100
>
> I get different ones. Just replacing the call in the API.pm doesn't do
> the trick sadly, so I can't just try this out myself.
Hmm... I would get exactly the same list - except that the latter would
only return 25 results (despite the limit parameter).
--
Michael
Michael
"It doesn't work - what shall I do?" - "Please check your server.log and/or scanner.log file!"
(LMS: Settings/Information)Comment
Comment