Synchronise Crossfade
Quick Jump !!
0) No Synchro
1) Internal Clock
2) Midi Time Code / SMPTE
3) CD Audio Position
4) MIDI Data Stream (All MIDI Notes)
5) MIDI Data Stream (Note 96 (C8) - GO)
6) MIDI Data Stream (Control Change)
7) Wave Audio Position
8) Midi Audio Position
9) AVI Video Position (AVI, MOV or MPG)
10) Send a Control Change 44 to the MIDI OUT Port
11) Internal clock, opening Day file (1.asc-Sun, 2.asc- Mon...)
12) MIDI Data Stream (Program Change)
13) All MCI Positions (CD, AVI, MPG, *.* ...)
14) Count Down Timer
15) Crossfade Counter
16) MIDI Data Stream (Pitch Wheel [value]-Cue No.[value])
17) MIDI Data Stream (Note [value]-Cue No.[value])
Add 100 to set both Internal Clock and Selected Synchro
When Multimedia Synchronisation is selected, a synchronisation cue may be inserted in real-time just by clicking with the left mouse button on the first panel of the toolbar. If the time required to prepare the exact cue values is not available, create the reference points first (recording the related cues), and then edit the recorded cues
off-line.
Specific Crossfade synchronisation options may be selected and these are detailed below.
Note the three option buttons in the bottom of this window in the frame "Synchronisation Priority":
Time priority (Low) (default)
This option is the normal synchronisation standard. ProScenium triggers all the cues corresponding to the returned code position. In this mode you can be sure to have perfect time synchronisation, but it is not 100% safe in all situations. For Example, if a large video file is running, and you are running at 25 frames a second is it possible to lose some reference points.
Another way to lose a Cue is when you manually write in the Cue number. For Example, Midi Time Code has a resolution of 2 frames, this means that 1 frame (even or odd following the SMPTE type ) is not received.
Incidentally, you will not encounter this problem if you set the positions by just clicking with the mouse on the first panel of the status bar when the synchronisation is running.
Medium Priority
Using this option ensures that if you do lose a reference point, you will only lose the last point that has been selected, but even if the last position is lost it can be recovered into the following frame, however, if more than one position has been skipped, only the last one will be recovered.
Trigger all positions
Using this option ensures that you are sure to trigger from all reference points, if a point is missed, it can be recovered into the following frame, even if the name doesn't match.
Take Care, if you are make mistakes in the sequence (for example setting two cues with a fade time of 5 seconds at an interval of 1 second), The ProScenium will always send all the cues, and this can cause a delay in the sequence.
Note that with a normal sequence (99% of applications) you will never have these problems.
These are the different Synchronised Crossfade Options that are provided by ProSceniumDMX.
0) No Synchro the user runs the Crossfade manually;
1) Internal Clock
The program runs the Crossfade automatically using the internal PC clock for memories that have the same number as current time. For example, if the current time is 13:11:11
Very Important: the clock must be set in European Time or Military Time from 00:00:00 to 23:59:59
and not in standard USA Time A.M. -P.M.: you can go in Windows Control Panel/Reginal Settings to change the Time Format.
(hours:minutes:seconds format) and a cue numbered 131111 exists (requiring the plain number with no space and no delimiter), this cue will be automatically started with the stored time in/out parameters.
Note that for this Sync Type and for Sync 11 you can also create masks, in order not to repeat cues with different starting hours.
For example, you want your Exterior 600's to change colour every 10 minutes throughout the day.
Make the cue with the right colour, and call it 991099.
This Cue will be triggered by ProScenium every hour at 10 minutes past the hour.
Cue No. (Mask) Frequency Triggered by ProScenium
991099 minutes Every hour at 10 minutes past the hour.
991599 minutes Every hour at 15 minutes past the hour.
999199 minutes All the ten minutes at min. 1
999599 minutes All the ten minutes at min. 5
999930 seconds All minutes at sec. 30
999900 seconds All minutes at sec. 00
999991 seconds All the ten seconds at sec. 1
999995 seconds All the ten seconds at sec. 5
In Sync mode 1 and Sync mode 11 you can ask ProScenium to Trigger the
Sunset and Sunrise event timer.
How to avoid triggering cues from 1 to 100 when you are in sync with internal clock.
If you are synchronised with the internal clock in mode 1 or 11, a common mistake is to make cues named 1, 2...100.
These cues are automatically triggered by ProScenium at 00:00:01 (midnight + 1 second) and so on.
To avoid this, you must rename the cues, for example, 250001, etc or 0.1, 0.2 , so that they do not fall into the intervals of triggering by the internal clock.
If this is not possible (imagine simultaneous configuration with internal clock and 2532 Direct Access Controller), you could do the following :
i) Record a cue named 235959 with Sync 0 as MCI Command, with a follow on time of 61 seconds
ii) Record a cue named 240000 with Sync1 (or 11) as MCI Command
iii) ProScenium will not trigger internal clock cues from 00 :00 :00 to 00 :01 :00
iv) This means that cues from 1 to 100 will not be automatically triggered around midnight
2) Midi Time Code / SMPTE
The program reads Midi Time Code (MTC) through the Midi port (using a SoundBlaster™ compatible card). If the MTC returned is 12:11:11:24 (Hours:Minutes:Seconds:Frames) and a memory numbered 12111124 exists, it will be started as in the case above.
Using external SMPTE to synchronise your Cues:
The ProScenium can read an external SMPTE source in two different ways:
If the PC you use is already equipped with a sound card (Sound Blaster compatible), you already have the capability to read MTC (Midi Time Code).
All you have to buy is a SMPTE to MTC converter, and a normal Sound Cable to split the
DB 15 connector on your sound card to MIDI In and MIDI Out.
A very good converter at a reasonable price is the JL Cooper PPS-2
http://www.soundtech.co.uk/jlcooper/stjlcpps.htm
Another option, if you have a free ISA slot, is an integrated MIDI/SMPTE card, like the interface card made by Opcode/Musicquest. They make a MQX-32M that supports 2 midi channels and SMPTE code directly. This would gives faster frame updates and will not drop every other frame. In the long run I think this would provide better, more reliable performance when synchronising to another device. You can get more information about the card from:
http://www.opcode.com/products/winhardware/mqx32m.html
Now that you have the ability to read SMPTE, all you have to do in ProScenium is to select Synchronise Crossfade Option 2 from the Configuration Panel, The time code will be displayed in a small box that opens up on the Screen. The selected option will be shown in the left panel of the status bar.
To make a cue list with perfect synchronisation, just click with your mouse on this panel while the time code is running to make empty entries synchronised with your time code, after you have done this, fill all the empty entries with the cues that you have programmed by just calling the cues and pressing on "Record" -> "OK".
3) CD Audio Position
The program reads the positioning on the CD (with the Track:Minutes:Seconds format). If for instance the CD is running Track 12:11:11 i.e. track 12, 11 minutes and 11 seconds, the program will check if a cue numbered 121111 exists, and will start it as in the case above;
4) MIDI Data Stream (All MIDI Notes)
The program reads the MIDI note via the MIDI interface (requires a Sound Blaster™ compatible audio card) and it runs the channel corresponding to the note. For example, playing MIDI note #36, will operate channel 1, playing note #37, will operate channel 2 and so on.
5) MIDI Data Stream (Note 96 (C8) - GO)
The program reads the MIDI note via the MIDI interface (requires a Sound Blaster™ compatible audio card) and it runs the channel corresponding to the note. For example, playing MIDI note #36, will operate channel 1, playing note #37, will operate channel 2 and so on. Playing note #96 (C8) will activate the "Go" command and playing channel #95 (B7) will step back one cue.
6) MIDI Data Stream (Control Change)
The program reads from the MIDI port the Control Change codes (still requiring a Sound Blaster™ compatible audio card).
These are the codes that are implemented:
CONTROL Action
Control Change 44 Value 0 to 4 Go
Control Change 44 Value 5 to 9 Back
Control Change 44 Value 11 Chaser1 On/Off Toggle
Control Change 44 Value 12 Chaser2 On/Off Toggle
Control Change 44 Value 13 Chaser3 On/Off Toggle
Control Change 44 Value 14 Chaser4 On/Off Toggle
Control Change 44 Value 15 Chaser5 On/Off Toggle
Control Change 44 Value 16 Chaser6 On/Off Toggle
Control Change 44 Value 17 Chaser7 On/Off Toggle
Control Change 44 Value 18 Chaser8 On/Off Toggle
Control Change 44 Value 21 Group1 On/Off Toggle
Control Change 44 Value 22 Group2 On/Off Toggle
...
The same for all 32 groups
...
Control Change 44 Value 52 Group32 On/Off Toggle
Control Change 25 Value 1 to 127 Starts cue 1 to 127
Control Change 26 Value 0 to 127 Starts cue 128 to 255
Control Change 27 Value 0 to 127 Starts cue 256 to 383
Control Change 28 Value 0 to 127 Starts cue 384 to 511
Control Change 29 Value 0 to 127 Starts cue 512 to 639
Control Change 30 Value 0 to 127 Starts cue 640 to 767
Control Change 31 Value 0 to 127 Starts cue 768 to 895
Control Change 32 Value 0 to 127 Starts cue 896 to 1023
Control Change 33 Value 0 to 127 Starts cue 1024 to 1151
….
Note that MIDI standard considers a Control Change as a state change therefore to command Group 1 to turn On and Off, the following commands are required:
Control Change 44 Value 21 Group1 On/Off Toggle
followed by an inactive Control Change, e.g.:
Control Change 44 Value 20 (no change, just passing to another control)
then again:
Control Change 44 Value 21 Group1 On/Off Toggle
while the sequence:
Control Change 44 Value 21 Group1 On/Off Toggle
Control Change 44 Value 21 Group1 On/Off Toggle
does not cause any Control change.
7) Wave Audio Position
The program reads the reference position of the Wave Audio file. If, for instance the returned value is 597, the program checks for the existence of a cue numbered 597 (with no spaces or delimiters) and if such a cue exists will start the Crossfade with the stored cue timing parameters.
8) Midi Audio Position
The program reads the reference position of the Midi Audio file. If, for instance the returned value is 597, the program checks for the existence of a cue numbered 597 (with no spaces or delimiters) and if such a cue exists will start the Crossfade with the stored cue timing parameters.
9) AVI Video Position (AVI, MOV or MPG)
The program reads the reference position of the AVI Video file. If, for instance the returned value is 597, the program checks for the existence of a cue numbered 597 (with no spaces or delimiters) and if such a cue exists will start the Crossfade with the stored cue timing parameters.
10) Send a Control Change 44 to the MIDI OUT Port
Every time a GO command is given on the main console and if the secondary console is configured with Synchronisation Crossfade Option No.6, the GO command will be received and actuated both consoles. This is useful to guarantee complete cross-synchronisation when running two parallel ProScenium systems
11) Internal Clock, opening Day file (1.asc-Sun, 2.asc- Mon...)
Very Important: the clock must be set in European Time or Military Time from 00:00:00 to 23:59:59
and not in standard USA Time A.M. -P.M.: you can go in Windows Control Panel/Reginal Settings to change the Time Format.
When ProScenium starts, it checks for a Day of the week file in your Martin ProScenium default directory in this order :
Trigger
Base Day to trigger EX.File Name
Year
Every Sunday 1.asc Will start every Sunday throughout the year
Every Monday 2.asc Will start every Monday throughout the year
Every Tuesday 3.asc Will start every Tuesday throughout the year
Every Wednesday 4.asc Will start every Wednesday throughout the year
Every Thursday 5.asc Will start every Thursday throughout the year
Every Friday 6.asc Will start every Friday throughout the year
Every Saturday 7.asc Will start every Saturday throughout the year
Quarter
Every Day in the 4th
Quarter of year Q_4.asc Will start every day from Sept to Dec
Quarter with Weekday specification
Specific Days in the
4th Quarter of Year Q_4_6.asc Will start every Friday from Sept to Dec
Month
Every Day in a
specific Month M_10.asc Will start every day in October
Month with Weekday specification
Specific Days in a
specific Month M_10_6.asc Will start every Friday in October
Week
Every Day in a
specific Week W_42.asc Will start every day in the 42nd Week of the Year
Week with Weekday specification
Specific Days in a
specific Week W_42_6.asc Will start on Friday of the 42nd Week of the Year
Specific Day
One specific Day
of the Year 12_25.asc Will start on Christmas Day
N.B. For ProScenium, Week 1 is assumed to be the first full week of the year and not the one in which January 1 occurs. (January 1 often occurs in week 53).
This means that if you are on Synchronise Crossfade Option No.11, and you start ProScenium on Monday, Proscenium will check for the file named 2.asc, and, if the file exists, it will load it and start the synchronisation with the information that is stored inside, this can be different for every day of the week.
If you need an "year long" synchronisation and you want a special program, for example, for Christmas, you can call the file 12_25.asc. The syntax is MM_DD.asc, for the 1st of January the name will be 1_1.asc.
You can also ask ProScenium to fill the filename for you just clicking on the menu "Files/Save as date file"
12) MIDI Data Stream (Program Change)
The program reads from the MIDI port the Control Change codes (still requiring a Sound Blaster™ compatible audio card).
The codes of different program changes (0 to 127) are the same of the Control Change explained in Synchronise Crossfade Option No.6
13) All MCI Positions (CD, AVI, MPG, *.* ...)
The program reads the reference position of any of previous described multimedia file. You can change dynamically the source of synchronisation.
14) Count Down Timer
This is a special function, useful in applications that have to show the amount of time before a specific event. Imagine, for example, that you want to show how many seconds are remaining in the millennium, until 1st January 2000.
First of all you have to find some fixtures, or group of fixtures that are able to show the 10 numbers, from 0 to 9 (Martin has some different solutions to do it). This can be done not only with gobos, but also with conventional lights, possibly a group of normal lamps with a small dimmer, similar to conventional displays.
having arranged your lights, you need to make 10 memories for each fixture (one memory for each number). The structure of the numbers uses the following format :
… X X X X X X X X
… 8 7 6 5 4 3 2 1
10:7 10:6 10:5 10:4 10:3 10:2 10 0-9
So you have to make cue 10 to show a 0 for the first fixture, cue 11 to show an 1, and so on until 9. For the second fixture you start with cue 20, to show a 0, after 21 to show a 1 and so on…
… 3 1 5 3 6 0 0 0
… 8 7 6 5 4 3 2 1
So for example to make the number 31.536.000 (one year expressed in seconds), ProScenium will add cue 83+71+65+53+46+30+20+10
This means that all you have to do is to make 80 cues with the right positions and the right numbers from 0 to 9.
After you have done this, access the Special Function Menu and enter the date of the event, for example 1/1/2000 0.00.00, or 25/12/1998 23.59.59 to have the count-down until Christmas.
Also, in the Special Function Menu, you can decide to show the time in seconds, minutes, hours or days.
Another option is to have the countdown running on preset A, or on chaser 1, to allow multitasking, leaving you the main crossfade for other tasks.
An interesting option is the following: when the countdown reaches the 0 (at the moment of the event), ProScenium will automatically send the last cue, (that you can link to any other one in the sequence, with a music, a video, or you can send a complete light show at the moment of the event (with the MCI commands and all the capabilities that you can have with a normal cue).
15) Crossfade Counter
This special function is similar to the previous one, but it can count the amount of time required to carry out an action. Imagine that you want to display the number of people that are visiting your museum, cinema, hotel, and you wish to project it on the main wall of your hall.
In the first instance, you must connect a Crossfade "Go" device (remember that in ProScenium you can trigger crossfades not only with the mouse and the keyboard, but also with the joystick, Midi, DMX…etc.). You can also add any sensor and interface it to simulate the joystick1 button1 closing 4 and 6 Pin in your Sound Card joystick interface.
Please contact your dealer for more information about the sound card Pin-Out.
This functions allows you to increase of 1 the main counter, every crossfade, or every specific number of crossfades.
If you select to show the counter on chaser 1, every time you press a "go" you will see the counter projection increasing of one unit.
For details of how to make cues for this function, please refer to previous section 14) Count Down Timer
16) MIDI Data Stream (Pitch Wheel [value]-Cue No.[value])
(Pitch Wheel). The program reads from the MIDI port the Pitch Wheel Value (still requiring a Sound Blaster™ compatible audio card).
The codes of different Pitch Wheel values directly call the respective Cue number.
For example, receiving the Pitch Wheel value 100, will start cue 100 with the respective Time In and Time out, MCI command and so on.
17) MIDI Data Stream (Note [value]-Cue No.[value])
The program reads the MIDI note via the MIDI interface (requires a Sound Blaster™ compatible audio card) and it runs the Cue corresponding to the note (with his Time-In and Time-Out). For example, playing MIDI note #36, will start Cue 1, playing note #37, will start Cue 2 and so on.
Add 100 to set both Internal Clock and Selected Synchro
If you want to run the internal clock at the same time as any of the 17 Synchronisation options above, you just add 100 to the Sync number.
For Example Sync 103 will trigger Internal clock + CD-Audio.
In order that the internal clock cues, do not overlap with either the CD-Rom or other Multimedia TimeCodes, they will be preceded by 8888.
For example if current time is 12:11:11 (hours:minutes:seconds format) and a cue numbered 8888121111 exists (requiring the plain number with no space and no delimiter), this cue will be triggered.
Contents