ProppFrexx ONAIR User-Forum

Why is this M3U file not being split when UDP:hh:mm split is set to TimeUpdate?
Could you take a look at what might be wrong in this file?

The UDP command (program update separator) must start with a # (else it would be recognized as a file entry!), i.e. it must be: #UPD:01:00:00

Is this correct: when using “Split by TimeUpdate”, it only creates one PFP file, but with “TimeUpdateOrHour” it creates one for each hour?
Also, why are the playlists not being placed in the configured Playlist Output Folder? They are ending up in the AppData folder instead.
I’ve attached the M3U file for reference.

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.

I’ve done some testing, and it seems that only with “TimeUpdateOrHour” a playlist is created for each hour, but it is not split at the position where the UDP command is placed.
Also, the playlists are still being written to the AppData folder instead of the configured output folder.

Are there any settings that need to be adjusted for this to work correctly? Or are there other requirements in the M3U file? For example, does each hour need to contain exactly one hour of content, or slightly less?

You define the Playlist Output Folder in the general settings:

An v4.5.2.11 update is available.

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

After the update, I get this error message.

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.

Also all nodes with a Warning symbol contains entries which can not be resolved, e.g. who's given reference entries doesn't exist - you might expand those nodes, to know which one.

Is this the exact same m3u file you already send above? Or is it a new m3u file? If yes, you can post it here.

The issue is not in the file, but in the folder it is being sent to. When I set the output folder in the settings to C:\REMOTE\M3U and run the test, I get that error message.
When I set it to C:\Users\AppData\..., there is no error, and the import works perfectly.