jimbo-nomads
-
Posts
22 -
Joined
-
Last visited
Posts posted by jimbo-nomads
-
-
show file attached. It's the second fade cue that's the problem. (There is a long wait before the 1st fade goes)
-
Thanks. I'm next at the theatre on Monday & will grab the show file then.
-
I have a cue with general stage lighting plus a set of led bars simulating early morning. The next cue is a cross fade to bright morning on the led bars over 5 minutes. Done manually on the go button the stage stays up and the led bars crossfade colours. Done automatically the whole stage goes dark and comes back over the 5 minutes with the colour fade.
Any ideas?
-
Edward,
Thanks, I'll check that next time I'm at the theatre.
Jim
-
Try8ng to create an effect by pushing master playback down & up to flicker the lights but if I go further down than 50% playback switches back to LX1.
Any ideas?
Jim
-
Upgraded & problem solved
-
Fixed. As there are 2 DMX outputs and we are only using 1 it was trying to mirror DMX 1 o to DMX 2 and this caused the interaction problem. Turned off DMX 2 and all ok.
-
That was my thought but the patching hasn't been altered. All worked fine before the upgrade! Will send xhowfile when next at the theatre.
-
Updated to .4 but when loading the last show file there are no descriptions on the cues and stepping through the cues does nothing to the lights but the normal lights through dimmer packs work from the sliders.
Also the moving heads don't settle down. Still occasional flashes of colour from them and operating the sliders for the normal dimmer pack lights causes interaction with the moving heads.
I've upgraded to .4 but still the same! Any ideas?
Jim
-
Latest update:
Found that taking the master playback down to 0 and back up clears it and all required lights come up.
Last show of run tonight so will update be t week & report back.
Jim
-
Edward,
Programme Time was set to 5. Have cleared it but at every switch on still no output for several minutes and then everything works fine.
Hate power cycling because I have to calibrate the monitor again which should be cleared with upgrading the software.
After this run I will update the software and see if my 2 problems go away.
Regards
Jim
-
Thanks Edward.
Planning to upgrade after the current show run finishes.
Regards,
Jim
-
Have an FLX S48 with the recommended Iiyama 17" touch screen monitor. It won't work as touch screen unless it's calibrated. After calibration attached a keyboard so I could press the "Enter" key. It then works fine till it desk & monitor are powered off.
When it's all powered on I have to go through calibration every time. Any ideas?
Regards,
Jim
-
Edward,
No, didn't manually release/turn off playback.
Will be in touch if it happens again with the show file but it is a very simple one.
Thanks,
Jim
-
Edward,
Thanks. As it happens that was the problem. I don't currently have an external monitor (on order) and thought I'd read that the desk automatically detected the external monitor.
Jim
-
Hi Edward,
No to both questions. I used just stack 0 and didn't touch the encoder wheels as far as I can remember.
Is there any way to temporarily disable that encoder wheel?
Jim
-
Sorry forgot to sign in. This is me not guest
-
Hi,
When you take a channel up and then bring it back down, you've put '0%' into the programmer, so submasters and memories can't affect that channel until you clear the programmer (the programmer always wins!).
Press the clear button, and then your submasters and memories should work fine?
Regards,
Jon,
Thanks for that, I'll try that next time I'm at the theatre (Next week).
Would pressing the clear button after an update solve my other problem of an update not always working?
Thanks,
Jim
-
IS this really the only occurrence of this problem?
Can anyone give me a clue as to what the problem is?
-
After upgrade to 7.6.0 whenever I take any slider up & down to zero that channel will never turn back on in any cue even if it was programmed.
Only fix is to power off & back on.
Any ideas?
Flx s48 auto problem
in FLX S24 & FLX S48
Posted
Cue 4 to 5 happen 10 pages apart. The problem shows itself from 13 to 13.5. Tonight is the last performance so won't be able to check it out for some time now. Thanks for looking at it and I'll get back to you at some point.