ProppFrexx ONAIR User-Forum

No, I also guess the script is not the issue.
Hence my guess it might be related to the history.

No. When the error occurs you might run the test script.
Or you enable the Debug Logging in the general settings and you can take a look once the issue occurred.

It is really difficult to find the reason.
How often do you have the issue?

Than is that output folder maybe invalid?

That log returned script entries / tracks.
As you said, it seems, that it only under certain conditions produces errors resp. has issues.
So this is indeed hard to measure it tell from here.
So you would need to monitor it when you discover the error. I assume it is a history issue.

The "Test..." function always produces an output - so it is impossible 'nothing pop up'.
The full output in this window (bottom part) is interesting...

Then expand the LAST node!
An exception occurred while reading a log file entry - probably the entry after the last valid one produced an error.
The error is, as given - i.e. the entries path' format is incorrect.
As I don't have your audio files I can not exactly tell which one is corrupt/incorrect ...

1. No, it might skip that script line. So I guess there is some other issue. But I can not tell here which one. Any hint or exception the the logs? See the ribbon tab.

2. Maybe it is the same issue?
Yes, you can use the „Test…“ function of the script to see, if you maybe have a history issue?

An v4.5.2.11 update is available.

There was indeed a bud with the #UPD command in the M3U Program Import.

You define the Playlist Output Folder in the general settings:

No.
Even with “Split by TimeUpdate” it creates a new program for each UPD command.
With “TimeUpdateOrHour” it creates a new program either by each UPD command or if this doesn't happen, the per Hour.

But you can simply try it and then see the result.