Server frontend / watchdog

config
server

#21

Some fixes and additions :

  • Fixed for real this time the TextBoxes for the paths, now the changes are saved.
  • Added a button to rebuild the scanner’s database. It stops the scanner, removes both _media and pouch__all_dbs__ folders and starts it again.
  • Also added two items in the tray context menu (rebuild media db and open diag window):
    tray_context

Deleted files still appearing in CasparCG Client
#22

I uploaded the project to GitHub with some changes after a big cleanup.
The code is still somewhat messy but I’m open to suggestions. This is still a beta.

Changes

Added to the new version:

  • Dynamic handling and editing of executables. Now they can be added or removed.
  • Added options to each executable:
    • Name for the tab
    • Autostart at launch
    • Autostart delay
    • Enable or disable console commands
    • Startup commands
    • Delay for each startup command
  • Added a “new file” button for creating new config files.
  • Edit an existing file pressing the Shift key while clicking the “edit file” button.

You can download the first release here:
CasparLauncher - v1.0-beta

Some features I still want to implement are console command history and older configuration versions (still figuring out how to deduce the version).


Mixer command on server start
#23

Checking out casparcg.exe file information I can see there’s version metadata. For that you can use FileVersionInfo.FileVersion.


#24

There is also a version AMCP command, see the wiki for details.


#25

Great! I see that’s not a problem.
The actual issue would be guessing the actual config file version. One could assume that from the casparcg.exe version but, if you open another file from any other location and it’s based on older or newer versions, the editor woudn’t know which options to expose.
What I had in mind is to show the correct options according to the file version and warn about differences between config and server versions. And eventually convert what’s backward compatible to make that work.


#26

Also, it would be nice to make an assistant-like configuration creator.


#27

Then the approach I proposed is way more preferable as it doesn’t require to run Server to know the version of the executable.

But from there I’ll try to keep working on what I proposed some time ago, which might be really helpful in providing validation for the different versions of Server.


Web Server to Local CasparCG Server