2015-11-19, 11:04
@yocoldrain
You are right to some extent. In your case this getter I'm talking about must return either null or the path of the stream itself.
In essense, it must return THE argument that you used in constructor to PlayMedia.
Your m3u http link may be the text file containing N links, in this case the full path I'm talking about is indeed the http (original) link itself.
You see, the playlists as media containers of the links are the objects in their nature. They exist in media centers as an entity.
It's not just "some lines that may be added to the playing queue".
And you can use them in Kodi to organize your library, it even has the directory structure video/playlists, audio/playlists or something like this.
The inability to extract the existing container path on the system, even with special:// is a serious drawback of current Kodi Python API.
You are right to some extent. In your case this getter I'm talking about must return either null or the path of the stream itself.
In essense, it must return THE argument that you used in constructor to PlayMedia.
Your m3u http link may be the text file containing N links, in this case the full path I'm talking about is indeed the http (original) link itself.
You see, the playlists as media containers of the links are the objects in their nature. They exist in media centers as an entity.
It's not just "some lines that may be added to the playing queue".
And you can use them in Kodi to organize your library, it even has the directory structure video/playlists, audio/playlists or something like this.
The inability to extract the existing container path on the system, even with special:// is a serious drawback of current Kodi Python API.