Subsonic Forum

Haven't had any problems with Subsonic, it normally works like a charm. I recently updated to the latest 3.5 (was running one of the betas), but that was a while ago and it has been working fine since. Today, when I fire it up and select some music to play then play it, the main pane goes all black with "The Video is Loading..." in the center. A screenshot is below.

I have tried different browsers (FF and Chrome), I tried deleting all the players and letting it recreate one. I checked all the settings but couldn't find one that might cause it. I tried stopping and restarting the tomcat service. I am still using the WAR version. I have been thinking about switching to the standalone version, but was of the mindset of if it ain't broken don't fix it. Although, now, appears to have spontaneously broken. Any suggestions?

Click image for bigger version:

Please check your browser settings for how .m3u files are handled. It should be setup to use your favorite music player (Winamp, Windows Media Player etc).

I was having the same issue with FireFox 3 and VLC. I uninstalled both, then reinstalled. While installing VLC there was a checkbox for a "Mozilla Plugin" that I recall checking the last time around. I skipped it this time, since I think that FireFox was trying to load some plugin (thus the Video is Loading... message). Now it is working properly.

sindre_mehus wrote:Please check your browser settings for how .m3u files are handled. It should be setup to use your favorite music player (Winamp, Windows Media Player etc).

I will check that, but the thing that makes me wonder is it does it in both Firefox AND Chrome. Chrome doesn't have a separate file type configuration, it uses the windows association. I verified windows has Winamp as the default handler for .m3u before posting that. I will check in Firefox as well tonight, but I don't think its going to turn up anything due to the Chrome thing. Thanks for the response

Finally had some time to mess with it and found it was caused by the VLC Media Player add-in. After removing that from Firefox the problem went away. I still have no idea how that could have caused the exact same issue in Chrome, and haven't since bothered to try it there again (since I don't really care for Chrome anyway). Anyway, problem solved.