kgallen

[ that's the best I can do, this Forum doesn't have rolling-around-on-the-floor-laughing smiley]

What? That's what he looked like when I was in Cwmbran last October!

I would hope not, that wouldn't be useful! It would need to be on a per-fixture instance basis. Maybe the OP could clarify exactly what is happening and what the settings are. This function has been available on many Zero88 consoles so I'd expect Jon or Keith to spot an issue like this pretty early on.

I think there is some middle ground here. This is such a complex product it just must have a manual for users to have the vaguest chance of using it, however intuitive the developers might think it is. As we're discussing, a paper based manual is probably impractical due to the rate and extent of changes to the platform, and as users we like these enhancements. Documentation that is up to date is always a challenge, particularly for a small company. Maybe Jon would consider a 'softer' form of manual, maybe published and maintained online rather than on paper. Maybe such a format would be easier to maintain and keep up to date with software changes, but at the end of the day is going to take some effort and commitment to get together. The console has been out for well over 18 months now. An official complete manual in whatever form is really a reasonable expectation by now before we really do scare off new customers for an excellent product, and that will be bad for all of us. Just my 2p worth...

Hi Emrys, Just use Load File as if you were reloading a show. Kevin

A quick answer before Jon gives us a better more complete explanation (which will certainly be useful for me too): Smart Tag is the desk working out what fixture parameters have changed since the last cue/current state in order to only record the changes. Advanced Tracking requires the user to control the fixture parameter "tag state" manually thus having total control over what is and what is not recorded in the cue. ...that's how I understand it anyway! Kevin

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