First of all, again: If you already have a Subsonic package installed and running fine: Stay where you are!

Subsonic itself is the same and you might loose your settings during update, I still don’t know when and why this happens, the error is not really reproducible.

I’ve changed the installation/update/uninstallation procedure and included a backup and restore option.

While installing, you can select whether to restore a Backup of Subsonic (which was created during uninstall or with the Subsonic backup creator) or to perform a fresh install. To restore create a folder named Subsonic (with capital S) in your public folder. If you haven’t got a public folder (on multi-bay-nas) create a new shared folder in the DSM. Now place the backup-ed files into the Subsonic folder.

While updating you can select whether to update normally or restore a backup from the public folder.

While uninstalling you can select whether to create a backup in the public folder or not. (You don’t have to do anything to the folder if you want to restore it afterwards)

There is also a new ffmpeg version included, but still no x264 support,. If you are a pro and can compile such things properly or if you’ve got a compiled version for ARM or x86 please let me know, thanks .

Thanks to patters I’ve included timezone support, so the log files should have the correct time now.

upgrade_uifile

[{
"step_title": "Restore Backup",
"items":
[{
"type": "singleselect",
"desc": "Would you like to restore a backup of Subsonic? Create a folder with all relevant files in it, name it Subsonic (with capital S)and place it into your public folder",
"subitems":
[{
"key": "update_restore",
"desc": "Yes, I have a custom backup, please restore it"
},
{
"key": "no",
"desc": "No, just update and leave Subsonic as it is now (all preferences and the library will be kept)"
}]
}]
}]