K-Nine

You cannot patch the same DMX output to more than one fader.

At present, the remote switches can only be configured to act as Go button pushes or Go to memory (Frog Series Manual - Page 6-9). Frog Reference 5487 - Extend options for Remote Switches

If I may quote from the Frog Series Operating Manual, the book according to Memories, Chapter 4 Page 7 ... Partial Memories The output levels of generic and fixture brightness channels are always recorded regardless of the fixture tagging and attribute selection. To record only the brightness levels of fixtures, all fixtures must be untagged prior to pressing the PROGRAM button. 8)

Since we are going to allow fade times to be specified and editable for channel data on submasters in the next update package - we are going to have to redesign the main LCD display for the submasters. Therefore it should be relatively easy to add in a submaster name field. However, this field may be a display (read only) field since the naming function for memories, submasters and palettes has already been defined. Frog Reference No 5455 - Submaster name displayed on Main LCD.

Frog Reference No 5454 - Separate Wait or Dwell times for LTP parameters - to be reviewed.

Yes, it is possible I suggest you put the desk in partial mode first, select the fixtures you wish to be controlled by the submaster, set their brightess (intensity) to full using the control wheel, then save the data directly onto a submaster. The submaster fader can then be used to control the brightness/intensity level of the fixtures without affecting any of their other LTP parameters (colour, gobo, pan tilt etc.)

The Battery Status is also displayed in the Desk Information section of Super User.

It's not just the tagging of individual parameters that is the issue, it's the untagging, ability to tag/untag all parameters for a particular attribute or fixture, display of what is actually tagged etc. I agree that simply moving a wheel could tag the parameter, but you can't use the attribute and wheel to untag as this combination is already used to change the wheel editing modes.

Compared to the time required to program the actual chase, the additional time and key presses required to transfer the chase memory onto a submaster is probably quite minimal. In the current software submasters can only contain a single set of channel/fixture data or a reference to a transferred memory. To enable the user to program a chase directly onto a submaster would require a significant change to the internal data structures and user interfaces.

Generic (Dimmer) channels and Fixture brightness (intensity) channels are treated as HTP (Highest takes precedence) channels. Fixture Colour, Beamshape and Position parameters (eg colour wheel, gobo, pan, tilt etc.) are treated as LTP (Last teakes precedence) channels. The processing of HTP and LTP channels is significantly different: A HTP channel output value is calculated from a number of different sources - preset faders (generic channels) or virtual faders (fixture brightness), submaster(s), sx buttons (mambo) and playback X. An LTP channel output value is based on whatever it was LAST told to do - which could be from the control wheels, submaster, playback or by outputting a palette. If you create a fixture type a parameter will behave as HTP if it is classed as brightness, or LTP if it is classed as colour, beamshape or position. A colour palette will only contain fixture colour parameter levels. A beamshape palette will only contain fixture beamshape parameter levels. A position palette will only contain fixture position parameter levels. Back to the original question .... If you want to copy brightness 'scenes' into a chase memory - use submasters - either program the 'scene' directly onto the submaster as channel data, or program a scene memory and transfer it onto the submaster. If you want to copy colour, beamshape or position data into a chase memory - use palettes. Hope that clears things up

At the moment it is only possible to program channel data (generic/dimmer channels and fixture parameters) directly onto a submaster. The only way to have a chase running from a submaster is to create a chase memory and then transfer it onto the submaster. If you want to keep the submaster and playback x (memory stack) separate, you could try programming the memories you wish to use on the submasters at higher memory numbers (eg start at 900). If you put a jump at the end of the normal memory stack back to the beginning then these additional memories won't affect the memory stack.

We are investigating this problem. We have not seen this particular 'bug' ourselves, nor have we had any other reports of this particular problem. Have you tried using a different external keyboard ?

A frog goes into a bank and approaches the teller. He can see from her nameplate that her name is Patricia Whack. The frog says: "Miss Whack, I'd like to get a $30,000 loan to take a holiday." The teller looks at the frog in disbelief and asks his name. The frog says that his name is Kermit Jagger, his dad is Mick Jagger, and that it's okay as he knows the bank manager. The teller explains that he will need to secure the loan with some collateral. The frog says, "Sure, no problem, I have this", and produces a tiny porcelain elephant, about half an inch tall - bright pink and perfectly formed. The teller is very confused, and explains that she'll have to consult with the bank manager and disappears into a back office. She finds the manager and says, "There's a frog called Kermit Jagger out there who claims to know you and wants to borrow $30,000, and he wants to use this as collateral". She holds up the tiny pink elephant and says "I mean, what in the world is this ? ". The bank manager looks back at her and says... wait for it ...... "It's a knick-knack, Pattie Whack. Give the frog a loan. His old man's a Rolling Stone".

Were you running the chase on the playback X or the submaster, and did you edit the memory or the submaster ? If you could send a copy of the show then we can try running it here and see if we can reproduce the problem.

As far as I remember the only way to ensure that the chase starts on step one is to finish on the last step. N-shot chases have been mentioned before and are in the Frog database for review.

The S and R/T besides times in the trigger column on the memories screen indicate SMPTE time codes and Real Time. Refer to the Release Notes for Software Release 8 for further details. CLICK HERE.

Doh, Didn't think of that one ... and it only uses the one submaster

Allowing user editable fade times on submasters which have been recorded directly (as opposed to having a transferred memory) is one of the features we are planning for the next update. CLICK HERE for further details.

There is now ... although it is a bit large :f

We don't produce a quick programming guide at the moment but it is something that we may produce in the future. What information would you like to see in such a guide ? However, I would recommend you keep the manual with you as it does contain a lot of useful information. (Totally unbiased comment since I wrote it :wink: ) If you have any operational questions about the desk please post them in this forum or contact me via email or PM.

The reason that the text below the buttons on the front panel display is 'fuzzy' is that the front panel picture was taken from the original bitmap of the front panel label itself and scaled down to fit on a monitor screen. However, if you move the mouse pointer over a particular button or fader, the name of the button/fader appears underneath the front panel display in the grey bar

Hi, We don't currently have n shot chases on the Frog desks but you could achieve the desired effect as follows: Program two scene memories with the two positions (scene 1 - centre stage, scene 2 - final fanout position). Set the LTP fade time of the second memory to the time you want for the lights to move between the two positions, eg 5 seconds. Ensure that the Position action is set to fade. Transfer the two memories onto two separate submasters (say 1-1 and 1-2). Raise submaster 1 - the lights go to the centre stage position. Raise submaster 2 - the lights fanout in the desired time. Note - It will probably be best if the desk is in Partial Mode as then only the lights in this effect will change outputs when you raise the submasters.

Whenever you program a chase, the brightness levels in the chase are programmed, maybe 0, but still programmed nevertheless. The effect you are seeing is because the LTP chases are tied to the HTP chases and the HTP chase on a frog desk stops running when the memory is no longer the current or previous memory. So if you trigger a Colour chase, then a Beamshape chase - they both run ok, as the Colour chase is the previous memory, and the Beamshape chase is the current memory. If you then trigger the Position chase - the Colour chase stops as the Beamshape chase is is now previous and the Position chase is Current. (Originally the LTP chases continued running after the HTP chase was abandoned (no longer current or previous memory), but this was considered a bit too confusing for the users, apparently)

The Frog Screen is a remote control touch panel designed for use with the Frog Box. It provides most of the functionality available on the Frog Box front panel, without having to be in the location of the Frog Box itself. The Frog Screen has 130 user-definable buttons which can be used to play back any of the programmed memories or act as a Go button. To download a copy of the Frog Screen Operating Manual CLICK HERE

A new version of the Frog Series software has been released. This version contains new functionality for the Frog Box which includes communications with the new Frog Screen. To download Version 8.2 software and release notes CLICK HERE.