User Tools

Site Tools


timestrips

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
timestrips [2017/11/17 15:21]
admin [Create Timestrip]
timestrips [2018/09/06 08:43] (current)
admin [Using Timelines for daily tasks]
Line 1: Line 1:
-====== ​Timestrips ​======+====== ​Timelines ​======
  
-Timestrips ​are a kind of Timeline. The main difference is, that a Timestrip is vertical arranged.For us, this seems to be more practical for programming. It is possible to run more than one Timestrip ​at a time.+Timelines ​are vertical arranged ​in V-Control. It is possible to run more than one Timeline ​at a time.
  
-Timestrips ​are controlled by external ​timecode. (If no external timecode is available, the internal timecode can be used). To tell the system were to get the timecode from, a Timecode ​Source device ​has to be configured. ​Usually, this is a timecode reader ​such as Alpermann+Velte TC 60.+Timelines ​are controlled by timecode. To tell the system were to get the timecode from, a Timecode ​Variable ​has to be configured. ​This can be the Position variable of a device such as a timecode reader ​or a player, ​as well as the internal clock of the V-Control machine.
  
-Timestrips can use Chase Devices. That are devices that are automatically locket to the external timecode. +To add a cue to a Timelineenter a value in the //​Position//​ field, select a command and click //Add Cmd//. Now a new row is added to the timeline table. The table is automatically sorted by time code.
- +
-To add a cue to a Timestrip, click //Add Position// to create ​a new row in the Timestrip.+
  
 {{:​Timestrip.png|}} {{:​Timestrip.png|}}
  
-===== Timestrip ​user interface ===== +===== Timeline ​user interface =====
- +
-  - Timestrip list: lists all avalable Timestrips. +
-  - Timestrip view: This is the visual representation of the Timestrip. The first column hold the timecode for a cue. A cue can consist of up to 48 tracks, each track representing an individual command. A track is not linked to a device, so having commands from different devices within one track is OK. To edit a timecode double click on it. To edit a cue, double click on the cues row and column. +
-  - Add Track adds one more track to the timestrip. +
-  - Remove Track removes the last track. +
-  - The Position field changes the current position in the Timestrip. By entering a value here and pressing the Enter / Return key, all Chase Devices will locate to this position. The timecode entered in the Position field is also used for the Add Position button (see 7. Add Position). +
-  - These buttons change the Position value. +
-  - The Add Position button creates a new row in the Timestrip table. The content of the Position field is used as new timecode value. +
-  - Absolute Offset moves the Timestrip to another position. If, for example, an absolute offset of one hour is stet, all the timecode values are changing and one hour is added to them. +
-  - Relative Offset leaves the timecode in the table unchanged. It means that firing a cue is delayed (if offset is positive) or ahead (if offset is negative) +
-  - The Chase Mode area determines the Chase Devices and Timecode Master source +
- +
-===== Create Timestrip ===== +
- +
-A new Timestrip can be created by the Timestrips list context menu. Alternatively use the {{:​addtaskiocon.png|}} Icon to do this. +
- +
-{{:​AddTimestrip.png|}} +
- +
-The Position field holds the timecode value for a new cue. Add Position creates a new row in the timestrip table. +
- +
-{{:​NewTimestrip.png|empty Timestrip}} +
- +
  
-{{:NewTimestripLine.png|}}+**Position:** 
 +If a timeline is running, this field is updated with the current time(code) for this timeline. If a Timeline is edited, this field determines the position of the new cue. Each Time a cue is added to the timeline, the value of this field ist used as trigger value.
  
-To add cueselect a command ​and press the Add Cmd button.+**Loop:** 
 +By default //Loop// is checked. If Timeline is running, and the current Timecode is > then the last Cue's Timecode, the Timeline will not stop. It keeps running, and as soon as the selected Timecode variables content comes into a range of the Timecode values of the Timeline, it jumps to the corect position.
  
-{{:​Timestrip_AddCue.png|}}+If //Loop// is unchecked, the task will stop if the last cue was executed.
  
-===== Chase Devices =====+**Offset:​** 
 +Determines an offset value to the current Timecode. Could be positive or negative.
  
-The Chase area determines the chase devices and the master timecode. Chase devices follow the external (or internal) timecode automatically,​ as far as the timestrip is running. To configure this feature, the following steps have to be carried out.+**Select TC Variable:**
  
-{{:ChaseDevices.png|}}+{{ ::​select_tc_variable.png |}}
  
-**1Determine the Timecode ​Master**+In a new Timeline, there is a button labeled //Select TC Variable//Click this button to select a device variable that contains a Time or Timecode ​that triggers this timeline.
  
-Via //Timecode Source button//, a dialogue is opening, allowing to select a device as timecode master.+{{ ::​select_tc_variable2.png |}}
  
-{{:​MasterTimecodeSelect.png|}}+Click the //Add// button if a variable is selectedThe caption of the button changes to "​Devicename.Variablename"​. 
 +===== Create Timelines =====
  
-In this case, we use a timecode reader interface (Alpermann + Velte TC60 RL Timecode Reader)To complete the selection, don't forget ​to choose a channel for the device as well (tc60 in this example). If there is no external timecode reader available, one can choose Internal Timecode as timecode source.+A new Timeline can be created by the Timelinelist'​s context menu. Alternatively ​use the {{:​addtaskiocon.png|}} Icon to do this.
  
-**2Start TC (only with Internal Timecode)**+{{ :​addtimestrip.png |}}
  
-Determines ​the start value of the internal timer. This is were the Timestrip starts.+Once created, ​the work with timelines is very similar then with cuelists. The only difference is that the first column has a timecode ​value instead ​of an ID. This timecode ​is used to trigger ​the cue
  
-**3. Set End TC (only with Internal ​Timecode)**+==== Enter Timecode ​Values ====
  
-Determines the end value of the internal timer. This is were the Timestrip ends.+Once a timecode variable is selected as timecode master, enter a time value in the //​Position//​ field. This field is optimized for timecode values and takes care that the timecode is allways in a correct format. There is no need to enter the exact format by yourself. For example, if you want to have a timecode trigger value "​00-01-12-23"​ it is OK to enter "​11223"​. After pressing the <​Enter>​ key on your keyboard, the value is automatically formated to "​00-01-12-23"​.
  
-**4Framerate of the Timecode**+The algorithm always looks from right to left, filling the missing digits with "​0"​The //Offset// field works in the same way.
  
-**5Preroll Frames**+If you want to edit an existing value in the timeline after the cue was created, double click on the timecode value to edit it
  
-Preroll Frames determine the time, the system needs for synchronization. They depend on the device that is used as chase device. The quicker the chase device can locate a new position, the less Preroll Frames can be necessary. For today'​s harddisk players, a value between 5 and 15 Frames should be sufficient.+{{ ::​edit_timeline_timecode.png |}}
  
-**6Select ​the Chase Devices**+After editing, it might happen that the cue jumps to another row in the timelineThis is because ​the timeline is always sorted by timecode.
  
-Add Device opens a dialogue to choose the chase devices. 
-  
-{{:​SelectChaseDevices.png|}} 
  
-To select a chase device, select the device and the channels.+==== Using Timelines for daily tasks ====
  
-**7. Remove ​the selected chase device**+If there are daily tasks such as power on and off a system, ​the timeline is one solution (among others) to do this. A //​System// ​device ​is needed to get the real time of the V-Control system.
  
-**8Chase Device List**+{{ ::​systemdevice.png |}}
  
-A list with all configured chase devices+The //System Device// has the device variable //​CurrentTime//,​ which can be used as timecode master for this task.
  
-**9. Run from Current ​TC  (only with Internal Timecode)**+Click the //​Select ​TC Variable// button to select the //​CurrentTime//​ variable as master timecode.
  
-The timestrip start from the position entered in the Position field.+{{ ::​currenttime.png |}}
  
-**10Loop (only with Internal Timecode)**+In the example below, a projector is switched on at 09:00:00 in the morning and off at 18:00:00 in the evening.
  
-Play endless. If you are using an external timecode, the timecode source has to do the loop if you want one.+{{ ::dailytask.png |}}
timestrips.1510932111.txt.gz · Last modified: 2017/11/17 15:21 by admin