kgallen

Jan 2016 CPC now do the SIBA HRC 10A fuses: FF02367 49p ea but MOQ=10.

Hi, Give this one a go. Load this and your own into the Fixture Editor to see what is different. Note: On FatFrog you won't get the channel details for ch12 on the displays. Regards, Kevin Yiscor_12LED_RGBW_Mover.ift

Hi Rejean, Can you attach your fixture file here so we can take a look? In what way doesn't it work? Kevin

Isn't that the point of 36 channel mode that you have individual control of all elements in the fixture? If you press the desk Colour button don't you cycle through the RGB for each element? Hopefully the fixture definition has an overall master dimmer. If you select the fixture and press Home, do all elements come on RGB? Kevin

Hi James, There is quite a bit of work in these, but you really ought to build the full feature fixture as a minimum. Generally the other modes are then a stripped down version. Good luck, Kevin

GROUP 1 AND 2 ENTER = Group 1 and fixture 2. GROUP 1 AND GROUP 2 ENTER = Group 1 AND Group2. This syntax extends ad-nauseum: GROUP 1 AND 3 EXCEPT 5 THRU 7 ENTER = Group 1 fixtures plus fixture 3 but not fixtures 5, 6 or 7 (which would only be relevant if they were in Group 1!) etc etc

Hi Jon. False alarm. Seems I have to press the middle button of the encoder wheel ("Scroll") to get the colour palettes for the scroller. Must have done this before but don't recall it! I have LEDs and scroller a patched. The palettes for the LEDs are always shown by default even if I only select the scroller. I.e. To get the scroller palettes I have to press the encoder button even if the scroller is the only thing selected. Anyway, works the same on 7.8.4 and 7.8.5, so thanks for the code image to check. Previous comment on possible display bug still apply. Kevin

I know this was covered in a topic, but blowed if I can find it. [ETA: See the bottom of this post: http://zero88.com/forum/topic/7172-more-questions-issues/#entry28049] 1 AND 2 AND 3 ENTER is fine, ch 1,2,3 are selected. 1 AND GROUP 1 ENTER starts to edit the cue number field. Grrr. GROUP 1 AND 1 ENTER is fine. GROUP 1 AND GROUP 2 ENTER starts to edit to cue number field. Grrr. (1) Please sort out a better way of triggering cue number edit, as it getting mixed up with syntax termination is naff and really annoying! But I sympathise as there doesn't seem to be an easy answer with ENTER being used to trigger field edit... (2) How to select multiple groups with syntax (with touch screen is ok). We know selection order is significant for effects... Thanks.

I tried re patching the fixture but it didn't help. I don't have a 7.8.4 image I can revert too to try back on that version (desk came with 7.8.4 on it). I realise you want customers to always move forward with software releases, but keeping at least the previous version available on the software download page would be useful for situations like these or when the new version actually has bugs that can't be tolerated for an upcoming show. Thanks. Further: I created some user colour palettes for the scroller (I was paying attention on the new videos . I select the fixture and dial up 'Red' on the encoder, RECORD COLOUR hit 33. However the output window shows C33: Colour 33:Clear even though the encoder label says Scroll (C33) Red. The output window says the colour is 'Clear' regardless of what colour is programmed. The encoder label is consistent with the scroller gel and the user palette does move the scroller to the correct gel frame.

Playing with 7.8.5. Thought it better to start a new topic now. The other day I reported this in one of my other threads: http://zero88.com/forum/topic/7331-confused-by-playback-overlaying/?p=28801 Separately, another Next issue: Playback 0 is on cue 6, Current:6 Next:7. Programming some other playbacks now, I'm seeing that the Next yellow bar on Playback 0 is jumping back to cue 1 after hitting one of the MFFs after RECORD (used syntax to set some levels, hit RECORD, hit eg MFF11). Also in the status row, Next:1. Also as an aside, I now press down arrow and the yellow bar jumps to cue 8 and Next:8. The Next cue really had changed, because if I GO on Playback 0 then the stack goes to cue 1 not cue 7 as it should have. This behaviour wouldn't appear to be intentional, and is a potential pain when building a cue stack if it is!

Oops sorry my mistake - doing it in a rush in my lunch! Thanks Jon. Kev

OK, you're excused ;-) Have fun!

Give this a go. This one was pretty straightforward, you should have a go yourself. Download the Fixture Editor: http://zero88.com/support/index.php?/de/Knowledgebase/Article/View/49/0/zero-88-fixture-tools---version-26 [Jon - the Fixture Editor software is ridiculously hard to find on the website - can you link it from other software and fixture pages?] (Thanks, JB, it was short and sweet this one, so didn't take long - but have a go too, it's good practice!) Kevin Chauvet_BeamShot.ift

Hitwave, can you post a link to the manual. I'll have a look, but probably won't be today...

On 7.8.5 my colour scrollers no longer respond to any 'auto' palette. With 7.8.4, I could hit a red auto colour palette and my LEDs and CQ1D scrollers would go red. With 7.8.5 only the LEDs are going red, the scroller stays at eg Scroll=Yellow. Same setup as posted in another topic, just reloaded the showfile after updating the desk from 7.8.4 to 7.8.5 tonight. The showfile brought in my own fixture definitions for eg lamp+CQ1D as I had for 7.8.4. My scroller fixture profile includes colour detail (names and RGB). Ideas? Me? This is the showfile from the other topic: http://zero88.com/forum/index.php?app=core&module=attach&section=attach&attach_id=662

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