tamanaco;318506 Wrote: > > The issue: It seems that whenever the MusicIP returns a song with a > extended (foreign) character the mixes stop and the playlist starts > from the begining. See the relevant lines from my server log below.
Yes this is a known issue. I've added a few but there are definately more, I think there are around 300 different characters, basically if I find a track that breaks it then I add it but I dont really want to add 300+ checks before every track queue event. :s The next release will fix these characters; [ ] + , in path/filenames and I will look to add the more common ones over time. tamanaco;318506 Wrote: > > The questions: > How come the settings that I view using the Web interface of the > MusicIP server are not reflected in the settings page of SugarCube? I'll try and explain, note this is a simplistic explanation Imagine distinct buckets.. Bucket #1 - You have MusicIP GUI which is the MusicIP product standalone. If you create mixes in the MusicIP product the settings used are as defined within its own menu system. (It also has the ability to act like headless mode but lets ignore that). Now bucket #2 is MIP headless mode, (AKA http://localhost:10002/) this is like a pipe into the MusicIP GUI product. So once the headless mode is setup you can request stuff down this pipe and get response back down the pipe. Settings are for ease of explanation distinct from bucket #1 and setup via the mmm.ini file BUT because its a pipe you can also pass your own settings to it on a per mix request basis. There are some features that are available in the MusicIP product but not available (yet) in the headless. For eg. dont include seed track in results and mood settings. The benefits of headless mode are that it basically allows you to have MusicIP always running in the system background without a GUI open and you can do most of the stuff that you can do in the MusicIP standalone product. Now bucket #3 is the vanilla MusicIP plugin in SqueezeCentre, this has its own set of configuration settings Plugin->MusicIP settings these are again for ease of explanation distinct from bucket #1 and bucket #2. You have all the integration of the holding play button down and the M mix symbol etc. but basically its talking down the pipe to bucket #2 or bucket #1 depending on how you setup MusicIP and Squeezecentre. Now bucket #4 (queue drumroll) is SugarCube, again distinct settings as defined in Plugin->SugarCube settings. So SugarCube's settings are seperate and for various reasons I decided to use my own. In a nutshell I didnt just want to rewrite the MusicIP plugin! You will also notice the vanilla MusicIP doesnt support such things as recipes and I personally find it slightly cumbersome to work with. Sugarcube supports the latest available settings of MIP and saves me the confusing issue, in that if I copy the MIP settings, then what about for example recipes, they arent available to poach, so I would end up with a confusing mixture of borrowed and my own settings, where as if I hold my own settings its easier to code and hopefully less confusing. Just setting the port in the SugarCube settings page is enough for it to work. (Assuming you have headless mode setup) This also has many benefits, one of which is that you can play around with the settings in a dynamic fashion while its playing music and they are re-read for each track selection. Also potentially you dont need to have the vanilla MusicIP plugin installed to be able to utilise MIP mixing inside Squeezecentre and could remove it and all the bother of scanning etc. though I've not tried removing it yet and wouldnt recommend it! :) tamanaco;318506 Wrote: > > I'm confused as I thought that one of the recommended *Pre-requisites* > for SugarCube was MusicIP configured to run headless. When running > MusicIP headless does it mean that once I use the MusicIP server Web UI > to change the settings that this settings are reflected on the SC > MusicIP mixes. > Right I think when you mean MusicIP Server Web UI is what I call the MusicIP GUI standalone product. Additionally to the above buckets there is some overlap in that the filters you can define in the MusicIP GUI are available to use from the headless, vanilla MusicIP plugin and also from the SugarCube plugin. So if you create filters in the MusicIP GUI, you just need to do a reload on the MusicIP Headless mode (ie. http://localhost:10002/ and hit the reload cache button) and the filters are then immediately available to use in the vanilla MusicIP plugin (I think) and SugarCube (For sure). If you have SugarCube set to use the filter that you just modified in the MusicIP GUI, then once the headless has been refreshed it will immediately take affect in the next track selection without having to change anything further. tamanaco;318506 Wrote: > > Again, pardon my ignorance as I just got a bit confused. Are the > settings for the mixes comming from the MusicIP server or do you need > to use the setting in the setting page of SugarCube? > > I did not change any of the default settings of SugarCube and the mixes > that I get reflect the MusicIP mixes that I get with SugarCube disabled. > I hope I made sense. > I only utilise "filter" settings from the MusicIP GUI, rest are in the plugin->sugarcube settings page. I dont touch the vanilla MusicIP plugin settings and dont reference them. Hopefully my explanation makes sense? There are guides on setting up headless mode on my website http://www.spicefly.com/ and also in the wiki. -- cparker www.spicefly.com - Visit for an enhanced Interface for MusicIP and integration tips and tricks, Plugin coding tips and Spicefly SugarCube the MIP AutoDJ plugin! ------------------------------------------------------------------------ cparker's Profile: http://forums.slimdevices.com/member.php?userid=2083 View this thread: http://forums.slimdevices.com/showthread.php?t=49226 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/plugins
