2017-01-07, 00:12
(2017-01-06, 21:55)Jeremy White Wrote:(2017-01-06, 19:46)ncarthy Wrote: @jeremy, Have you tried using the options of the Player.Open command?
I cant remember the exact format but something like "options":{"shuffled":false}
I don't have access to the yatse code. They just keep insisting it it a kodi bug.
Is there any good tool to simulate json requests to kodi I can test with?
I do, and I know every single line of it And I do know and practice Kodi code since a lot of years with numerous patches merged, tons of bug report. So you may choose to not believe but it's quite easy to test by yourself.
Create an XSP file, use player.open since 16.x it will most of the time work and respect or not the random parameter but as reported in one of my link 3 post earlier, it will fail for some xsp types like episodes. (And on previous Kodi version result where very inconsistent).
The workaround is to use Kodi playlist and add the playlist via Playlist.Add then start the first item of the playlist.
Adding playlist as files sometimes works but have the great side effect to not expand the playlist inside Kodi playlist system accessible via JSON, so files are queued but you can't see the queue or interact with it.
The problem is that Playlist.Add have a known bug about not respecting order given in the xsp or m3u but fully consider that it's a folder and add the file in alphabetical order. Ignoring XSP order parameter or m3u real order.
Dealing with Kodi JSON is all about compromise and hacks, specially for some parts like playlists. And for playlist there's no good way to cover everything correctly, the best possible way is the workaround Yatse use that at least plays things 100% of the time and allows proper control. At the expense of xsp random bug and m3u reordering. (But Yatse also offer playlist listing in correct order + a play all button that plays in order to address this limitation).