Problem with generating and saving Playlists

[Jörg B]

Hello, there are many problems and discrepancies when creating playlists using PlaylistGenerator Pro and the Scheduler. It is now strongly recommended to only use the command generate PresetName in the Scheduler going forward. This works reliably as long as the playlists generated are played immediately and not saved as m3u8 files.


For example, if I use the assistant and select “Generate playlist” and tick the checkbox “Do not play, but save playlist,” the assistant still creates the old command using run playlistgeneratorpro.exe, like this:
run PlaylistGeneratorPro.exe "-preset=Zusammenstellung Lokalnachrichten" "-out=E:\audio\#automatische Beitragserstellung\Regionews\Playlist\Regionews.m3u8"
This command, however, causes a PlaylistGen Error 1.


If I then manually change the command to:
generate "Zusammenstellung Lokalnachrichten" "-out=E:\audio\#automatische Beitragserstellung\Regionews\Playlist\Regionews.m3u8"
it results in PlaylistGen Error 3: “cannot find Preset …” – probably because everything following generate is interpreted as the preset name.


But the old command with run playlistgeneratorpro.exe is no longer supposed to be used and also causes PlaylistGen Error 1. What can I do? I want to generate playlists that are then loaded later, for example to play local news.

 

[djsoft]

It is now strongly recommended to only use the command generate PresetName in the Scheduler going forward.

Correction: no, it is not recommended by us (developers). Actually, the opposite is recommended: use two scheduled events. First to create playlist and save it, and second to play this playlist at the set time. The generate command is a legacy way to create and play playlists.

For example, if I use the assistant and select “Generate playlist” and tick the checkbox “Do not play, but save playlist,” the assistant still creates the old command using run playlistgeneratorpro.exe, like this:

This is the correct command and it's not outdated.

This command, however, causes a PlaylistGen Error 1.

This error message is caused by errors that had occurred during creation of the playlist. You can open the Playlist Generator and press the Generate button, then check the Log window for errors. There must be none. Before 7.1.2 one of the errors without actual "Error" text was "No appropriate tracks in a category" - this message also considered as an error and will lead to "PlGen Error 1".

If I then manually change the command to:
generate "Zusammenstellung Lokalnachrichten" "-out=E:\audio\#automatische Beitragserstellung\Regionews\Playlist\Regionews.m3u8"
it results in PlaylistGen Error 3: “cannot find Preset …” – probably because everything following generate is interpreted as the preset name.

The syntax of the command is not correct, so it wouldn't work. The generate command takes only one argument, the name of the preset.

But the old command with run playlistgeneratorpro.exe is no longer supposed to be used and also causes PlaylistGen Error 1. What can I do? I want to generate playlists that are then loaded later, for example to play local news.

I'm not sure why you call this command "old". It's a newer syntax, generate command was introduced like 5 years before run PlaylistGenerator.

 

[ibek95]

This error message is caused by errors that had occurred during creation of the playlist. You can open the Playlist Generator and press the Generate button, then check the Log window for errors. There must be none. Before 7.1.2 one of the errors without actual "Error" text was "No appropriate tracks in a category" - this message also considered as an error and will lead to "PlGen Error 1".

Can the playlist still be saved/load then? Even if it has this new error PlGenError1 due to "no appropriate tracks in a category"? Before I update my RB to 7.1.X it would be good to know that ... because in 7.0.8.0 even with occasionally "no appropiate tracks in category" playlists work.

 

[djsoft]

Can the playlist still be saved/load then? Even if it has this new error PlGenError1 due to "no appropriate tracks in a category"? Before I update my RB to 7.1.X it would be good to know that ... because in 7.0.8.0 even with occasionally "no appropiate tracks in category" playlists work.

I guess we'll change the "No appropriate tracks" message classification from "error" to "warning" to prevent this error message from appearing. This will be in the next minor update (7.1.3).