Qobuz.com streaming plugin

[d6jg]

Simply skips to next playable item which could be local FLAC (transcoded correctly) or Spotty Ogg (converted to mp3). Is there a specific log setting that would show me more?

all i can see is

[19-12-12 13:54:04.0640] Slim::Player::Song:pen (410) Error: Couldn't create command line for flc playback for [qobuz://50303540.flac]

[d6jg]

I have Spotty & Qobuz currently enabled
Interestingly DSTM/LastMix will choose FLACs from Qobuz for all of my players when appropriate but for Alexa it always chooses a Spotify track.
I have been adding Qobuz tracks manually to the playlist for testing which then throws the error as above. Quboz tracks that error with Alexa do play correctly on normal players so its not a bad file issue.

[philchillbill]

For Alexa players, the JSON query [players, ?] will return isPlayer: 0. Maybe that’s being checked somewhere.


Sent from my iPhone using Tapatalk

[mherger]

> For Alexa players, the JSON query [players, ?] will return isPlayer: 0.
> Maybe that’s being checked somewhere.

Are you streaming the stream.mp3 URL? I think that isPlayer flag is to
tell whether it's a player understanding slimproto.

--

Michael

[philchillbill]

> For Alexa players, the JSON query [players, ?] will return isPlayer: 0.
> Maybe that’s being checked somewhere.

Are you streaming the stream.mp3 URL? I think that isPlayer flag is to
tell whether it's a player understanding slimproto.

--

Michael

Yes it uses /stream.mp3?player=Alexa

[mherger]

> Yes it uses /stream.mp3?player=Alexa

Ok, I think transcoding from FLAC to MP3 is simply disabled in
convert.conf for remote streams. I tried to enable it, but playback then
would fail for other reasons. I must assume it has not been enabled for
good reasons. I also remember that this topic had come up before. And
the fact that it still is not enabled leads me to think that it is not
possible.

--

Michael

[marcoc1712]

> Yes it uses /stream.mp3?player=Alexa

Ok, I think transcoding from FLAC to MP3 is simply disabled in
convert.conf for remote streams. I tried to enable it, but playback then
would fail for other reasons. I must assume it has not been enabled for
good reasons. I also remember that this topic had come up before. And
the fact that it still is not enabled leads me to think that it is not
possible.

--

Michael

The problem is Seeking (T Capability) as for today you should remove it when transcoding remote streams.
I sent to you some years ago the patch to solve this problem in LMS.

[mherger]

> The problem is Seeking (T Capability) as for today you should remove it
> when transcoding remote streams.
> I sent to you some years ago the patch to solve this problem in LMS.

Seeking is different. Maybe I thought about this, rather than about the
transcoding. Transcoding from remote source would be the R capability.

--

Michael

[marcoc1712]

> The problem is Seeking (T Capability) as for today you should remove it
> when transcoding remote streams.
> I sent to you some years ago the patch to solve this problem in LMS.

Seeking is different. Maybe I thought about this, rather than about the
transcoding. Transcoding from remote source would be the R capability.

--

Michael

Correct, but Qobuz uses STDIN (I) capability, nor Remote (R).
The problem is that LMS require T to be disabled when I is enabled, I could not remember where exactly is the related code, but sure in TranscodingHelper or called form there, I could check if you need.

[d6jg]

Correct, but Qobuz uses STDIN (I) capability, nor Remote (R).
The problem is that LMS require T to be disabled when I is enabled, I could not remember where exactly is the related code, but sure in TranscodingHelper or called form there, I could check if you need.

Hang on fellas.

The only reason that this has reared its head is me testing phillchillbill's MediaSever skill for Alexa. This provides two modes of operation 1) as a controller for existing players of whatever type and 2) as a player in its own right where it uses stream.mp3.

As far as 1) is concerned there is no issue with playing Tidal, Qobuz etc although voice control needs perfecting.

It is 2) that generates the issue but we already know that Alexa Echo devices are (in the main) HD capable from Amazon Music HD however at present there is no documentation on how a developer can utilise that capablity but surely that must only be a question of time?

If so is it even worth trying to transcode a remote stream for this single use case which could go away very quickly.