[bill_orange]

This is going to be a tough problem for others to reproduce. I am not able to play music playlists using the Kodi-Alexa skill for the Amazon Echo.

Here is the playlist:

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<smartplaylist type="songs">
<name>Classical</name>
<match>all</match>
<rule field="genre" operator="is">
<value>Classical</value>
</rule>
<limit>100</limit>
</smartplaylist>


This result form the Kodi logfile is this:

16:13:25.428 T:1943417488 NOTICE: VideoPlayer: Opening: special://profile/playlists/music/Classical.xsp
16:13:25.428 T:1943417488 WARNING: CDVDMessageQueue(player):ut MSGQ_NOT_INITIALIZED
16:13:25.429 T:1855976352 NOTICE: Creating InputStream
16:13:25.433 T:1855976352 NOTICE: Creating Demuxer
16:13:25.437 T:1855976352 ERROR: Open - error probing input format, special://profile/playlists/music/Classical.xsp
16:13:25.437 T:1855976352 ERROR: OpenDemuxStream - Error creating demuxer
16:13:25.438 T:1855976352 NOTICE: CVideoPlayer::OnExit()
16:13:25.438 T:1943417488 ERROR: Playlist Player: skipping unplayable item: 0, path [special://profile/playlists/music/Classical.xsp]
16:13:25.446 T:1943417488 NOTICE: CVideoPlayer::CloseFile()
16:13:25.446 T:1943417488 NOTICE: VideoPlayer: waiting for threads to exit
16:13:25.446 T:1943417488 NOTICE: VideoPlayer: finished waiting
16:13:25.446 T:1943417488 NOTICE: CVideoPlayer::CloseFile()
16:13:25.446 T:1943417488 NOTICE: VideoPlayer: waiting for threads to exit
16:13:25.446 T:1943417488 NOTICE: VideoPlayer: finished waiting

The playlist works fine run manually.

The developer of the Kodi skill suggests that a parameter in the playlist function call used in his skill may have been depreciated between Kodi 17 and 18. He uses call Player.Open with the "file" parameter set to the playlist file. Is that possible?

Looks like this bug is affecting third party apps other than the Amazon Echo skill.

http://forum.kodi.tv/showthread.php?tid=315249

I wonder if anyone is working on this. It probably does not affect many people. Improper (or no action) from a properly constructed JSON string should be a pretty fixable problem. Too deep for me unfortunately.

Bill