ProppFrexx ONAIR User-Forum

It is possible!
Try using a single ${CRLF} to separate the commands and end with a double ${CRLF}${CRLF} to terminate the sequence.

There are always downsides
And yes, that is also normal, as the user can not delay the overlay once the effective start time has passed (that is the time it disappeas).
So I am afraid, that this behavior must/will stay as is.

Please show the full command...Are you sending it from a different PF instance? If yes, did you enable the TCP/IP Remoteing server on the receiving PF instance? Make the call more simple and execute it from the command-line builder - then you will also see a possible result/error code. E.g. use this...

Changed in v3.0.14.11 !

Should now be fixed in v3.0.14.11 !

I'll see what can be done!

If it would be an overlay which crashed, it would not crash again right when you start ProppFrexx again! May be it was again another unattended Windows Update in the background? Also from where did you receive the Silence Detection message? Was that from within ProppFrexx? If yes, that would also in...

Yes, you might use the News & Advert Manager to plan and manage your Newsflash. For News Management see here: http://www.proppfrexx.radio42.com/forum/viewtopic.php?f=4&t=822 Within ProppFrexx you have now various choices to integrate these planned News into your playlist - depending on your ...

What did you do at the moment it crashed. Did you install a new .Net Framework while it was running - or what exactly happened. However, from the Windows Event Log it looks, like a system component/driver actually crashed and thus crashed ProppFrexx with it. Or did you do any other updates or change...

Then check your system - and the Debug Logging! A crash like this can not be caused by ProppFrexx itself - else there would be an entry in the ProppFrexx Error.log. If that is not the case, it must be a system component which caused the crash. If that system component was instantiated by ProppFrexx ...