K-Nine

The problem here is insufficient horizontal flyback time, so on some monitors, the edges of the picture are not displayed correctly. Illusion Reference 4692 - Display problems with some LCD monitors.

Great News ! Glad to hear it's working well for you. If you have any trouble.... you know where we are :-)

Just had another thought .... :idea: The brightness (dimmer) parameters for fixtures are controlled by faders ... VIRTUAL faders. Assuming that you are not playing around with fixture parameters during the running of your show .... why not select the fixture(s) you wish to control, select the Brightness button ... the first finger wheel then controls the Brightness parameters of the selected fixture(s) ... HTP mixed with the outputs from the memory stack (playback X) and submasters .. Voila 8)

I can't see how having the brightness for these fixtures on one submaster would constitute 'wasting subs' or have I missed something here :?:

If you wish to program a memory down to attribute level: Ensure that the Program Mode is set to Partial in Desk Setup. Check that only the fixtures to be recorded are tagged (yellow LED in fixture selection button is flashing) To record a single attribute (eg Position), press and hold down the attribute button and then press the Program button. Note - Generic and fixture brightness channels are always recorded regardless of which fixtures are tagged and which attribute buttons are held prior to pressing program. If you don't wish the brightness levels to be recorded, ensure that that they are at zero when you press Program. See Mambo Frog Operating Manual (Issue 2) pages 3-4, 3-8 for details.

My suggestion would be as follows: Ensure that the desk is in partial programming mode (Desk Setup) Set the brightness of the required fixture(s) to full; ensure all other generic channels and fixture brightnesses are at zero and all fixtures are untagged. Program the channel data directly onto a submaster.

The current release of software for the Illusion 120 & 240. This release includes minor bug fixes and code optimisation. The software can be downloaded from the main Zero 88 website : CLICK HERE.

When you set up a fixture with a movement effect and then save it into a scene memory, chase step or directly as channel data onto a submaster or SX button, the movement effect parameters (Effect, Size X, Size Y, Offset, Rotation, Speed) are saved with the fixture data. If they weren't, then when you output the memory, raised the submaster or pressed the SX button, there would be no movement effect on the outputs ! It's not the case that they are not stored, it's a case of they are not displayed when you preview the memory or submaster. If I remember correctly, if you wish to adjust a movement effect on a memory or submaster you need to EDIT the item, select the required fixture(s) and then select POSITION. The movement effect parameters should then be at their correct values on the LCD. The following issues relating to movement effects have been noted : Frog Reference 5405 - When you preview a memory or submaster with a movement effect, the movement effect parameters are not shown on the screen. Frog Reference 5403 - If you set up a fixture with a movement effect and then save it into a position palette, the instantaneous values of the pan and tilt parameters are taken when the palette is programmed, resulting in a static position without the movement effect. Frog Reference 5505 - When a movement effect is running on a fixture this is not reflected in the movement effect parameters on the wheel LCD - they show No effect , size = 0 etc. We are planning to address these issues in future software updates.

The Fixture data we use on the Frog series of desks was 'inherited' from that used on the Sirius 250/500 desks. On these desks the parameter details (lists of colours, gobos etc.) were displayed on the monitor screen. When we developed the Frog desks all of this data was 'translated' into a form which could be used by the Frogs. The tool which I use to generate our fixture library is similar to the Fixture Type Editor but has a few additional functions which allows me to generate fixture data in the old Sirius 250/500 format, define wheel groups for four wheels etc. We decided to leave the parameter details section in, even though it is not currently used by the Frogs. As the person responsible for maintaining out fixture library I have spent many happy ( :!: ) hours typing in parameter details for the Sirius 250/500. Lighting desks with moving light capability which we develop in the future will almost certainly use the same fixture data, and the parameter details may make a comeback :wink:

Were these 'scenes' programmed directly onto the submasters as channel data, or were they programmed as scene memories and then transferred onto the submasters ? This is important since channel data on submasters can only be output manually (at the moment). If raising another submaster causes the fixtures to go out it sounds as though there was some fixture data programmed onto that submaster. Did you check that all fixtures were untagged before pressing Program ? Programming in partial mode should only record those fixtures that are tagged when you press the program button. Additionally, you can choose to record a particular attribute if required.(eg colour only or position only) Note - As generic channels and fixture brightness channels are HTP they are always recorded into the memory or submaster data regardless of which fixtures may be tagged when you hit program. See Frog Series Manual (Issue 5) Page 5-3 for further details. At present, if you want a timed fade on a submaster you have to program a scene memory with the generic and fixture data you want; set the fade up and down times as required, and then transfer the memory with time onto the submaster. I realise this may seem a little clunky and it is one area we are looking to improve in the next feature updates package later this year. This sounds like the fixture brightness may also be coming from the current memory on the playback X - and since fixture brightness channels are mixed HTP, then the fixture will still be 'on'. Try setting an LTP fade time and position action to fade in the scene memory and ensure you transfer the memory with time onto the submaster - when the submaster is raised when it reaches the LTP trigger level, the position parameters should be triggered and fade to their new values.

Hi, I have just tested this out on a desk here and it would appear that as long as your filename is 15 characters or less (19 characters including the .cft extension) then the fixtures types in the file should load correctly. Frog Reference 5496 - The desk software does not recognise long filenames when assigning fixture type from floppy disk or loading CFT - to be fixed in future release.

No worries, that's what this forum is for What was the problem in the end ? You are not alone in your 'rookieness' and you may be able to help someone out if you let them know your mistakes (and solutions).

Details of new/modified functionality, bug fixes etc. are documented initially in the release notes which accompany a new software release - see the downloads - software section on the Zero 88 website. All new/modified functionality also gets included in new issues of the manuals, but sometimes there is a delay between the software release and the new issue of the manual being produced. I believe that the latest Frog Series Manual on out website is Issue 4 which should include all the functionality included up to software release 7.5.

Would you want to label desk channels, DMX channels or both ? In my mind, you would be labelling desk channels at that point. (this is the way the console currently works) Would a DMX channel label be useful too ? If so, I'd assume that it would go in the patch screen.

I may have misunderstood the problem, but.... If you recorded palettes with the 10 fixtures, then those palettes would not have contained any data for the two new fixtures you added afterwards. You would have needed to go back and edit the palettes to include the new fixtures. The same applies to the memories... if the lights were not assigned when you recorded them, then the desk wouldn't know that they were there. If this is the case, then the desk is working the way it is supposed to.

There is not currently a feature as you describe, although the 'Go' button crossfade can be manually overridden, allowing you to speed up and slow down the crossfade. As to whether it is a feature that will be in a future update, I can't say either way... We will include it in the suggestions database, and it will be reviewed.

Your desk is still in the 3 year warranty period. In the first instance, you should contact the Zero 88 dealer you bought the unit from, they will be able to sort out the warranty return for you. If you send it to the factory, send it for the attention of the service department. You will need to fill out a warranty fault report form in order that it gets sorted out properly.

That's what I've been telling people all year :roll: It's amazing what you can find in the manual

Just an additional note.. Make sure you backup any showdata in your desk first. The show data is lost when you upgrade the software. When upgrading, the desk will prompt you if you want to continue. These prompts are on the LCD, not on the monitor. (So don't sit there for 10 minutes looking at the monitor !)

There are a few different ways you can set the scrollers up on the FatFrog, but whichever way you choose they will all work in a similar fashion. You can select and program colour states in isolation, or as a part of a lighting state. The colours can be saved as submasters, in memories or as colour palettes, allowing you to use them as colour presets for fast programming. It should be fairly straightforward.

I was going to suggest that but you beat me to it

As far as I remember, when creating a new fixture type it is only possible to define one set of 'real' pan and tilt parameters. Although I think it is possible to add other 'pan' and 'tilt' parameters in the Position group, it is NOT possible to classify them as 'pan' and 'tilt' (The special field in the parameter window). The movement effects engine is only designed to work on the parameters which are defined as 'pan' and 'tilt'.

Fair enough, I was just pointing out that the SX buttons sounded fairly close to what you were asking for. The SX buttons on the Mambo Frog work in a similar manner to Submaster flash buttons anyway. Is there any need to make matters more complex ? Since you can transfer any of the scene memories in the memory stack onto submasters anyway why do we need a separate mode ? Just make sure that the submaster page is on the correct page for the set of memories you want ? You may need to press the Page button, but this is no more effort that pressing a function or other button, and the added functionality that would be needed on the submaster screen etc.. The tricky bit, is as Paul explained in his post, making the desk perform the "everything proceeds as it was befor pressing it" due to the nature of how LTP processing works. Generally speaking when you output a memory, submaster, SX button or palette or you adjust LTP parameters with the control wheels, you tell specified LTP channels to go to a particular value. You don't necessarily remember the whole list of events which may have generated the previous state of those LTP values, especially as they could have come from a variety of sources in any order. Live adjustment of chase speed on both the playback X and submasters have been entered into the request database and will be reviewed along with all the other feature requests - see other topics for relevant Frog Reference Nos. Not something that's ever likely to happen, sorry.

It will get logged for review anyway... I was just asking if there was a reason 8) I can see the logic if, as you say you want all the DSL scrollers in one fixture... it makes the rig patching a bit more involved otherwise. We'll see what happens.

Not wanting to seem flippant here, but if you have the limitation on the desk, is there any reason you are not designing / patching your rig to make the scrollers appear on adjacent DMX channels ?