kgallen

I think I'd try again in a new set of PBs as the programming on PB21-23 looks really confusing. If you are wanting to use your 3 PBs to mix R and G and B freely then you'll need to be in one of the Teacking modes and make sure only the required colour parameter is touched before hitting Record. Kevin

This page http://www.zero88.com/software/index.shtml and http://www.zero88.com/software/zeros/ seem to list 7.9 for FLX only so looks like you're correct on x86/OrbXF. I didn't actually realise for a while that 7.9 was out - and only then because the last beta 7.8.5.33 (or whatever it was) got locked from access, although 7.8.5.33 was for OrbXF in addition to FLX! Kevin

(I'm sure Jon will have a better explanation soon, and sorry if I'm about to point out the obvious and you're and experienced user!) All of the LEDs seem to be recorded with Blue=100 in all programmed P/Bs 21-23 and you're in Non-Tracking mode so all attributes will always be recorded - so activating any P/B will set all LEDs to blue regardless of what they were before. I don't see any programming in P/B1 or P/B2. If with ch101 thru 115 selected, I choose a green palette then the Intensities/Live window says C6:Green for the R/G/B. Activating a playback doesn't change them to Blue=100. Source/Live shows the source as P i.e programmer. So it seem the programmer takes priority over the activated playback. If I release the programmer overrides with Shift+Clear (clear the programmer but leave the selection intact), then the LEDs revert to Blue=100 even without touching the P/Bs. This is probably all as intended, will leave for Jon to confirm or otherwise! OK so I'm poking around a bit more now and I'm now confused! If I set Source/Live for the Output Window and press the PB21-23 buttons I do get other selections up on the Output WIndow. If I press PB21, the internal screen gets the red bar top right. Clear+PB21 clears the colour. Likewise, Green on PB22 and Blue on PB23 and Clear+PB can clear the colour. But this doesn't really seem to correspond with the Output Window. With PB21, R,B columns are blank and Green colums says "D" (I need to look up what this is, maybe default?). With PB22, R,G=C 22/1 and Blue is "D". With PB23, Green=C 23/1 and R,B columns are blank. So now I'm as confused as you as in Non Tracking I would have thought all colour attributes would be recorded always! Over to Jon...! I was using PhantomOS(FLX)7.9 so didn't have any real lights connected! I was just looking at the Intensities/Live window with ch 101 thru 115 selected so I could see the LTP attribute information.

"As Kevin says you can use a forward slash (which is easy IF you have an external keyboard, or use a showfile loaded from Phantom FLX). I've added an issue to make this easier - ZOS-7310 - thanks for pointing it out :-)" Hi Jon I think I asked a while back if THRU could be used for this, because as you say otherwise it needs an external keyboard. So you might already have this logged.

Default times can be split, in Setup you can type 3/5. I found this by accident myself just playing around!

Ok, can't offer to fix it for you as you're not local to me. If your Tech department can't fix this then get a better Tech department because if the resistors are the fault then it's a straightforward fix! Kevin

If you can solder, swapping the resistors is pretty straightforward. You have to remove all of the screws holding the PCB into the chassis to get to the solder side. I've done 4 Betapacks (1's and 2's) and I don't recall them being hard - the Betapack 1s I think were a bit easier as there is more room. Just make sure you get the correct VR rated components as per my link. Don't just buy any old 100k 1W resistors as they are across mains voltage. If you've got an ohmmeter, you can get an idea if there is a problem with the resistors - there are 4 in there so you can compare readings - but don't expect to measure 100k when they are in-circuit. Replace all of the 100k resistors not just the ones you think have failed. It'll cost you a couple of pounds to buy the correct resistors. Kevin ps Where are you in the UK?

Did both channels fail at the same time before you replaced the triacs? If so, maybe a sync circuit problem rather than triacs? I'd take a look at the infamous 100k sync circuit resistors. http://www.blue-room.org.uk/wiki/Betapack_Servicing http://zero88.com/forum/topic/3709-betapack-1/#entry27190 Kevin

There's no reason why you can't use this new light, but you will need to build a new fixture profile for it. Do you know how to do that with the Fixture Tools? http://zero88.com/forum/topic/6230-fixture-tools/ You could load the file for the light you currently have into the Editor and use it as a basis for the new one. Give it a go, it's quite straightforward. You can always come back on this thread and ask for more help. Posting a link to the manual would also be handy, and indicating if there is a specific mode you need. Good luck. Kevin

What I suggested above seems to work on the desk.

Sorry can't help with the load problem. Regards the monitor there is no mechanism to load drivers yourself, they have to be supported by the underlying OS in the software. The compatibility list is not exhaustive it's just the list of monitors that the software developers have tested. If you get it to work, great. If not you could ask Zero88 if it's common enough for them to get working or you need to switch to a supported screen. Good luck!

Good question! I can't try this at the moment, but looking at the release notes, maybe try: - go into Blind mode with Shift Z - ensure the fader select is on Playbacks - select the appropriate playbacks page - hold the required playback button (one of the 24 under the playback masters) - type the cue number See if this loads the required playback cue into the blind page. Let us know!

If you set each group to e.g. red then record the colour palette then this should give you a shortcut to getting an "all red" fixture. I realise this is not ideal as this does not allow you to "dial up" the colour on the fly, but if you know the colours you'll need when programming then this should give you a quicker approach than having to deal with each group separately. I think is Jon is away at ABTT so unless Keith is about then you might have to wait a couple of days in the hopes of a better solution ( ).

Would a colour palette be adequate?

The only other difference I saw was that the constituent fixtures were defined the other way round. In mine the dimmer was parameter 2, in yours 1. I don't see how this should make any difference though! Are you saying the desk is remembering the fixture now? Good news anyway, we got there in the end! Kevin

OK, partial good news! I really don't understand the desk not remembering the fixture, that makes no sense at all. I'm not aware there is anything in the fixture definition that would cause it to be lost! I'll have a think, but that part has me stumped! Your fixture definition looks good to me. Do you mean the "Fixed" tick box in the Details tab? I've no idea what that does - it's not ticked in my fixture profile and it's not explained in the Fixture Tools manual! Kevin

Just had a look at your fixture. It's very similar to mine, but with one important difference: in the Scroll Parameter Detail tab, whilst you've listed all of the DMX ranges and given them names, you haven't defined the RGB for each range. For example on "Clear 130" you need to tick the "Colour Defined" box and set R=G=B=255 (then press "Replace"). Similar for Red 106, tick the Colour Defined box and set R=255, G=0, B=0 then press "Replace". Do this for the rest of the colours. Then you should get those colours in the palette under the encoder button. Regards, Kevin

Really? I just downloaded the file from the Forum onto my work laptop and it opened up in Fixture Editor fine. I'll take a look at yours... Regards, Kevin

Here's mine for Lamp+ChromaQ CQ1D if you want to give it a try or to compare to your profile. Under "Scrollers" is Dimmer+CQ1D Scroller Lamp_CQ1D.ift

Hmmm that's really weird. Even if the fixture is not on the desk before you reload the show, it should come back in with the showfile. Can you still see the fixture profile available if you go into Setup->Patch Wizard? When you load the showfile can you see the fixture is patched and still has a DMX address (Setup->Edit Fixtures ->Patch)? Back to basics, if you do: <Clear><Clear><type channel number of scroller><Enter><Colour> does the middle button of encoder 1 not bring up your list of defined gel colours?

It shouldn't lose that information. I've built the same sort of fixture too for the same reasons. What software version is on the FLX? 7.8.5? In Setup -> System Settings, there is a Recovery Mode setting - what is that set to? (Not that it should make any difference!) When you say "Recording on USB" do you mean you saved a show to USB and that wouldn't restore the function either? That sounds very weird...

Certainly electrolytic capacitors can "dry out" although I'm not sure I'd go about changing them unless you see a problem, they look aged or you know they've had a an over-voltage event. I don't see any value in swapping out the voltage regulators unless you think they are damaged. At 20 years of age maybe I'd be more concerned that the data retention of any non-volatile digital storage devices (EPROMs and the like) is well down the statistical tail of the expected retention life. Such devices of that era often had guaranteed retention of 10 years, and 20 year retentions were more unusual (generally military grade components). I have these 'worries' with my own Demux48 of a similar age! Other ICs of that era are built from a relatively large geometry silicon process, and failure modes due to electromigration were not the reliability concerns we now have with the ultra-deep sub-micron processes we use on today's digital devices. Maybe for now, "If it ain't broke, don't fix it!" (NiCd batteries excepted, but you've replaced that one). Kevin ETA: If you do change the electrolytics, I'd recommend ensuring a good margin on their voltage rating. If you can physically fit the replacement to the PCB, choosing one at double the voltage rating is always good for reliability, and a minimum rating of 16V is always a good rule-of-thumb even on 5V supplies.

Unfortunately memories can't reference subs as you wish (unlike palettes which can be referenced and subs that can reference memories, but not the other way round which is what you require). You can of course re-program a memory with a new look made up of your revised subs, but it's exactly that, a reprogram of a memory rather than a reference. Regards, Kevin ps What you want would actually be very complex to implement because you could record a memory from an arbitrary set of subs (possibly containing fixtures), plus faders plus additional fixtures and all that implies the possibility of a very complex tag state particularly if you were in tracking mode, tracking intensity channels as well as colour/beamshape/position parameters. Sorry it's beyond what the console is capable of! Manual (covers software to 9.0): http://zero88.com/support/index.php?/de/Knowledgebase/Article/View/51/58/frog-range-operating-manual-issue-6-en Release Notes (to software 10.12, for many extra features beyond what's in the above manual): http://zero88.com/support/index.php?/Knowledgebase/Article/GetAttachment/56/554

Hi Jon, When you get a moment could you explain how the AutoPalettes (Colour) are assembled from the data provided in the fixture profile? I've been looking at my fixture profiles (all built myself) and trying to see how the colour parameters and any "Details" translate into what is available in the Auto Colour Palettes. I can see correlation in the names, but I can see the Auto Palettes aren't the union of all e.g. Color1 parameters defined in the profile. Some colours are in the palette twice (e.g. "White" and "[W]") even though they have the same "Colour Defined" RGB in the fixture profile (R=G=B=255) whereas some are not in the Auto Palettes at all. I found an Amber (R=255,G=144,B=0) that was in the fixture profile detail but not in the palette. The closest other was an "Orange" R=255,G=128,B=0. I'm sure that of course you have to rationalise the palettes to avoid duplicates of near-identical RGB specs, but as I say above there were some apparent duplicates and some apparent omissions. This is just for "interest" to some extent, but it would be good to know how to structure the "Detail" section of a fixture profile to get that entry available under a palette button! Thanks, Kevin

??? Setup -> Load File Sorry - seems a strange question, is that not what you meant?