Page 2 of 2

Re: All Proppfrexx data back in place

Posted: 10 Jan 2017 15:51
by radio42
I see, and yes, this is what I referred to before with the LineIn-Feed:
But it might also be a simple 'LineIn-Feed' scheduling what you are looking for, as described here:
viewtopic.php?f=9&t=636&p=1810
In addition, take a look at the control-commands MAIN_LINEIN_FEED_ON/OFF, which can also be used to toggle the LineFeed option as explained here (either from within this ProppFrexx or any other ProppFrexx instance):
viewtopic.php?f=9&t=636&p=1810

In addition you can use the "LineIn Feed" button in the Main ribbon tab to toggle the state manually.

This means:
Use the 'Line-Feed' option to toggle the Non-Stop system between:
1) using the external LineIn (LineIn-Feed ON); i.e. taking the signal of the 2nd Live-System and muting all other mixer channels
and
2) using the normal mixer output channels (LineIn-Feed OFF); i.e. regular non-stop playout while muting the LineIn input channel

Also see the related global events 'Application.OnLineInFeedON/OFF' which can be used to handle/trigger additional actions.

As such, the mentioned Master/Salve mode is in this case absolutely not needed (as this is really for triggering a backup system)!

I guess that is all which is needed ;-)

Re: All Proppfrexx data back in place

Posted: 10 Jan 2017 20:59
by radio42
The location of the Program Scheduler's .calendar file is located in the general settings, section 'Scripts/Scheduler' - so just go there and change the calendar file location there to its correct path!
Same with the 'Advert Storage Path', see general settings, section 'Scripts/Scheduler' as well.

Not sure what you mean by:
1. overrules PC2 ? Can you explain in detail what you are looking for!
2. What exactly are you look for in GPIO?
What do you understand under 'switch between music-computer (PC1) and Live (PC2)'?
This can be various, as I don't know your environment I cannot give a clear answer.
Are you streaming to the internet? If yes, how exactly? How should the music/stream be transitioned?
E.g. if you want to turn off the streaming on PC1 and switch it to PC2, your streaming connection to your server might drop - with all the respective consequences! Is that what you want?
Or are you an FM station with a transmitter signal, which needs to be switched from 1 PC the another? Etc. etc.
See below for details...

Or do you simple want to use PC1 as your main playout system and PC2 being used for preparation and voice tracksing.
If yes, simply use a common shared network folder for all your media and script libraries as well as define a common shared network folder for your program scheduler calendar file and your Advert Storage Path.
This way, PC1 and PC2 will access the same program and overlay data.

Master/Salve Mode (Multi Studio Backup):
ProppFrexx contains a Master/Slave mode incl. heartbeat monitoring! You need to have 2 machines with ProppFrexx ONAIR installed.
One will act as the 'MASTER' and one as a 'SLAVE'.
The 'SLAVE' will monitor the heartbeat of the 'MASTER'.
On both machines you need to configure the Remote-TCP option (see the general settings in the section 'GPIO/Remoting').
Make sure the 'TCP Control Enabled' option is checked!
And configure your 'RemoteControl Server Port' and 'Authorization Password' as needed.
Once a port and password is configured the two machines might communicate to each other.

You can find this feature in the 'RCM' popup (Remote Control Monitor) - which is located in the 'Main' mixer channel strip.
In this popup the 'TCP Server' should indicate 'Online' (according to the above settings).

Now click on the "Manage Remote Clients" button.
This will open a new dialog called "Remote Client Manager".
Here you can actually 'Add Client' you want to see...but that is another feature...
In this dialog you'll also now find a "Remote Monitoring Master/Slave..." button - this one is used to configure the 'heartbeat monitoring'.

You should only setup this 'Remote Monitoring Master/Slave' on your SLAVE machine!
Enter 'Master IP or DNS', 'Master Remoting Port' and 'Remoting Password' of your other (Master) machine (according to the above mentioned Remote TCP-Server settings).
Now enable the 'Monitor Master Heartbeat' checkbox and finally click on the 'Stopped' button in the 'Monitoring Status' group.
Make sure that your Master machine is running at that time.
Now you can click on OK.
You have now enabled the heartbeat monitoring on your SLAVE machine!

It will now automatically be turned on every time you start ProppFrexx on this slave machine again!
To deactivate it just uncheck the 'Monitor Master Heartbeat' checkbox again.

The SLAVE machine will now run in 'Slave-Mode'!
Whenever the heartbeat detection fails (e.g. because the monitored MASTER goes down)...this SLAVE machine will switch into Master-Mode. Once the MASTER comes back....it will switch back to Slave-Mode.

So what is Slave- or Master-Mode?
Actually nothing - except, that two system events are triggered to which you might assign any control-commands.
See the general settings section 'Events/Commands' in the Application node you'll find two respective entries:
- OnSetMaster
- OnSetSlave
Here you can assign any control-command(s) to be executed with these events.

This means you decide what to do with the heartbeat detection.
E.g. when the SLAVE machine goes into Master-Mode - the OnSetMaster event is triggered.
And when the MASTER comes back, the SLAVE is set back to Slave-Mode - the OnSetSlave event is triggered.

This allows you to e.g. start an emergency playlist, or mute/unmute a mixer channel or start or stop the Scheduler and/or start or stop your streaming servers etc. etc.

So heartbeat monitoring is about checking the availability of a remote machine and switching the Slave/Master-Mode accordingly - on which you then can react via any control-command(s).
Therefore the machine doing the monitoring is by default set into Slave-Mode and constantly 'pings' the machine to be monitored (which by default should run in Master-Mode).