Do not autostart next playlist

[Havenstad FM]

Hi Bernd,

I know there is a button that appears in the ribbon when the next autogenerated playlist becomes visible as a new tab in the playlist window. This button is labeled something like 'DoNotAutostartNextPlaylist'. I think it will prevent the autostart of the next playlist when pressed (as it is clearly labeled

Our regular users have limited rights and apparently they do not see this button. Can You explain to me which right is responsible for the visibility of this button?

Regards,

Jack Reitsema
ITC Havenstad.FM

[radio42]

It is the "AllowProgramOverlayChanges" right which needs to be set.
Else, if you always do not want to start a program automatically, you might also set the programs 'StartType' to 'Manual'.

[Havenstad FM]

Hi Bernd,

Allright, but what other functions are enabled by this "AllowProgramOverlayChanges". In my perception the automatic playing of a playlist is a playlist function and has nothing to do with overlays.

The point is, for every live dj hour i use a script to generate a playlist with appropriate music for the live hour. So, if the show host is sick or otherwise not available the generated playlist will play. If he is present however he can use the 'DoNotAutostartNextPlaylist' to suppress the generated playlist and he can create his own playlist.

But, I do not want the regular users to change any of the overlays that are programmed to play the news and commercials.

Regards,

Jack Reitsema
ITC Havenstad.FM

[Havenstad FM]

Hi Bernd,

Ok, I gave the regular operators the "AllowProgramOverlayChanges" right this morning, but now, after a few hours, they are reporting that the generated playlist is still starting. Is a complete restart of ProppFrexx necessary or should a logout/login be enough ?

Regards,

Jack Reitsema
ITC Havenstad.FM

[radio42]

Why do they report it?
Did they see the button and clicked on it? Or did they not even see the button (in which case they must of course report what they reported)?
A logout/login is however needed to bring the rights into effect and make the button visible.

[radio42]

The name is for allowing changes for a program and overlays.
This right allows:
- Show/Allow the use of the 'Do Not AutoStart Next Playlist' button
- Show/Allow thr use of the 'Delay Overlay' button
-

[Havenstad FM]

Hi Bernd,

Today i witnessed it myself.

I did a complete restart of PFOA.
A scripted playlist was autoplaying from 11:00 to 12:00.
The user logged in as a regular operator at approximately 11:40.
At 11:45 the next playlist for 12:00 showed up in a new tab (just as intended)
At the same time the 'No Autostart Next Program' became visible in the ribbon (just as intended)
The user created a new playlist to use his own choice of music in his show starting from 12:00
He also clicked the 'No Autostart Next Program' button
After the news and commercial overlays at 12:00 the user starts the first track from his own playlist.
At the same time the first track from the autogenerated playlist starts playing (which should have been prevented by the button)
I switched to the autogenerated playlist and see that player A is playing ad AutoPlay is active.

Apparently the button does not function in our setup - do the users need an extra right?
At this moment they have the following rights:

2016-09-28 12_30_58-Clipboard.png (109.07 KiB) Viewed 10798 times

With kind regards,

Jack Reitsema
ITC Havenstad.FM

[Havenstad FM]

Hi Bernd,

Yep, the button was really pushed and disabled after clicking it.

I was also re-checking our setup and indeed i do use a control-command. This is what we do:

During unmanned hours: the mixer table has a button to go in NONSTOP ON mode. If this button is pushed a command sequence is executed in PFOA to (a) route all sound to another soundcard channel (not using the mixer's faders anymore) and (b) set PLS_CURRENT_AUTOPLAY_ON.

During live shows: the mixer table is switched to NONSTOP OFF mode. Now the control commands in PFOA will route all players to their corresponding soundcard channels (on the mixer's faders) and finally set PLS_CURRENT_AUTOPLAY_OFF.

So the operator needs to open the fader matching player A/B, then he switches the mixer table to NONSTOP OFF and after that he is responsible for starting/stopping the players manually.

Could it be that the button 'No Autostart Next Program' only acts on the playlist that has the focus? I do not recall exactly, but i can imagine that his newly created playlist was in focus at the moment he pushed the button.

We also noticed that when we turn our mixer to NONSTOP ON and thus issue the PLS_CURRENT_AUTOPLAY_ON sometimes the next playlist will not autoplay. It seems the operator needs to bring the next playlist in focus first and then switch the mixer to NONSTOP ON.

I hope you get a good idea of our setup, Bernd. Otherwise i will be happy to create a movie to see how our setup is intended to be used. But that will have to wait a few days as i am going away for the rest of the week.

With kind regards,

Jack Reitsema
ITC Havenstad.FM

[radio42]

No, the 'No AutoStart Next Playlist' button works globally independent of which playlisthas the focus
Only the commands you mentioned use the currently active playlist as their names suggest.

So it must be something different.
Please use the'Debug Logging' as explained above an we should get some more info what is happening.

[radio42]

I just made a test here with exactly your settings and I had no issues and it worked as expected.
Did you really clicked on the "No AutoStart Next Program" button? Note, that the button will be disabled once you clicked it, like shown in the picture below:

No AutoStart Next Program.jpg (54.29 KiB) Viewed 10795 times

In addition, the next program must have a 'Soft' Start Type - but I guess this is the case, as otherwise the button should not show up.

The only other idea I have is, that you might be using any control-command somewhere to activate AutoPlay?!
In order to verify that, you might activate the 'Debug Logging' (see general settings, section 'More Stuff') and when the issue happened again then send me the generated Debug .log file.