kgallen

This link will get you going with the fuses. I'll have to take a look at mine for the holders... Fuse holders probably as here: RS 344-5591 (MOQ=5 though...) Farnell 1703163 Rapid 26-3082

Are you boys working on the "Easter Egg Calendar" yet? We need a regular "fix" now you know. Tyler will be able to have an egggggg..ggg.ggg...cellent time making them.

I think I can do Clear Fixture for you:

Check the colour fade time in the cue (defaults to 3s) [a submaster is really a single-cue playback], which will affect the fade time for the colour when going into the state. Also with Setup+Playback Button, under Raise and Lower, look at the colour fade time (I think that defaults to 0s), which will affect how quickly the colour releases once the fader lowers. Have a play with those two settings - it can be confusing at first but once you think about it, it (usually) makes sense! Kevin

Hi Edi, Slightly (/completely) not answering your question, but this article might help you out with your experiments in this respect: http://support.zero88.com/Consoles/FLX/1014413041/RGB-Colour-Mixing-on-faders-FLX-Series.htm Regards, Kevin

Hi Mark, I'll attempt a half-baked answer until Edward comes along, as you might be trying to do this now. In theory you don't have to do anything for move on dark, the desk just works it out for you. It's possible, depending on whether the movers are used in your previous cue (0.3?) you don't actually need your cue 0.4. If your movers are unlit in 0.3 then just record 0.5 with the position/beamshape/intensity you want. When cue 0.3 has run, say your movers fade out in 0.3, once they've done that the desk will "move on dark" them ready for the intensity build in 0.5. If you need the 0.4 step to do the move, it's possible the desk is not recording those parameters because the fixture intensity is at 0 - if you're using Tracking+SmartTag then this might be the cause (Edward can clarify this). I think the way around this would be when you RECORD your 0.4, in the Record window that pops up, turn off SmartTag (assuming you're using SmartTag usually, make sure this is back on for the next cue you record). If you've just moved the movers and set the gobo etc, then the position and beamshape attributes should be "tagged" so these should get recorded into the 0.4 cue. Then when you record 0.5, the intensity should be up but the position/beamshape should track from 0.4. Hope that helps. Let us know how you get on. Kevin

Hi Edward, Really? If you update a cue and use Cue Only, surely internally in the desk database it has to then go and change the following cue to reinstate the fixture value that was updated Cue Only in order to remove the tracking behaviour. i.e in updated cue n, the fixture takes the update value then in cue n+1 the fixture has to be set back to the values from cue n-1. This wouldn't be necessary in Non-Tracking. Sorry - an academic comment really, we'll not get into exactly how the software is architected, I'm just surprised it's "the same". Kevin

Yes it just makes that record/update operation record everything. The following cue you record will just record the changes again. If you set the desk into the Non-Tracking mode, (I believe) it will always record everything (intensity, colour, position etc). However if you have anything other than dimmers patched, you'll probably want to use the Tracking mode (I just use "Tracking Basic") because that takes most of the worry out of LTP attributes like colour and movement. Not sure if it will help, but there are a few external documents linked here that talk about tracking. The ETC one is ok.

Rob, Don't be daft, denigrating yourself. It's new to me too. Fortunately usually tracking "just works", certainly with SmartTag on With your edits, what you needed to do was select "Cue Only" in the Record/Update window. Otherwise the change "tracks" into the later cues - that's what tracking does - the "Record" operation with SmartTag only captures the changes from one cue to the next rather than everything. This means that is a light isn't set to change, it's not recorded. If you want to store "everything" - and I usually do this for blackouts, then use Shift+Record, which comes up as "Record All", and does just that, so all intensities get recorded in the blackout cue, and this "blocks" any lights that are tracking from "bleeding through". Stand by for a much better explanation from Edward or Jon! Kevin

The Frogs absolutely do support virtual dimmers in the fixture definition . It was introduced in software 10.10 and bug-fixed in 10.12. See: http://nr1.s3.amazonaws.com/kb/2AD62C9/3879A76B/3A210339/32/FrogOS Release Notes v10.12.pdf Of course the fixture definition has to define the virtual channel, which should be the case in Zero88 Fixture Library releases. We've been here before... I'll find the post in a minute! Here :

Hi Phillip, Do you mean the screen built into the FLX or an external touch screen monitor? If the external screen, after you have started the Calibration, press the Update key and then see if the monitor is responding to touch. If the internal screen, sorry the Zero88 guys will have to help you out... Kevin

Hi Andy. Latest Frog software is 10.12 but you can update the fixtures independently. Either look to a more recent fixture library from Zero88 with the fixtures you need or alternatively create your own fixture definition file using the fixture editor tool. All are downloadable from the Zero88 website. FrogOS 10.12: http://support.zero88.com/Legacy-products/Legacy-Consoles/Frog-Series/975242041/Frog-Series-Overview-Software.htm Fixture Library 34 (also read info on fitting on a 1.44MB floppy disk): http://support.zero88.com/Legacy-products/Legacy-Consoles/Jester-ML-TL-Series/975203021/Fixture-Library-Release-34-Jester-Series-Frog-Series-Illusion-500-Diablo-Sirius-250-500.htm Fixture Tools: http://support.zero88.com/975064841/Floppy-disk-Console-Fixture-Library.htm Kevin

Hi Thierry, It's not about more cables/Universes, it's about patching your non-compliant fixtures at DMX addresses above 32 (or above 257) on the one universe you have installed. However I see you've listed some fixtures (LinearLeds 36x10W RGBW) that I'm sure gobble up DMX addresses so you may not have enough addresses from 257-512 to do this. Also you might not want to get involved in RDM fixture configuration if you have a stable setup using manual configuration that is working perfectly well (i.e. not using technology for technology's sake!). All the best. Kevin

Hi Thierry, A Happy New Year to you too! In the thread below, Jon suggests a workaround for a DMX Universe with fixtures who do not behave in the presence of RDM packets. See the section on DMX address: Regards, Kevin

Hey - you're never that quick on my questions! Edward's answer is much better than mine, though - he uses the correct terminology!

This is because when you drop the fader it "releases" the playback. This means that the playback stops having any control over the lights. If you have no other playbacks active then there is nothing else controlling the lights, so given they have to have "some" position, then the desk will drop back to the fixture default - which is the same as Home but with zero intensity. What you need to do is to stop the action of lowering the fader from releasing the channels. On FLX this will be Setup+PB button then under Raise and Lower, turn off Release. I suspect FLX S will be the same. If not, Edward will be along any moment to put the story straight, but this information might get you going in the interim...! Regards, Kevin

Hi Edward. Brilliant explanation - thanks for taking the time to explain that for me, much appreciated! That’s one for next year’s Advent Calendar! Cheers, Kevin ps Ooooo FLX T- shirt...

Hi Edward, Thanks for your comprehensive response to my additional queries - I shall try those! For (3) I'm really surprised this isn't "Allow Stomping" - when you say you reported ZOS-8389 can you elaborate on the issue you found - I read your reply as you found an issue with stomping, rather than with Intensity LTP - maybe I misunderstand which part of (1) you found an issue with! I thought "stomping" would mean that the playback could "stomp all over" another playback and thus if my PB1 has "allow stomping" then it could "stomp all over" what the Master PB wanted to do (even LTP) and thus would support what I was looking to do in (3) i.e. PB1 keeps control of the HTP and LTP channels. Thus I'm not sure I understand what "Allow Stomping" actually allows! The FLX manual says "“Stomping” occurs when a playback takes control of all the channels from another playback" - but clearly I misunderstand here too - maybe related to the "release" part. Could you give me a deeper explanation of what stomping actually is and how the "release" part factors in to the operation? Maybe the manual could have a better explanation as it seems a more complex concept than the one sentence in the manual would have me believe! Thanks again! Kevin ps That's another couple of ZOS's with my name on. Tell Jon I'll take a zero88 t-shirt (XL size) and a couple of those zero88 USB sticks .

Hi Edward (and ziglight), Thanks for your response, suggested workaround and other options - I'll have a play with an Effects Palette (not used those before) and the Speed Override. Also are you able to comment on my (2) regards colour fade time and (3) regards whether this is "stomping" and why I can't get the PB1 to keep control of the colour? Cheers, Kevin

Hi Jon/Edward, Any help/update/comments on this thread at all? I'm in Tech this weekend, so if you can comment if my usage is incorrect of if you think it's a bug that would help me out. Thanks, Kevin

Following on from having this effect chase, some other queries/observations: (1) So if I play my PB1 Effect chase over the top of my Master PB cue stack, I want the PB1 chase to take control of the intensity. From playback setup, I chose Intensity Mixing - LTP. This seems to do the job. Is this the correct way to achieve this? (At first I tried Allow Stomping from the Advanced tab, not knowing what "Stomping" is but it didn't do anything!). (2) When I raise the PB1 MFF, the colour fade time into the Effect chase can be altered in the cue view. However I find that when the MFF is released, the colour snaps back to that in the Master Playback - no fade there. What I'd actually like, is when the PB1 MFF is raised, the colour snaps to my Effect chase colours, but on release of PB1 the colour fades back to that in the current Master Playback cue. Is this possible? (3) If my PB1 Effects chase is running and I advance my Master PB, the colour of the chase moves to that in the incoming cue of the Master PB. So this makes sense for LTP of the colour. However if I want the PB1 Effect chase to retain control of the colour (and intensity) despite what the Master PB incoming cues have, can I configure the PB1 to do this? (Again, tried "Allow Stomping" but this didn't help!).

Hi, Sorry for yet another "basic" question on using the effects engine! I'm confused about how to update the speed of the chase, once I've programmed it to a Playback. This is my scenario: I have 4 identical RGBW LEDs, Fixtures 1-4. I select them one at a time and turn them on to @@ and set each one to a different colour using the colour palettes. I select 1 THRU 4. I go to Effects, chose Chaser, Random Offset, set the speed as (I think) I want. I Record this to Playback 1. I edit this playback to set the Colour fade time to 0. I clear the programmer, raise PB 1 and I get my Effects chase. All good. However I now decide the Effect speed is not what I want. Say it's too fast. PB1 is raised and the Effect is running. I select 1THRU 4. I go to Effect. I adjust the Speed and the output effect slows down. I now want to update my recorded PB1 with this new speed. I press Update. The chase stops running. I press the MFF key for PB1 to perform the update. I drop the MFF for PB1 to release the PB and then raise it again to retrigger. I have no chase effect. I have the static condition as output at the point I pressed Update. So what am I doing wrong? How do I update the speed in the recorded PB cue? This is not a "Chase" playback, so Global Tempo and Tap Tempo are not relevant (although I'd be interested if the Effect chase speed can be coupled to e.g. Tap Tempo). If prior to pressing Update I re-select the Chase effect and re-select Random offset then adjust the speed, I find the Update as required can be performed - but is it really necessary to re-select the Effect type and setup just to change the speed of an existing effect? I can re-record the PB from scratch (i.e. using Record rather than Update), but then I have the pain of having to set up the PB again and re-edit the colour fade time. Not something I want to be doing at the tech when the Director just wants a change in the speed of an Effect they are otherwise happy with. ...actually what I really wanted was some random flashing colours to use for a disco effect on these 4 LEDs... Thanks, Kevin ps Did have a dig through the Forum to see if I've asked this before but didn't find anything. Of course if I look again it will be staring at me...!

....and to end these advacan-advacan-advacan-advacanada videos... we'll do it all again next year... ! ...oh this is all just taking too long...!

Sorry Edward, I was being a bit flippant with the historical behaviour. Actually since installing 7.9.3 the other day I haven't done much "encoder bashing" so I'll have to give it a go and see what you chaps have been up to. Previously my observations were that the "acceleration curve" wasn't very good (i.e. there wasn't one) - at the slow end there would be jumps of 3/4/5 counts per "click" (particularly noticeable on effect speed which changes a lot with a count at the low end) and then when you wanted to get a shift on, you'd be frantically winding the thing round and round. Anyway we digress onto FLX, this is a Solution thread I've seemingly hijacked!

Oh we FLXers have our own encoder sensitivity issues - although at least they don't spin on their own! Strange that one, the (same?) wheels on my Fat Frog have always been quite stiff...! There seems to be a lot of variability in them as other users reported theirs as quite free-running as you have on your Solution.