kgallen

I concur with 7.8.5, Clear+Fader Func can force the release of a UDK (with Setup Release=No). Thanks for the ZOS on Clear+UDK not working.

Isn't that the wrong way round? Surely the grey box should be there if the fixture needs to move on dark, so you 'don't press go' - user can't be expected to know some fixtures will want to MOD and wait 4s just in case. i.e I wouldn't know the fixture is part way through a MOD because the grey box comes only when it's done. So grey box needs to be there if fixture wants to MOD, and grey box goes once any MOD is over - then I know I can GO as there are no grey boxes on screen. Must be me bein' stuupid Back on my original query and using your case study, I still don't understand why fixture 49 didn't go red with playback 1 at 100% as it should have been recorded with R=100,G=B=0 not R=G=B=0. I have the same 'problem' with fixture 53, which should be in playback 1 as B=100, but if I overlay playback 1 on cue 4, then it goes to R=G=B=0 so it's dark. I concur from watching the display the desk operates as you say, but as yet can't make that stack up in my mind. But basically I didn't manage to record my 'look' of cue 1 into my 'submaster' (playback 1) for recall at an arbitrary time. I tried setting playback 0 to release on lower enabled, so playback 0 dropped all control, but playback 1 still didn't give me the colours I expected. It's just like one of the colour parameters wasn't tagged when the playback 1 was recorded. I tried the same process and recorded cue 1 into playback 7 and it worked just the same (which I'm sure is a relief to you!) So how? At least when I release playback 1 they go back to what the cue stack says. Must be mi' age!

Hi. Just having a play with 7.8.5 and there is a bug with the current/next cue colour bars not shown if cue 0 was shown. Using this showfile, Go+0, go, go, now the colour bars have gone but Current:2 Next:3. In this step, cue 0 is purged from the display and it seems the colour bars are not redrawn. Go again and the colour bars reappear. Also cursor keys bring the bars back, but e.g. down puts both bars on cue 2 when Next:3.

Try this one. No detail in the manual for the sub-channel detail, so you'll have to suck-it-and-see! Note - no 12 channel mode; manual provided has 8 and 13 channel modes... Kevin Two separate fixture definitions within the one manufacturer, one for 8ch one for 13ch. I usually create the larger one, then chop down for the smaller. Make Pan and Tilt 16-bit ( Size=Word {16-bit} ), then set the Channel (LSB) for the Fine, and the Channel (MSB) is then the Coarse. beamz_mini_wash_7x10w.ift

JB you're such a sweetie OK, give this a go. I've added a virtual dimmer for the RGB as there is some yukky half-baked dimmer on channel 6 mixed in with other crud that makes that dimmer a bit hard to use. Let me know if it doesn't work quite how you'd like it. Kevin Forgot to allocate the wheels for you. See this updated one. equinox_party_par.ift

Please post a link to the manual. Thanks.

Hopefully a daft question, but do you have a DMX terminator plugged into the last fixture in the DMX chain? Didn't see this mentioned above but could have missed it...

Hi Lazer, I'd like to help, but sorry I don't understand: Maybe you could rewrite this a different way?

Hi Jon, That's great info thanks. I'll have more of a play with the sequence of events against your explanation. So I still need to work out how to program and use an overlayed playback in the context of what MOD needs to do to reconcile the overall state considering the other non-released playbacks. Complex for the software to handle with all of these concurrent possibilities! Thanks, Kevin

Hi Jon, Thanks for taking a look. Ummm, ok. I guess I'm confused how the MOD behaviour got carried across to another Playback. I assumed MOD actions got computed on the fly as the cue stack was run, rather than being captured as part of a RECORD step. I understand "Don't MOD (colour|beam|pos)" can be set as a Cue Setting, but I didn't have any of those. So in terms of how I recorded the cue to Playback 1 (using it in a "submaster" context), what should I have done differently? This is interesting, I wondered what the grey boxes were. Can you elaborate a bit more on what this means/indicates? It would also be useful to add to the manual a complete table of what various colours mean (as in blue=fading up, green=down, purple=tracking, red=?? [overlayed?], yellow=??, grey box=some MOD activity). Thanks, Kevin

See earlier answer given by one JonH! http://zero88.com/forum/topic/7327-should-flx-have-subforums-how-do-i-bugs-errors/ Plus the one in this thread!

All of it? Chilli is an install (rather than a portable) dimmer product. First line means you can hard wire the DMX connection wires to internal terminal blocks rather than via an XLR5 plug. The DMX address is set via the front panel regardless of how you connect DMX. Second line means the Chilli includes a DMX termination capability for use if it's the last DMX device in the DMX chain, and you set this by some internal switch mechanism. DMX 512-1990 is the specification for the DMX protocol used to talk between the lighting desk and the dimmer. Enough? (I'm slightly confused as your intro post says 'highly skilled in lighting systems', so maybe there's more to your question?) Hope that helps anyway. Kevin

Hi Johnny, It looks like you've got your fixture colours and palettes sorted, great! For timecodes, maybe take a look at the Cue Settings field in your cue stack window (e.g. Playback 0). For a given cue, if you use the arrow keys to move right to the Cue Settings field, then <Enter> you should get a Cue Settings window where I believe you can set MIDI timecode (or realtime). Kevin

Cheers, Hamish, glad it worked ok! Regards, Kevin

Yes, but the Illusion doesn't have a patented non-scratch surface like the FLX, so I think you'll find the ongoing repaint costs for the Illusion will make it's continued use as a stage manager communication tool no longer financially viable. What I mean is, an upgrade to FLX is inevitable. I can put you in touch with a good supplier if you like.

With virtual dimmer for RGBA "component" as Jon suggests. As he says, there is one in the standard library, but you've got the package together here if that's more convenient. chauvet_colordash_batten_quad_6.ift

Here you go. It is a complex one with lots of modes and lots of channels, so let me know if you see any errors. Regards, Kevin JonH - you owe me for this one , 80 channels indeed... Philips_eSTRIP_10RGBW.ift

For user Wier69 (http://zero88.com/forum/topic/7338-chauvet-beam-led-350-z88-profile/#entry28717) 8ch and 14ch options Gobo images included Chauvet_Beam_350.ift

Wow, that was a busy one. Give this a go... Regards, Kevin Chauvet_Beam_350.ift

Here we go, showfile. Hopefully Jon can tell me what I'm doing wrong! testing3.isf

Can you point me at a manual and I'll have a go. Chauvet have a "Beam" and a "Spot". You say "Beam" but then "Profile" which means I'm not sure which model you really mean. This (Beam LED 350): http://www.chauvetlighting.co.uk/products/manuals/Intimidator_Beam_LED_350_UM_Rev3_WO.pdf or this (Spot LED 350): http://www.chauvetlighting.co.uk/products/manuals/Intimidator_Spot_LED_350_UM_Rev8_WO.pdf ...or something else entirely!

Hi Jon, I see you're answering posts - do you have any comment on this one? Thanks, Kevin

Hi Jon, Thanks for the detail, that's really interesting.I didn't see the "green/red button" info in the User Manual. It would be great to be able to capture all of these "application ideas" somewhere. Clearly when developing and spec'ing the console you tried out many scenarios from your own usage and refined the operation. Certainly on the course you had some good examples - with a small number of key presses you were generating some fundamental building blocks onto playbacks. As yet I'm failing to really replicate these in the same slick way! (More sick than slick!) Maybe there could be a subforum for FLX for "application ideas/examples" - this would allow users to exploit the power of the console and the efficient programming methods you've built in. Also it could capture the key "tricks" required e.g. "at the step, SmartTag must be turned off so only xyz is recorded" etc. Thanks, Kevin

That'll be it! Thanks. One footnote for the manual and on-desk help pages!

Hi guys, Thanks for the comments and ideas. I've ordered a small Belkin 4-port hub to ease congestion on the ports. It's an unpowered one, but keyboard/mouse/USB stick shouldn't present too much of a current load (and Jon assures us the FLX USB ports are man-enough for anything!). Derek - thanks for the Maplin link, that small keyboard/wireless mouse is a good idea. Ironically I also got one of those right-angle USB adaptors in an attempt to plug the desk light in one of the back ports (leaving the front one free for a memory stick)... but I was scuppered by the rear overhang. Looks like I might have a new application for it! Cheers, Kevin Oh I see Ian, this is what you use your FLX for is it? LX Cue 13 - Go... ouch! http://www.instructables.com/id/Hack-your-usb-missile-launcher-into-an-quotAuto-/