K-Nine

I assume that you have configured the required remote switches to be GO or Go to memory number in Desk Setup ?

If you unassign fixtures and then assign the same fixture buttons to a new fixture type, you are effectively deleting the old fixture types from the show data on the desk. Consequently all the data stored for those fixture types in memories, submasters and palettes is deleted from the show file. The newer Leap Frog 48/96 and Frog2 desks have functions that allow you to swap fixture types and the desk will try and copy as much data as possible from the old fixture to the new fixture.

The Drive modifer, as with all of the chase modifiers (Direction, Attack, Speed etc.) applies to the whole of the chase memory.

It is not possible to adjust any of the parameters relating to the sound to light processing in the desk. There is some description of the circuitry above. From what I remember the difference between the two Drive modifiers is as follows: Bass ... the next step of the chase is triggered by the Bass beat of the incoming audio signal. No audio signal ... chase stops. Vari .. the chase runs at the programmed speed with additional step triggers provided by the Bass beat of the incoming audio signal ... no audio input ... chase runs at the programmed speed.

If you record a number of different UDFs with different channels at 100% and a fade time of zero, then you can mix the required state by having each of the UDF faders at the appropriate level. Press ACTIVE ENTER to grab the outputting channels into the programmer at their current levels and then record to a new UDF or wherever required ... this method appears to be working fine on my desk here. Check you're running the latest software version (4.3)

There should be no difference operationally or functionally between the Fat Frog and Bull Frog desks ... they run the same software. The bass beat of the audio input signal is used when the Drive modifer of a chase memory is set to Bass or Vari.

On the Frog 2, a chase is programmed by recording all the various steps of the chase into a cue stack as individual cues and then converting the whole cue stack to a chase and adjusting the modifiers as required.

Load the UDF into the programmer, select the Fade view of the program window and change the fade times of the required fixture parameters to zero ... or remember to set the fade times when you record the UDF initially, otherwise they will pick up the default fade times as defined in Desk Setup ACTIVE ENTER ... All channels owned by the playbacks, UDF and UDK will be pulled into the Program Window. (See Operating Manual page 99 for details of all the commands using the ACTIVE key).

What sort of other 'details' are you trying to save ? If you mean the breakdown of a fixture parameter into a number of DMX values ranges, then these details are not used on desks in the original Frog series. The parameter details however, are used and displayed on the new Leap Frog 48/96 and Frog 2 desks. If a fixture parameter (eg Pan, Tilt) takes up two DMX channels then you need to specify the parameter as 16 bit rather than the default 8 bit and assign the MSB channel and LSB channel to the coarse and fine channels respectively.

So it was just a DMX addressing problem rather than one with controlling the fog machine from the desk ?

This has been logged in our database - to be fixed in the next version of software - Ref. F2-2075.

Leap Frog 48/96 Operating Manual - Issue 3 The updated operating manual describing all the new and modified functions implemented in Version 3.0 software is now available from the Downloads section of the website: CLICK HERE.

Frog 2 Operating Manual - Issue 4.3 The Frog 2 Operating Manual - Issue 4.3 is now available: CLICK HERE The updated manual contains all the new and modified functionality that was implemented in Version 4.3 software.

This has been logged in our database and will be fixed in the next version of software (Ref: LF-2063).

Just a thought ... check what the Preset Mix Mode is set to in Setup - Desk Setup - Behaviour. There are two options: HTP - Highest Takes Precedence LTP Mix - You need to use the preset fader to match the current output level of the dimmer channel. Once the level has been 'picked up' you can adjust the output level up or down using the fader.

Any 'fixtures' which have more than a single brightness/intensity channel (generics/conventionals/parcans etc..) are usually assigned to the fixture buttons (MFKs) on the desk. The desk has 10 pages of 20 buttons so you can assign and patch up to 200 fixtures.

For further information on groups and macros, see the following sectrions of the Operating Manual ... Groups: Pages 129 - 131 Macros: 143 - 146

Sounds like a good idea. The problem at the moment is that the command line MFKs (Special Page 2) are all assigned. However, if one can be identified that is not required in command line mode it could be replaced by a REM DIM key perhaps

Could you not simply program the chase memory after the scene memory and have it trigger automatically ? In the next version of software, there will be the ability to run a macro when a cue (memory) is triggered. If you programmed the macro to be the corresponding submaster flash button (and set the flash button action to latch) then the submaster containing the chase will be triggered when the cue is run Alternatively, you could simply push the submaster fader up at the appropriate time, or is that perhaps expecting too much of the operator ?

Note - There are two different versions of the fixture library; the full one and the filtered one that has the parameters details removed in order to fit it onto a single floppy disk. Make sure that you download the filtered one listed on the fat frog page (CLICK HERE) rather than the Leap Frog 48/96 or Frog 2 page on the website. If the fixture you require is not in the library, you can create your own type using the fixture editor which can be downloaded from our website. If the fixture profile is similar to one by the same manufacturer you can import that type and edit it or you can create a new fixture type from scratch.

Go into Setup - Patch and select the [Edit Fixtures] option. Select the [Patch] option. Select the fixtures (control channels/preset faders) that you wish to patch in sequential order using the flash buttons below the corresponding preset faders. The selected channels are displayed in the patch table on the monitor. Move the cursor to the ALL row and the DMX column. Press ENTER, then enter the DMX address of the first control channel. Each of the selected channels will then be patched sequentially from the start address. To patch a control channel to more than one different DMX address move the cursor to the required channel and across to the Duplicate 1 column. Press ENTER. Select the required universe and DMX address in the popup window displayed. See Operating Manual Issue 2 Pages 43-48 for full details of these functions.

Personally, I would create a fixture type that matched the DMX profile given for the fixture. That way the other three parameters are there should you require them at some point in the future. If you don't need them at the present then they are simply left at their default values. Because of the way dimmer (intensity, brightness) channels are processed differently on the desk to colour, beamshape and position channels, only one dimmer channel can be defined per fixture. With the LED parcan I would assign the red, green and blue parameters to the COLOUR attribute. This means that these parameters will be processed LTP rather than HTP but you will have individual control of each parameter via the control wheels.

Have you tried the Lee or Rosco websites to see if they provide any conversion or look up tables ? Alternatively, try the Blue Room. I am sure I have heard a similar question asked there.

You should be able to use the fixture editor to take the original fixture profile and add a separate dimmer subfixture. When patching the new fixture the dimmer and the colorcommander would have their own DMX start addresses.

Copying memory zero is one way of programming blackout cues ... or would be if you could copy memory zero However it is not the best solution, because it is rather clunky, and all the LTP parameters would be programmed at their home positions, thus introducing redundant moves and defeating move on dark in that blackout. Try switching Smart tags on, then just hit the BLACKOUT button, or lower the GRAND MASTER fader, and then press record. Hey presto, quick blackout recorded which will allow move on dark