-
-
Notifications
You must be signed in to change notification settings - Fork 133
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
Comments
I have a confession: I'm unfamiliar with |
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. |
@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. |
the first line is meta info and second is actual song url |
The issue is that when requesting the current track info from Mopidy (eg However, when requesting the track information from a playlist, it doesn't perform a backend lookup. It just reads the 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 |
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
The text was updated successfully, but these errors were encountered: