To import, select one playlist from the first drop-down box, and click "OK", otherwise if you click "Delete" the selected playlist will be deleted (if owned by you).
To export a playlist to the Subsonic Server, create a playlist in Amarok and save it, rename the playlist by adding the suffix "SubRok" ... For example: [subrok] - Pop/Rock Music, then select it from the second drop-down box and click "OK".
any plan to update api version to match latest subsonic version ?
Try to leave Port field blank and put the complete address in the Hostname field.
I am using SubRok 1.7 with Subsonic 5.2.1. When streaming an mp3 the playback stops with 5 seconds remaining in the song. Song transitions are fine, but the pause near the end is annoying. Can SubRok be configured to cache the entire song plus the next song to avoid this pause?
SubRok is only an intermediary between Amarok and the Subsonic Server, I can't manipulate the streaming.
I really like the script. I just got Subsonic set up recently and browsing the collection through Amarok is great.
I realise this isn't your problem, but a limitation in Amarok's StreamItem.
I updated the script to pad track numbers with a leading 0, so everything sorts properly. If you are interested in the patch, just let me know where to send it.
I'm running the same version. And yes, the track list is ordered correctly in the Media Sources view. It is when I select an album and choose "Add to Playlist" or "Replace Playlist" that the tracks are ordered incorrectly in the Playlist view.
I'll send you a message with a link to a screenshot.
I really like the idea behind, good work you're doing.
Unfortunately the REST-API got upgraded again, could please have a look to support 1.12 ?
unfortunately I get "Incompatible Subsonic REST protocol version. Server must upgrade." message after click on "Test Connection".
Would you provide an upgrade / a version that works with musiccabinet?
I gave a look at musiccabinet, is based on version 4.7 of subsonic, so there should be no problem, it's weird.
Starting with version 1.8.0, the API provides methods for accessing the media collection organized according to ID3 tags, rather than file structure.
For instance, browsing through the collection using ID3 tags should use the getArtists, getArtist and getAlbum methods. To browse using file structure you would use getIndexes and getMusicDirectory.
My previously idea isn't good, because there isn't compatibility with previous API REST, since I used these calls to run the script.
Looking at the rest api doc it says with parameter 'v' you can specify the client version. I guess that's what you're doing?
I will ask the musiccabinet devs, maybe they know more.
If is only a problem related to the version of REST protocol, I can add a dropdown menu in the configuration dialog where you can select the right version. What version uses musiccabinet?