Bugzilla – Bug 11748
Can't start MusicIP mixes from the WebUI.
Last modified: 2011-11-06 23:24:47 UTC
If I click the MIP action icon on an album, it displays the list of tracks making up the mix, and I can play an individual song from the list. But if I click play on All Songs, nothing plays.
Created attachment 5094 [details] Error log
Steven: Can you have a look at this one please
Hmm, this works fine for me on Win XP SP3, SqueezeCenter 7.4 25912 and MusicIP 1.8.1b. Michael, can you take a look at the log?
Alan - you might know better what the first part of the error log means (StreamingController). Phil - please remove _all_ 3rd party plugins and run a full wipe/rescan. Still reproducible? Sounds like some stale data or something to me.
I can see the error in the state-handling in StreamingController. That is simple to fix. But this is only going to happen because Song::new returned undef, which it only does if it also first calls logError, and I see no such error in the log. The one exception is if the playlist is empty, so this must be the case. Somehow, the playlistXtracksCommand has resulted in an empty playlist which it has nonetheless attempted to play.
Change 25967 fixes the StreamingController state error.
I have tried a few times now (including the Change 25967); sometimes it fails, sometimes it works. I think I must have some particular files that cause the problem when they are selected for a mix. I shall try a complete rescan, and see if I can get it to occur again.
For me this fails most often when I have a song that I forgot to scan with MusicIP after importing into my collection.
I always update my MusicIP library before scanning in SC. How can it go wrong if you forget to scan songs in MusicIP before starting a mix? As the mix is created via MusicIP, the mix can only contain songs that are MusicIP mixable (new songs would simply not be included in a mix). More likely to be another URL encoding issue, I think.
Full rescan completed. I looked to see what tracks were not marked as mixable in SC DB, but are mixable in MusicIP. I see that I have a handful of songs that have characters in their filename that are causing a problem with the MusicIP url encoding. backtick (` = %92) hash (# = %23) I think it's likely that one of these files was being picked up as part of a MusicIP mix (MusicIP thinks its mixable). When SC tries to interpret the playlist generated by MusicIP, the url doesn't match and causes the errors?
Philip, do you still see this issue with the tracks you mentioned? Moving to 8.0.
Unassigned bugs cannot have a priority.