O Thompson

Thanks for the response Edward, i hope you are well too? Please see an older show file attached. I have disabled all of the protocols except dmx, with no change. We have no other consoles (digital or otherwise) connected... Generic 2023.zos

Morning all, I've recently updated the firmware on my FLX console. It was a pretty significant jump, having not updated for the past 2 years... I now have some odd behaviours that i can't explain, and the only way to resolve them is to clear the desk and reprogram (which i am trying to avoid). I'll try to explain this as best i can. Some context... I have a generic show file that is used for most events in the venue. This worked fine prior to the update, and also worked find via capture after the update. i have a mixture of dimmed fixture (DMX 7-24), LED's and non dims (DMX 1-6) added to the console with a number of playbacks to control them. I have also programmed all RGB LED fixtures to allow for colour mixing. The non dims are set to "on" as default, so they come on when the console is powered up. The odd behavior is that none of the fixtures seem to work via playback or as individual channels. The non dims are also now "off" despite showing as on, and oddly they will trigger on then off at random DMX value when using the control wheel for the load of each non dim channel (CH 2371-2376). Furthermore, when using alternative channels, such as the dimmed fixtures (CH 7-12), the non dims trigger on and off at random values when the dimmed fixture channel faders are raised / lowered... but the dimmed fixtures dont function and are not on the same DMX address. If I clear all playbacks and fixtures, and add JUST my dimmed fixtures again, despite having different dmx addresses, the non dims and the dimmed fixture go to full as soon as they are added. However when i hit setup, the non dims go off and the dimmed fixtures act as expected. I can repeat this process with other fixture, and the non dims always seem to be triggered on with any dmx value / fixture i add, until i hit setup and return to show control. If i fully clear the desk and start from scratch, i intermittently get the same issue, but it seems to only affect the non dims when i add the first lot of new fixtures, after hitting setup once to return to show, and then go back to add fixtures again, i don't seem to have the same fault. Has anyone else experienced a similar issue? I have attached the show file in case there is something there that is off, if anyone has the time or inclination to take a look... Kind Regards Olly Generic 2024.zos

Morning all, I have pre plotted a show virtually, using capture. unfortunately, the movers on the virtual rig are rigged at 180 compared to the real rig... I don't have the option of simply rotating the rigged lights, but i have already programmed some intricate moves for scenes of the show. Rather than having to redo this, is there a way to invert the programmed data? I have tried inverting the fixture in the setup menu but it seems the desk anticipates this and applies the inverted setting to the playbacks, so my issue remains.

ah... that would do it. Over sight on my part. Thanks

Hi Folks, Its been a while and I hope you are all safe. I wanted to know if there is a way to prevent the blackout and grandmaster from affecting specific channels? Reason for this is... I have some moving heads, powered by colour source dimmers. The dimmers are set to relay, so that they "turn on" when a fader on the FLX is above a specified threshold (10%). I have patched the relays to the FLX and changed the default intensity of those channels to 100%. This means the moving heads are powered whenever I turn on the FLX. Now I want to utilise the grand master / blackout functions, but obviously this falls below the relay threshold and the moving heads lose power. Is there a way to set a channel safe option, removing them from the blackout function?

Thanks, Ill give that a go.

Thanks for the reply, Your suggestion, i think, is similar to my initial set up of using a 1 shot chase on a playback, built on similar cues... Firstly, I have found that if i only use 2 cues in the stack... Cue 1 - Fixtures fade to 0% Cue 2 - Fixtures move, change to white and fade up to 40% Then the following happens... Fixture fade to 0, then fixture fade to 40% whilst moving. So the move is still visible. If i do the following... Cue 1 - Fixtures fade to 0% Cue 2 - Fixtures move Cue 3- Fixtures Change to white and fade up to 40% This works as required, but should cue 2 in this case be necessary? or should "move on dark" negate the need for this? Moving on, how would i reverse this? if i lower the "piano" playback, I want the fixtures to fade out, move back to the position (of which ever playback is active) and then fade up again (unless the previous playback has altered / relased)? Is this possible? As it stands, releasing the piano playback will result in a live move of the fixtures to the previous playbacks state. Finally, Can i set the "piano" playback as "Always Takes Precedent"? For example, i have multiple washes using the mentioned moving head fixtures. The current solution allows me to "borrow" some of those fixtures for my piano. But... if i then want to change the wash light on stage, whilst still keeping my piano light, i cant. The fixtures will be taken over by any other playback using the fixtures...

On top of this, is there an option to set a playback as "always has precedent"? for example if i run the playback described above, i dont want my piano light to be taken over by a wash playback? i want the piano playback to stay active until released?

Im fairly sure this isnt a simple request, however... Let me try and set the scene... I have some moving heads used as wash lights. They are rigged FOH and provide down stage wash. I have a number of playbacks using these fixtures to create varying colours of wash on stage. On top of this, i have a couple of override playbacks (LTP) that "borrow" 2 or more of these moving heads for a piano light, focused in the auditorium. I have tried to do this using a cue stack turned into a 1 shot chase, which works for the initial move to the piano, although its a little glitchy and time consuming. selected fixtures fade. selected fixtures move to new position. selected fixtures choose colour. selected fixtures fade up. Is there anything i can do to alter the behaviour of the "release" of this playback? so that when the the fixtures fade down, move to previous position and fade back up? rather than simply move and alter colour "live"

Ha! just got it back from repair so i hope not...

Thanks Edward, Much appreciated as always.

ok, so by loading capture before zeros, and then toggling between the PC ip and the 127.0.0.1 ip on the universes section of the FLX phantoOS, i get control... not sure why the toggle between ip's is needed. but in this case it works.

Right... found a setting under the "universes" tab of setup that allows me to alter the IP for CITP. this works with the Dockhouse demo, but not when im creating a new project... is there a specific setting in capture that i might be missing?

I actually had it working quite successfully with the physical console. However in that case it was on an isolated network. We have a separate network setup in the venue for remote control of the FLX and X32 consoles, which allows me more control over the IP allocations.

ah ok. In that case, on the FLX sim there is no "visualiser" option. I have already enabled remote apps in devices (is this required) and selected the 127.0.0.1 IP option.

It may be worth noting that i am using a works PC and i am unable to re allocate the machines IP

Thanks for the swift replies... Edward, the link you provided doesn't seem to help... Shift +F10 has no response when using phantom ZerOS with the FLX sim?

Hi Folks, can anyone assist with ZerOS and Capture? I have the capture demo running on my PC and Phantom ZerOS also running on my PC, but i cant seem to get capture to see or respond to ZerOS.

Desk has returned... but with a faulty touch screen now...

Hi Edward, Thanks for the reply. Having used an air duster and booting in test mode, the fader is obviously not functioning correctly. When "delicately" used, the fader test display shows only a 3/4 travel when the physical fader is at full... when a small amount a pressure is applied the test screen shows the fader jumping along the full length of the fader travel. I have emailed support with these details. Many thanks.

Should be well within warranty, purchase order was May 2019 with delivery sometime in September... Just wondered if anyone else had a similar fault rectified?

Hi folks, has anyone else experienced this?... Fader 19 on our console is a little temperamental at the moment. When any pressure is on either the fader (or anywhere along the fader track) the intensity of that fader starts to jump? this doesn't happen on any other fader, and im talking very little pressure... for example when pushing the fader to full, the pressure of removing ones finger from the fader can cause the intensity to jump from 100 - 50, and you need to "tap" the fader to make it jump back to 100... I have a video clip, but im unable to post it here due to its size...

Thanks for the reply. The fade intensity of the fixtures is100% when the chase was programmed. The ramp up setting is also 100% in the mdf settings page. I have an inhibit set for the fixtures in the chase set to 70% for fixture 1 and 100% for fixture 2. i will send the show file once I get back to the venue.

2 threads in 1 day... sorry... I have since upgraded to the latest FW and all is working well, with the exception on 1 "glitch" that i hadn't noticed in previous versions... I have a few simple chases programmed to individual MFFs. These are set to global bpm and a number of them have either cross fade or ramp up / down applied to them. I have then set the "play" button of the master play back to be a tap tempo for global bpm. With the latest firmware i have noticed that when global bmp is applied to the chase mff, the ramp up / down or cross fade options are ignored and the chase steps "snap". Is this a known glitch? or something that has always been present but I've overlooked? and is there a way to combat this? Olly

so in essence, id need to create "sub fixtures" by patching manually on the desk... For example i would patch ch1 as a "dimmer" for intensity and they patch a 3ch "LED" fixture for each sub fixture (2-13)? Hadnt thought of doing it this way. It may be faster to program than a single 14 ch fixture with encoder only control... Thanks for the input