Page 1 of 2

Doing the production work remotely

Posted: 16 May 2014 11:39
by hdradio
I need to do all the work (scheduling, editing libraries, scripts etc.) from a remote pc (at home).
On a networked pc I have set all the paths to point to a mapped drive (of the OnAir pc).
It works except for Additional scripts.
I had all my Script Libraries under Script library path, so any change on that library was available on OnAir pc (after a reload of libraries which I did with a remote desktop software).
But that way I can't categorize them as they are under <auto> root.

To make the long story short:
My home is connected to my studio with a wireless connection.
What settings do I have to set on my remote pc, to work (I mean doing the production work - not playing onair) completely remotely without opening any remote control software (like teamviewer).

Re: Doing the production work remotely

Posted: 16 May 2014 13:10
by radio42
All libs (no matter if media or script) are under the category <Auto>, if you have loaded them automatically via the 'Auto Lib. Path'.
You can only categorize them when using the regular (additional) library function. I.e. click on the 'Additional Libraries...' button.

There is no way to completely do ALL your work remotely by just using ProppFrexx.
ProppFrexx offers various advanced remote features, but I am afraid, that doesn't mean that you can do ALL your configuration work remotely with ProppFrexx.
What is ALL?
Can you please compile a detailed list of exact 'tasks' which you want to do 'remotely'? Then I might give you an answer what might be possible and what not.

Anyhow for many tasks you can e.g. create a local copy on your home PC...do the work (scheduling, editing libraries, scripts etc.) at home locally and then sync the related files (e.g. the edited .pfp script files; the edited .calendar file; the edited .pfp media library playlist files; or the edited audio files/folders) with your remote OnAir PC.
However, there is no 'automatic' sync function for all these tasks available, as all users work differently and as such I see these setups/tasks on your side.

Re: Doing the production work remotely

Posted: 20 May 2014 12:20
by hdradio
The tasks that I want to do remotely are:
1. Create scripts under certain categories.
2. Schedule those scripts with program scheduler.
3. Create and schedule playlists.
4. Create and schedule campaigns.
5. Create custom libraries to be used in scripts.

Re: Doing the production work remotely

Posted: 20 May 2014 16:25
by hdradio
By custom libraries I mean creating a playlist to be used as a library.

I think that a real Radio Automation Software should have the option do all the production work remotely.
For me, that is very important.
I need to create a script and schedule for the next hour, without interrupting the work of the current dj.
What should I do ? Go to On Air studio and ask him : Sorry, can you give me 2 minutes to add a script to the library and refresh the libraries ? (or call him and ask : can I run a teamviewer for a moment to make some changes ?)
Any software I know can do that job remotely.
I think that you should add this to the wish list please.

Re: Doing the production work remotely

Posted: 20 May 2014 17:00
by radio42
Not sure, what you want to say by "real Radio Automation Software" - ProppFrexx is one!
I guess there is no reason to be sarcastic...

As said above you can do it already...if you follow the rules outlined, i.e. using shared folders and file locations.
Note, that we already discussed the use of the 'Auto Library Paths' in your case!

When you have configured RemoteClients accordingly on your instances, a SCHEDULER_REFRESH command is also automatically send to all these clients whenever you make a change to your Scheduler (I already showed that to you in a TeamViewer session, maybe you just forgot about it).
This command does the following (on the other instance):
- it reloads the media libs as needed
- it reloads the script libs as needed
- it updates/reloads the program calendar

You might also send the related reload control-commands manually whenever needed...

Almost the same btw happens, when you change the Overlay Scheduler. This issues a ADVERTLIB_REFRESH command to all configured RemoteClients.
This command does the following (on the other instance):
- it reloads your entire advert library
- it updates/reloads the overlay calendar

Again, when using shared folders and playlist locations and when you save your new scripts or media lib playlists to the 'Auto Lib Paths' - then all is reloaded automatically whenever you change the scheduler.

Else, if you want to sync things manually; you can create a user defined command to trigger things off for synchronization.
E.g. you can create a small shell script to for example copy your playlists, scripts even manually - but that is of course a more complex task and requires a user specific concept - like for a 'real Radio Station'.

So I am not sure what you are missing?

Re: Doing the production work remotely

Posted: 20 May 2014 17:15
by hdradio
Sorry Bernd, I had no intention to be sarcastic.
Of course I consider PF a real automation software, but as any software, the developer can not know how the end user will use it.
So some things might be missing. That's why we are here to help and add missing features. And I am very happy that you listen to us and in zero time, new updates are out.

Now about what I am missing.
I don't like to have all my scripts under <Auto> and I decided to add them under additional script libraries.
If I do the job on production studio (or at home), how can I add them to the OnAir instance without interrupting the dj's work ?

Re: Doing the production work remotely

Posted: 20 May 2014 18:09
by radio42
I see. So in essence you agree, that syncing etc. is fully possible, but you just do not like the standard way, but want to use a different way ;-)
Agree...

First a bit of info:
The 'Additional' script, media and cartwall libs are kept in a special config file called "ProppFrexx ONAIR.scriptlibs", "ProppFrexx ONAIR.cartwalllibs" resp. "ProppFrexx ONAIR.medialibs".
These file by default are located in your config folder.
The mixing settings ("ProppFrexx ONAIR.mixing") are equally located.

When e.g. adding new scripts, they are registered within these files (e.g. "ProppFrexx ONAIR.scriptlibs").
So you need to ensure, that the above mentioned files are located on a shared config folder.
And that they are used by all shared ProppFrexx instances.
So that when you make changes within one instance...they are accessible by another instance in the same way.

Note, that you still need to reload them (on instance A) when you made a change (on instance B) - but see the above mentioned automatic reload in case of RemoteClients!

Anyhow, there is a global option to use to define a global/shared location for all the above config files!

Yyou might use the "-globalconfig" command-line option when starting ProppFrexx ONAIR:

-globalconfig <path>
Defines the location (relative to the executable location or absolute path) to certain global configuration files. Namely:
• Additional Media Libraries (file ProppFrexx ONAIR.medialibs)
• Additional Cartwall Libraries (file ProppFrexx ONAIR.cartwalllibs)
• Additional Script Libraries (file ProppFrexx ONAIR.scriptlibs)
• Global Message Center Messages (file ProppFrexx ONAIR.messages)
• Mixing configuration (file ProppFrexx ONAIR.mixing)

By default ProppFrexx ONAIR stores the above mentioned configuration files in the standard configuration directory (which might be either the default Application User Data Folder or the configuration directory as defined by the -config command-line option, see above).
By using this command-line option you can enforce ProppFrexx ONAIR to retrieve and store the above mentioned configuration files at the given path location. This might for example be useful, if you want to share a global and common configuration of your libraries and mixing settings for different ProppFrexx instances (e.g. installed on different machines within a network) at a single central location. When doing so, be careful with making changes to these global config files, as different ProppFrexx instances might overwrite each others changes. To prevent such scenario, make sure to use a single dedicated ProppFrexx instance for making changes to your library collection (add or remove libraries) and for making changes to your mixing settings.

Attention:
Before using the -globalconfig option do the following:
a) create a global shared config folder
b) copy the existing files into that new folder

AND make sure to also same your media libs (playlist) as well as script files to a shared location, which is accessible by all instances.
That's it.
So basically the above -globalconfig command-line option will do the trick!

For manual syncing (reload) you can use the related control-commands:
MAIN_RELOAD_LIBRARY, MAIN_RESCAN_LIBRARY, SCHEDULER_REFRESH, ADVERTLIB_REFRESH

Re: Doing the production work remotely

Posted: 20 May 2014 19:31
by hdradio
I don't understand what is the standard way and is the different way that I want.
If you mean standard way is the <auto> scripts, you 've told me that most of your users (including you) use Additional script libraries.

Anyway, I think by the way you described, that -globalconfig will do my job. I 'll try it.
Q: Can I use both -config and -globalconfig at the same time ?
and
Can I create a custom user command to execute (from client to server) all of the above commands (MAIN_RELOAD_LIBRARY, MAIN_RESCAN_LIBRARY, SCHEDULER_REFRESH, ADVERTLIB_REFRESH) and what is that command ?

Re: Doing the production work remotely

Posted: 20 May 2014 20:21
by radio42
When using a 2nd PC with ProppFrexx installed you can do these tasks, if both (the OnAir PF instance as well as the 2nd PF instance) ae configured to use the same:
- shared program scheduler calendar file
- shared overlay scheduler calendar file
- shared Advert Storage Path
- shared script and playlist folder

Note, that scheduled scripts are referenced by their name. Meaning when adding a new script file, this needs to be reloaded on the OnAir instance before it is available.
Note, that you can not scheduled playlist, but script. However note, that playlist files being used within scripts are referenced by their location, so make sure that location is accessible from both PF instances.

Note sure what you mean by "custom libraries to be used in scripts"?
If you mean "Additional Media Libs" (those which are maintained manually), than note, that you can create one locally, but need to add that also on the OnAir instance (there is no remote feature for this available).
The same is true, if you manage your scripts within "Additional Script Libs".

Re: Doing the production work remotely

Posted: 20 May 2014 21:23
by radio42
Maybe a misunderstanding, with 'standard way' I meant the way we/you discussed with me via the TeamViewer session.
I understood, that you wanted to use the 'Auto Lib Path'...

Anyhow, yes, you can use both -config and -globalconfig options.

The SCHEDULER_REFRESH command already reloads the media/cartwall and script libs plus the Program Scheduler calendar.
However you can specify e.g. within the User Commands a dedicated command where you simply invoke multiple commands.
Each line represents on control command, and a User Command can contain any number of lines...
To define a user command go to the general settings (Events/Commands) or click on the ribbon arrow icon at the User Commands group.