Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EXTINF in m3u playlist #8

Closed
jaedb opened this issue Jan 2, 2017 · 6 comments
Closed

EXTINF in m3u playlist #8

jaedb opened this issue Jan 2, 2017 · 6 comments

Comments

@jaedb
Copy link
Owner

jaedb commented Jan 2, 2017

From @mczerski on October 16, 2016 20:24

when I create playlist like this:

EXTINF:1,MultiRoom

rtsp://osmc.local:5004/test

and then open the playlist in spotmop, the name of the track is the uri not the name from the EXTINF directive. In moped ui this playlist is displayed correctly.

Copied from original issue: jaedb/spotmop#154

@jaedb
Copy link
Owner Author

jaedb commented Jan 2, 2017

I have a confession: I'm unfamiliar with EXTINF. Given that Mopidy core plays this fine, I'm sure it can be achieved. It will depend on what information about the stream Mopidy makes available.

@jaedb
Copy link
Owner Author

jaedb commented Jan 2, 2017

From @mczerski on October 24, 2016 11:55

ok, I thought that parsing m3u playlist is done by mopidy core. it would suffice to just show the url but this is also sometimes fail. sometimes the url is showed and sometimes there is nothing showed.

@jaedb
Copy link
Owner Author

jaedb commented Feb 9, 2017

@mczerski, can you please send me the relevant part of your m3u playlist? I'm just trying to isolate whether the issue is Iris not showing the info, or Mopidy not providing it.

@mczerski
Copy link

mczerski commented Feb 9, 2017

#EXTINF:1,MultiRoom
rtsp://livingroom-osmc.local:5004/test

the first line is meta info and second is actual song url

@jaedb jaedb removed the enhancement label Mar 1, 2017
@jaedb jaedb removed the 2.11 label May 24, 2017
@jaedb
Copy link
Owner Author

jaedb commented Oct 31, 2017

The issue is that when requesting the current track info from Mopidy (eg playback.current_tl_track), it returns the rendered track information. I believe Mopidy gets this from the backend provider related to the URI.

However, when requesting the track information from a playlist, it doesn't perform a backend lookup. It just reads the m3u file and respects whatever values are set there (eg your MultiRoom string). This is why you are experiencing a discrepancy.

With this in mind, I believe the issue is related to Mopidy (or more specifically, the m3u backend) as that is what is providing us the variation in titles.

Moped must be reading the playlist track information and not using the playback.current_tl_track functionality. Iris does use this.

@jaedb jaedb closed this as completed Oct 31, 2017
@Yadro
Copy link

Yadro commented Oct 28, 2018

It seems this issue related to iris..

I can demonstrate it:
Radio_M.m3u

#EXTM3U

#EXTINF:1,Ambient - UK2
http://uk2.internet-radio.com:31491/

#EXTINF:2,Echo Msk - Sample title
http://ice912.echo.msk.ru:9120/24.aac

And this is request and response about this playlist
image

image

As you can see Iris receive this information. But it render another.
It would be greate to show information from m3u in playlist. (I'm not talking about current playing track)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants