Jump to content
Vari-Lite Controls Support Forum

PJRichards

Members
  • Posts

    8
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

PJRichards's Achievements

Rookie

Rookie (2/14)

  • One Year In
  • First Post
  • Week One Done
  • One Month Later
  • Conversation Starter

Recent Badges

0

Reputation

  1. Hi Edward - sorry just to check one other thing If for example in a festival situation you suddenly want to use a look you've not already used so you built it using pallets in the programmer - I am correct to think that it's not then possible to have for example a white strobe bump on a MFF which would successfully trigger more than once over the top of this - I'd have to quickly save a cue somewhere with the new look on it and load it in order for any other playback to bump over the top more than once. Thanks
  2. Thanks! Had not spotted the little red little showing the re trigger clears the programmer, used to things staying in the programmer until I clear it! That's fine - now understand its limitations can try work around them Cheers for the rapid responses!
  3. Thanks Edward - Try pushing fader 7 up again and releasing after you've completed the above, so yellow is still on the command line, nothing cleared.
  4. Hi Edward - yeah I would agree I would expect it to stay the colour it was last told on the command window - but seems to be the playback releasing is telling it to revert to default. Attached test file - prepping for a festival and was going to give the FLX a wirl Playbacks: 1 = LED Par intensity 13 = LED Flood intensity 7 = LED flood colour stack 15 = Mover intensity 16 = Mover colour stack 17 = Mover Beam stack All stacks have just got 2 cues in just to have a play to see if I could resolve this issue. If 7, 16 or 17 are faded down / released then the fixtures return to default for that attribute. Hoping it is just something I've done wrong in the programming Thanks Y FEST 2023 Stage 2 - Test File.zos
  5. Could you possibly explain the priority levels for items on the command line when busking a show, it seems to be that if you put a manual intensity on a group of fixtures, say "Group 1 @ 10%" then as you would expect you get those fixtures to stay at 10% including when releasing any active playbacks which also contain intensity information. The programmer / syntax is acting as priority. However if you use a pallet for an attribute then whilst it initially works and you get the look wanted, if you happen to release an underlying playback which also had that attribute information on it then it seems to release the fixture back to default values for that attribute. Should it not be that the syntax / programmer is still priority and when you release a playback any attributes would refer to anything on the command line as the intensity does but it only seems to control intensity nothing else... Example - MFF1 = Intensity only for group 1 at Full. MFF2 = Group 1 in red push both faders up - fixtures are at full in red - as expected then manually change the intensity to 10% and change the colour to blue on the command line - again as expected fixtures are in blue at 10% however if I then release MFF2 the colour reverts back to the fixture default value but the intensity remains at 10%, is there a way to make sure that all information still in the programmer stays as priority until it is cleared so I could release the colour MFF but the colour would stay at the value sat on the command line? (coming from a chamsys background where the manual values in the programmer would be priority unless you set a playback to be a higher priority for example a white strobe set to bump over everything)
  6. Thanks Edward I think I'd concluded it just wasn't possible - the thing that threw me was the fact that the syntax saying "group X" "Colour X" is still sitting in the command line so was hoping that it would be possible to revert back to the programmer and the command line in the same way that it reverts back to the most recent playback as the most recent action outputting was actually the command line entry...possible future update?
  7. Smart Tag is off - it works absolutely fine if I've got a base colour running in another cue stack - can bump over not a problem but if i've busked in a colour manually into the programmer using a colour pallet - press the white cues flash button and it then clears this manual colour out when it is released.
  8. Hi I'm trying to record a playback so that when its flash button is pressed it bumps all the fixtures (LED) to White and then releases back to the colour that is currently in the programmer - I've disabled smart tag so only colour is recorded on the playback and it works to bump to the white but then releases back to the fixtures default colour and not the colour that was previously selected...it's almost like it is clearing the programmer - is there any way around this? Basically I want the flash button to override LTP whatever is in the programmer but not clear it...tried all the settings and options used in the mixing colour tutorials / previous forum posts but they don't seem to be working...
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.