Tempo/Speed triggering

[UniCav]

In trying to get my system tailored to our shows one of my biggest issues seems to be tempo control. Since 99% of what we do is full live with no backing tracks to sync by I have to match the speed of my sequences to what's happening on stage. I've tried using tap sync but no matter what I use for a keyboard shortcut there's a latency that I can't seem to overcome. I tried setting Up and Down arrows and also PgUP PgDn to the speed up and speed down but it doesn't seem to work. I'm planning to purchase and X-Keys USB pad for external control but I'm also considering a midi controller on the chance that will be more useful. Any suggestions appreciated!

[UniCav]

Addendum - I got ahold of an Alesis QX25 and hooked it up. Went to midi controls and hit start, edit, picked Page Independent, Tap Sync and hit a pad. It showed the pad selected and assigned to Tap Sync.
Hit save and went into Cues and started a sequence. Hit the pad and nothing happens. Tried different pads, changed the midi channel from 1-2 and back. Couple other things but no matter what it wouldn't set the tap sync. Also tried setting a midi key to toggle sequence 1 and that didn't work either. What am I forgetting to click to make the midi controls work?

[jdmyers]

After you assign and edit them (under settings / external control / MIDI), did you click START first, then SAVE?

[UniCav]

Yes I kept it on Start and then hit Save. I'm wondering if the Alesis QX25 sends CC signals like FS requires. The manual is very vague about CC functions. I think you may actually have to edit every function on the thing with software to make it do that and if that's the case it wouldn't be worth it. I still don't think this is going to solve my problem with the latency in Tap Sync. Ultimately I need a way to set the master speed to a metronome software or something.

[UniCav]

Just hooked the QX25 up to another PC and got the same problem trying to use the keys or pads. But discovered that using the knobs or transport buttons does work. So the problem must be the keys and pads don't send CC data. Still seems more accurate than mapping Tap Sync to a keyboard key and the master speed is adjustable by the knob which is promising.

EDIT - Not sure if that's actually going to work. Although on the Cue List it shows the speed of the sequence changing and running, the Fixture color indicator stops moving. I'll have to test this with the whole rig connected to see what happens. I still apparently haven't learned much about how to really use the Cue List and buttons because searching the forum for things like Midi and Metronome and the like I keep reading about using the Manual Trigger to actually switch between sequences in a cue list or Go Monkey for a specific song. I've only been setting up sequences and switching between them during songs at random and fighting the speed issue. I still have a LONG way to go before I have this figured out.

[Kings]

Some midi devices will put out a variable midi signal of between 0 and 127 when you hit a key (much like a piano where you can adjust the volume of each note by hitting the key harder). FS only recognises a signal of 127. Most midi keyboards have some sort of set up software or inbuilt function that allows you to generate 127 regardless of how hard you hit the key/button. I think you can also decrease the value recognised by FS by adjusting the FS ini file.

[UniCav]

Ahh good info Kings I'll check that

[UniCav]

Good FYI note to anyone working with MIDI. Using my friend's QX25 on my old WinXP laptop all it showed as the identified MIDI Interface was "Multimedia Audio Device" while on Win7 it showed "Alesis QX25". I just purchased an Akai MPD18 which has the Full Level button on it and it also showed up on my WinXP laptop as the generic "USB Audio Device" and also would not work, except for the CC Slider. I just connected it to my Win7 Laptop and it immediately showed up as "Akai MPD18". Installed Freestyler, stuck my 2 fixtures in and one sequence and set MIDI control to trigger a pad for Sequence 1 and VOILA! So the problem must lie with limitations of Windows XP. Now to copy all my chases to my work laptop and set all my presets and everything back up