Cool VL Viewer forum

The new Fmod Ex release has not solved it, viewer keeps freezing when a music url is changing, and I am using now v1.26.8.24 with the problem still existing, I need the taskmanager to kill the viewer. I guess I need to wait for another new release of Fmod.

With OpenAl it works fine, it doesn't freeze, but then I can not select "Notify about streaming music title changes".

Just to let you know, this is still happening in the current viewer. Since users of other viewers aren't screaming I'm guessing there's something in Cool VL Viewer that's different. There have been several updates to FMOD, and several updates to the viewer since this started and none have changed the behavior. The workaround still works. Personally I copy the music URL and listen using a player outside of SL, but when I forget I wind up having to kill -9 the viewer.

Perhaps you can take another look at how Cool VL Viewer is interfacing with FMOD when you have a chance.

Thanks Henri.

There is no problem with the Cool VL Viewer code itself. There may be one with the FMOD Ex versions in use. IIRC, most of the other viewers are still using FMOD Ex v4.44.18: you could try compiling the viewer with it and see if it solves your issue (but then, crash bugs that have been fixed in newer FMOD Ex versions would reappear...). I, for one, could never reproduce this issue... May be because I'm using OSS and not ALSA...

Just an FYI, Henri. This is still occurring with the latest version (Cool VL Viewer 1.26.12 (10) Aug 2 2014 09:10:51 (Cool VL Viewer)) even though there have been quite a few FMOD updates in this time.

Could you please enable the "FMOD" debug tag (in the floater opened via "Advanced" -> "Consoles" -> "Debug tags"), get the error to happen, and post the log ?

Without logs I'm clueless on what may be happening...

FMOD code audited and made more robust in today's releases. if you still encounter issues with audio streams freezing the viewer, please enable the "FMOD" debug tag, reproduce the bug, and post the log here !

Unfortunately it freezed again with 1.26.12 (12) version when I pressed the Stop play button. I will next time use the "FMOD" debug tag.

Strange, because no later than last night, I purposely went to an event and waited till the DJ closed the stream. Not only it didn't freeze a single hundredth of a second when the stream got dropped, but the start/stop function worked just fine, before and after the stream changed...
I'm starting to wonder if it's an OS-specific issue... So, pretty please, from now on, and for everyone posting in this thread, do abide with the rules of this forum and provide the full details requested in them. And yes, please, try and activate the FMOD debug tag when you go to such an event, so that full details are logged.
Also, do tell whether the media filter was activated or not and whether IP address lookup ("Preferences" -> "Audio & Media" -> "Media" -> "Lookup IP address for filtered domains") is activated or not; when it it, there may be a 10 seconds or so freeze, if the domain set on the new stream was not already allowed by the filter and if it doesn't resolve to a valid IP address, i.e. if the new stream domain is invalid (null/bogus/non-existent stream), and this is expected/normal/unavoidable (read the tool-tip for that setting).

Since I use the "FMOD" debug tag it has not freezed yet, but I see a lot of times this message appearing in the log, sometimes almost 100 times within one hour.

"DEBUG: LLAudioChannelFMODEX::cleanup: Aborting cleanup with no channel handle."

I don't know if this means something or that I just should ignore it.

I have not enabled the media filter.

Perfectly harmless and even normal/common (thus why it's a debug message instead of a warning).