Paul

Are you using an external monitor display? Most if not all of the menus are displayed in full on the monitor, making it easier to see what's there. Would be worth you upgrading from 9.6, a number of bugs relating to the stability of memory data when assigning and unassigning fixtures have been fixed since then. Download here. Instructions here.

Go into Super User, and look under 'Desk Information'.

Hi eldar, Glad things are getting sorted for you. What software version is the desk running? The '???' thing is odd - that's what the desk puts up on the wheel LCD when it's confused about something. If you're running the latest software (10.4) and you can make it do that again, please let me know how so I can look into it. Cheers, Paul.

No, it is not possible.

Someone once suggested that WHEELGROUP+HOME should home the selected fixtures without tagging them. This fits in fairly consistently with other uses of the WHEELGROUP button in software 10.X. The 2 questions which arise from this are: 1. Should this UN-tag any tagged parameters for the selected fixtures? 2. Should Brightness be homed to 0% or 100% in this case? Check out the posts on Frog Reference 5500 for similar discussions previously.

It's designed that way Pressing Home affects all parameters of the selected fixtures, hence they get auto-tagged by the desk.

This is what I'd expect. However now you have programmed the empty beamshape palettes and renamed the position palettes, then the position palettes will no longer lose their names.

Hi Rob, The answer to both of your questions is yes. To daisy-chain the packs, simply link them with standard analogue cables (there are 2 sockets per pack). The switch on the bottom of each alphapack will set whether it uses channels 1-3 or 4-6 from it's input. To get separate control of the third pack (if you don't want it sharing the same 3 channels as the one of the first two packs), simply run another analogue cable out from the desk. If you need to buy replacement fuseholders, just give us a ring! Regards, Paul.

Hi Morn, Were your position palettes named: 14 Random Lines 15 Laser Cannon 16 Rot. Triangle 21 Double Beam Anim ...by any chance? Thanks for the showfile, I was able to track down the problem using it. This is a bug which will be fixed in the next release. Frog Reference 5545 - Position palette names are not loaded if the same numbered Colour palette is programmed and the same numbered Beamshape palette is not programmed. As a workaround, if you program the same numbered beamshape palette (with any data), then the position palette names will then load correctly. Paul

Yes, you can do this. The software is the same for all desks in the Frog series.

Frog Series Software - Version 10.4 We have released Version 10.4 of the Frog Series Software. The new operating software, offline editor (Phantom Frog) and release notes can be downloaded from the Zero 88 Support Centre: CLICK HERE

Colour coding is already used on the normal outputs screen to indicate values that are increasing/decreasing. For consistency we should not adopt colour coding on the fixture outputs screen which has a different meaning.

F1 is for locking the monitor screen F2 is for naming things F3 is for individual live chase speed adjustment F4 is the Group button on a Fat Frog

There are 4 places that the fixture outputs can be seen: 1. Outputs screen on LCD. 2. Outputs screen on monitor. 3. Fixture outputs screen on monitor. 4. Wheel LCD. In all 4, holding down the WheelGroup button will show the current tag states. Using +/- in the fixture outputs screen isn't going to work, since the +/- keys are used for normal menu navigation on the LCD while the fixture outputs screen is displayed. I agree it would be useful to 'lock' these 4 outputs views on displaying tags mode (when programming for example), but there are times you'd probably also want to see the actual outputs (when running the show), not the tag states. I think a SuperUser option would probably not be the right thing here, since you'd want to switch between the two view modes faster than that. I think the best way would be if you held F1 and pressed WheelGroup. This would lock the 4 outputs views on the displaying tags mode. Press F1 and WheelGroup again to unlock. The LED in the wheelgroup button (currently unused) would be used to indicate the lock status. Frog Reference 5544 - Ability to lock fixture outputs views displaying tags.

Frog Reference 5543 - Colour-coding options for various monitor screens.

Frog Reference 5543 - Colour-coding options for various monitor screens.

Frog Reference 5543 - Colour-coding options for various monitor screens.

Can you post the show file on the forum (use the 'add attachment' function), and let us know which position palettes have their names in 10.2 but not in 10.3, then we can look at it. Thanks.

Can you post the show file on the forum (use the 'add attachment' function) and let us know which submaster isn't working, then we can look at it. Thanks.

The Fat Frog can do 16-bit no problem. You need to make sure that the mode that you have set the fixture in matches the fixture personality that you have selected on the desk. In most cases, changing a fixture from 8 bit to 16 bit control affects it's DMX channel allocation, hence the need to ensure that the settings at both ends of the DMX match.

Hi Chris, Yes. If an LTP parameter is not programmed (tagged) in a cue, then it will not change from it's current output value when you play that cue. I'll try and keep the description brief here and skip over some of the finer points, just so you can get started with it. Once you've understood the basic concept, hopefully the detailed description in the manual will start to make sense. I should point out that the way partial programming works has changed significantly between release 9.8 and release 10.0 software. If your desk is running release 9.8 (or previous), it's probably best to leave it at that until you've grasped the concepts of partial programming, before you move on to release 10.0. When you're programming in partial mode... - The desk will automatically 'tag' any parameters you change with the wheels. - If any parameters of a fixture are tagged, then the yellow LED in the fixture selection button will flash. - When you hit Program, only tagged parameters are recorded. Hence when you play back the thing you've recorded, only the parameters that you tagged will change. - You can toggle the tagged state of fixtures by holding down the fixture selection button for a couple of seconds until the yellow LED starts/stops flashing. - When you hit Program, the desk will (just after it's recorded your data) automatically clear the tag states so that you're starting with a clean sheet ready for the next thing you're recording. That's about all you need to get going, let us know if you have any further questions. Paul.

Put the desk in Partial Programming Mode (SuperUser->DeskSetup->ProgramMode). Then only LTP parameters that you 'tag' (yellow fixture LEDs flashing) will be recorded in each cue. HTP (brightness) parameters are ALWAYS recorded.

Hi ice, Thanks for doing the translation. Unfortunately this question is completely devoid of any information which might help us investigate. For instance: - the software version on the desk? - the serial number of the desk (by PM please)? - which "reaction time" gets slow? which screen? which button? - how many memories/submasters are programmed? - how many chases/movement effects are running? - how many (and what type of) fixtures are assigned? A copy of the showfile would help answer a lot of these questions. There are no memory upgrade options for any of the Frog series desks. Regards, Paul.

The exact mechanism by which the upgrade mechanism works is more complex than it would be appropriate to explain here. In short, if the upgrade fails, there is something wrong with the file on the upgrade disk. You don't need to understand the desks mechanisms, just try another disk, try formatting the disk in the desk first, try copying the osf file first etc etc as explained above.

The operating system loader checks the integrity of the operating system before running it. If the check fails, you get the System Terminated message.