K-Nine

Another thing to bear in mind is that even if the DMX outputs of the desk snap to the new values in zero time (or as close to zero as possible) not all fixtures can respond that quickly, especially if it involves large movements etc 8O

I see your point Haytech, but the way the Park function works on the Frog 2 desk is that it freezes the outputs of the fixture. Parameters of that fixture may still be programmed into cues etc, or not as required, at any level, by the user. You just don't see the outputs change live since they are frozen.

In the absence of a park function, you could always program the state of the ambient lights directly onto a submaster and just leave that raised

The DMX output from the two sockets should be identical. If they are not it sounds like there is possibly a problem with the DMX output board.

In Full Mode whenever you program a memory (scene or chase) or a submaster EVERY GENERIC CHANNEL AND FIXTURE CHANNEL will be recorded and consequently output when the memory is output or the submaster is raised. In Partial Mode, only those fixtures tagged will be recorded and output when the memory is output or the submaster raised. Personally I would recommend Partial Mode as it is far more flexible and allows you to program submasters that can just affect colour, beam or position of certain fixtures, without changing the outputs of untagged fixtures. You should decide which Program Mode you wish to use and set it to that mode before programming your memories and submasters. Program Mode is set in Desk Setup in Super User. See the following sections in the Frog Series Operating Manual: Memories - Full and Partial (Page 4-4) Submasters - Full and Partial (Page 5-3) Desk Setup - Program Mode (Page 6-9)

Whatever fixtures are programmed in the submaster data will always be output when you raise the submaster fader and trigger the LTP parameters. However, what you could try is programming the strobe effects into one or more beamshape palettes. When you want to strobe certain fixtures, simply select the required fixtures first and then output the appropriate palette - the data in the palette will only be applied to the selected fixtures

Slight correction to Haytech ... Press and hold F1 and then press a fixture selection button : This displays the Fixture Outputs Screen on the monitor which shows 12 consecutive fixtures starting at the fixture selected

As far as I am aware, we have never removed any functionality in all the various software updates we have issued, and I doubt very much we will do so in the future. If the F4 button is used in the future we will have to consider how this affects the group functionality on the fat frog.

Seeing as the Fat frog is the best selling desk in the Frog range I think it would be unwise to leave it off that particular desk

You are correct - on desks other than the Fat Frog it has no defined function (at the moment) ... but with so many suggestions and ideas that are still to be considered and reviewed, I'm sure it won't be long before we use it

Would this be similar to the 'Park' function on the Frog 2: When a fixture is parked it's current output values will be frozen, and cannot be adjusted by any method, until the fixture is unparked by the user.

How many faders did you have in mind Sam? The Frog2 does have DMX In. I guess this would be a good way to connect a simple fader desk to use as a wing. I don't think it does very much right now, so any suggestions what you'd like to be able to do with it?

Frog Series Operating Manual (Issue 6) - Fixture Outputs Screen - Page 7-11

I think it's possibly a problem with the monitor display not quite keeping up with the button presses. Try entering the memory number directly from an external keyboard (eg 123 ENTER) ... it's much quicker and it doesn't overshoot

NOTE: When you are adjusting fixture parameters and the wheel editing mode is one of the fan functions, you also have to bear in mind which of the selected fixtures is the 'primary' fixture (indicated by flashing red LED). For example in Fan First mode - if the first fixture in the selection is also the 'Primary' fixture, then it's value will be displayed on the wheel LCD. As the first fixture's values are fixed, the value displayed in the wheel LCD will NOT change, but moving the wheel should change the values of all the other selected fixtures accordingly

If you have an even number of fixtures selected and you use the fan-middle editing mode, the values are fanned around a 'virtual fixture' in the middle of the selection. For example if you had selected fixtures 1-4, then the output values would be centred around a 'virtual fixture' between fixtures 2 and 3. Suppose the pan values of fixtures 1-4 were all set to 50%; select fan - middle as the editing mode and gently move the pan control wheel. The values of fixtures 1 and 2 would decrease and those for fixtures 3 and 4 would increase, giving you something like 30%, 43%, 56%, 70%.

The Frog2 has 2 power switches, one on the desk, plus one on the power supply

Fixture Outputs Screen perhaps ??? Press and hold down F1 and then press one of the fixture selection buttons

Moderation: Post moved into this thread: Frog Reference 5555 - Insert and Delete keys on the external keyboard to map Insert and Clear buttons on the desk.

Sorry, but there are no print functions on the desks themselves either. One thing that has been mentioned in the past, and I stress this is only a possibility, is a PC utility that can take a show file from a frog series desk and generate a number of different reports showing cue lists, fixture assignment and patch, channel usage etc. Frog Reference 5521 - PC Utility to export/import show data as a CSV file for use in a spreadsheet. If there was a market out there for such a utility then we might be persuaded to produce one :wink:

Unfortunately, at the moment, there are no print options from the Phantom Frog. Frog Reference 5484 - Print options for the Phantom Frog.

All the desks in the frog range are capable of running multiple chases from the submasters (and SX buttons on the mambo) but it is the Playback X which uses a different mechanism and internal data structure which we are concerned with here.

Various combinations of real time triggers, auto triggers and jumps in the memory stack could provide a variety of possible solutions

Scaling the movement effect speed parameter to be a more sensible value as already suggested is a much simpler and quicker solution. Any additional data added to fixtures in the fixture library is not a trivial task AND the desk software has to be updated as well 8O

Maybe we should add a monitor screen as well :wink: