Facility Control

Hi again! Guess this will be another one for you @jamespeltzer

I am curretly trying to use DashBoard to create a list of camera cuts for a music video recording in our studio.
Seeing as this is choreographed and the camera cuts/transitions are planned ahead to the beat/click/timecode, this would be cool to do automagically.

Now, I have a list of cuts, with what camera follows and how long it should stay before cutting to the next and so on so forth.
However, the timer turns out to be somewhat of an issue. The smallest "counter" in a timer is 1 second, even though I can push the update time lower than the 500ms that is by default.
This isnt accurate enough in order to hit the "rythm" these cuts are supposed to be. One-tenth of a second would be good enough. Getting one hundred of a second seems a bit overkill or just impractical with how often the timer would have to update the parameter showing the timer.

Is there any way to go below just "ss" and go into milliseconds (ss.sss) instead? Or at least show one decimal?
Trying this in the "pattern" value in the timer code just turns what should be the milliseconds into seconds instead.

Would it be impractical to write a custom control on your switcher to do this instead? Where you could control the cuts down to the number of frames it pauses before cutting?
#DashBoard

Would it be impractical to write a custom control on your switcher to do this instead? Where you could control the cuts down to the number of frames it pauses before cutting?

I'm afraid it would be, and it would also kill the reason behind why I'm trying to get this done.
"‹Thanks to @evenover (a student at the college I work at) we have a working interface with Rundown Creator (http://www.rundowncreator.com/) through their API.
This in turn lets us define both inputs, how long they should be at that input, if there should be a connection with ROSS Xpression and what variables to put in the lower third or other graphics for that matter. Basically just interpret the REST response in JSON to fill out a parameter array with the corresponding information from Rundown Creator, and populate a table to showcase this in a human readable form.

In that way, we have, in theory, not fully tested (but somewhat) a working automation of our studio. Now in a newsroom setting this works, as the cuts can be on the second. However, I am now trying to get this to match a music video filming in our studio, and the problem here is that the cuts are not specifically on that second, but needs more accuracy in the shape of one-tenth of a second. So a cut can be after 3.8 seconds, and not at just 3 seconds, wich is what would happpen in DashBoard.

Dunno if this made sense, but basically, this lets whoever choreographs the shots (director) plan the entire thing in rundown creator, pick that rundown list in DashBoard and have it play through automagically.
#DashBoard

Could you have the studio band play to a click track and then have the click software send out MIDI commands to Rundown to run your various commands based on the beat/tempo? Ableton Live could do this.
#DashBoard

Could you have the studio band play to a click track and then have the click software send out MIDI commands to Rundown to run your various commands based on the beat/tempo? Ableton Live could do this.

Yes, for this particular studio band, I could do this. So I'm quite sure I could get it to work this time around based on a similar sollution to what you mention above. This could of course be done.
However not all bands are too fond of the click-track... So I want to make a sollution that works without the click-track, just for cases where we dont have this either available, or the band is not used to, or want to, use a click-track.

Good suggestion though.
#DashBoard

And ONCE again! Not relying in the GUI and reading more in the documentation I could've avoided asking this question alltogether..!
That and not relying too much on previous coding experience where the syntax is slightly off of course...
Simply add an S, and not sss to the setup of the timer and voila... milliseconds... Fun stuff this!

Goal of this week... Read the entire ogScript Reference book, start to finish... Not just light skimming this time.
#DashBoard

Glad you got it working, @astralsberg.
For this one, you also might find the little "help" button (question mark in a blue circle) next to the Display field in "Timers" handy - it lists all of the different fields you can use.



You might also find using ogscript.asyncExec(function, delay) handy - once inside of an async exec, you can use ogscript.pause(time_in_milliseconds) to temporarily pause your script's execution:

<abs contexttype="opengear" style="">
   <meta>
      <ogscript handles="onload">function createFade(steps, delay)
{
   return function()
   {
      var counter = 0;
      while (counter &lt; steps)   
      {
         ogscript.rename('output', counter);
         counter++;      
         ogscript.pause(delay);
      }
   }   
}


ogscript.asyncExec(createFade(10, 100), 0); //First fade
ogscript.asyncExec(createFade(20, 500), 0); //Second fade
</ogscript>
   </meta>
   <label height="78" id="output" left="20" name="Nothing" style="txt-align:west;" top="20" width="196"/>
</abs>

#DashBoard