ProppFrexx ONAIR User-Forum

I noticed that my overlays do not play anymore.
I was away the weekend and today that I came back I noticed that PF has stopped playing my overlays.
When it's time for an overlay to play, it does not play and there is a dead air until the silence detector switches auto play on.
There is no way to cancel or close overlay player. I can only restart PF.
I noticed that pf had stuck at last night's 20:15 overlay. The debug log shows:

Thanks for the logs, they revealed the area/reason where/why the overlay got stuck.

The '_2015_81' overlay actually got stuck when creating the playback stream. Meaning opening the advert track (audio file) by the audio engine never actually returned.
That shouldn't happen, but I guess anything's possible.
Unfortunately I can not clearly tell why that happened!

Are you updating/downloading those file by any application/downloader?
I remember, that there was once a similar issue when using a certain version of the RTV-Downloader tool, as that tool never properly released a file handle and at a certain point the system was running out of handles...which resulted in a similar behavior.

What was the file format?
Next time it happens, please generate a dump file via Task Manager (note, that you must use the 32-bit version of the taskmgr.exe; located in C:\Windows\SysWOW64\taskmgr.exe) and upload that.
See here for details: http://blogs.msdn.com/b/tess/archive/20 ... chine.aspx

You have PM

I AM NOT updating/downloading any file by ANY application/downloader.
That file is a simple mp3 256kbps 44100Hz
You can see at the log that this file had played normally many times that day.

I am sorry, but I do not see the filename or if it was changed/overwritten/updated in the past by any other process in the logs.

I can only see, that it got stuck while opening the advert file with the audio engine (bass) ... as said, the audio engine never returned from its 'OpenFile' call - which is not good!
And as said, to investigate why this happened, I would need a dump file (as explained above) to send that to the developer of the audio engine to investigate the real reason.

Can you please also post me the log entries for at around '2014-08-03 20:15:02' (+/- your show in advance time) when the overlay '_2015_81' was actually starting and being processed; as it seems, that this overlay was never effectively started and as such blocked the sub-sequent overlays...

Should now be fixed in v3.0.14.7!