After Spotify shut down the Echonet api despite having promised not to do so when they took over the company, I'm probably not the only one going back to Spicefly Sugarcube and MusicIP.
I wanted to take the opportunity and finally use MusicIP filters in my setup so that I can easily limit the selected tracks to certain parts of my library. I have understood that there is no way of creating filters in the headless version by itself and that you have to use the GUI version to create the filters (which are stored in the "default.m3lib" (musicIP's library), not in a separate file). Since my headless setup is on a NAS, I cannot run the GUI on the same machine so I copied the default.m3lib to my windows PC and opened it with MusicIP Mixer, created the filters, and copied the file back to the NAS.
When I opened the webinterface (port 10002), I had 0 songs because the file had been modified. It gave me a button to "reload cache" but it doesnt seem to do anything. I restarted everything that can be restarted but to no avail. I also changed the ownership of the file to 500:500, just like all the other MusicIP files, but that didn't change anything either.
Does anyone have an idea how to fix this?
UPDATE: I restored a backed up version of default.m3lib and MusicIP immediately recognized all 9000 songs in it when I pressed the "reload cache" button. So I'm guessing that there is perhaps some incompatibility between the windows and the linux version of musicIP? Or, more likely, between version 1.9 (which I use on windows) and version 1.8 (which I use on linux? Can anyone confirm this?
In the mean time, I also tried opening the file on the NAS directly with MusicIP Mixer (the containing directory is part of a Windows share on the NAS and can therefore be accessed directly from the windows machine). It worked fine to open it and I was able to create the filters, but MusicIP Mixer is unable to save the new library. I thought perhaps MusicIP on the NAs is blocking write access so I stopped it but it's still not possible to write to it...
I wanted to take the opportunity and finally use MusicIP filters in my setup so that I can easily limit the selected tracks to certain parts of my library. I have understood that there is no way of creating filters in the headless version by itself and that you have to use the GUI version to create the filters (which are stored in the "default.m3lib" (musicIP's library), not in a separate file). Since my headless setup is on a NAS, I cannot run the GUI on the same machine so I copied the default.m3lib to my windows PC and opened it with MusicIP Mixer, created the filters, and copied the file back to the NAS.
When I opened the webinterface (port 10002), I had 0 songs because the file had been modified. It gave me a button to "reload cache" but it doesnt seem to do anything. I restarted everything that can be restarted but to no avail. I also changed the ownership of the file to 500:500, just like all the other MusicIP files, but that didn't change anything either.
Does anyone have an idea how to fix this?
UPDATE: I restored a backed up version of default.m3lib and MusicIP immediately recognized all 9000 songs in it when I pressed the "reload cache" button. So I'm guessing that there is perhaps some incompatibility between the windows and the linux version of musicIP? Or, more likely, between version 1.9 (which I use on windows) and version 1.8 (which I use on linux? Can anyone confirm this?
In the mean time, I also tried opening the file on the NAS directly with MusicIP Mixer (the containing directory is part of a Windows share on the NAS and can therefore be accessed directly from the windows machine). It worked fine to open it and I was able to create the filters, but MusicIP Mixer is unable to save the new library. I thought perhaps MusicIP on the NAs is blocking write access so I stopped it but it's still not possible to write to it...
Comment