K-Nine

There is a known problem with the desk locking up if the auto-save occurs when programming blank palettes: Frog Reference 5510 - After programming blank palettes - "Saving Show, Please Wait... 100% Done." message stuck on LCD, requiring a reboot to fix. Bug.

Presumably you mean the palette lock feature as far as the flash buttons are concerned but NOT the palette lock as far as what is displayed on the monitor screen ? Wouldn't you then have a potential for confusion as the buttons are doing one thing but the monitor is showing something else, or do you change what is on the monitor screen after you press the Brightness button ?

Naming Shows - For a thread on this subject and links to numerous others .... CLICK HERE

Entering numeric values from the external keyboard is covered on page 7-14 of the manual Fade times may be entered in seconds only, seconds and tenths, or minutes, seconds and tenths.

You can always type the times in directly from an external keyboard ... this maybe not as good as using the wheels but is certainly quicker than moving through the three parts of the fade time field and using the cursor keys to set the time

Good point ... it's designed as a press once for blackout, press again to remove blackout Frog Reference 5558 - Disable autorepeat on Blackout button.

For more information on CROW fm ... CLICK HERE For more "CROW fm experiences" ... CLICK HERE

It sounds like the Blackout button is auto-repeating when held down, something that most of the front panel buttons do and in some cases is desirable. However, I suspect it is not desirable in the case of the Blackout button ... maybe the auto-repeat should be disabled ?

First check the status of the internal battery - if this has failed or is low this may explain why the desk is losing the show data. Enter Super User mode and select the Desk Information option. Look at the Battery Status option - it normally shows "OK".

This is indeed a 'phantom' button and shouldn't be there. It is a known bug in the Phantom Frog software. :oops: Frog Reference 5471 - Phantom Frog (FatFrog mode) - Spurious Group button. The Fat Frog desk uses the function button F4 as the Group button.

Helium Inc. ... well Helium is pretty light

CROW fm Cwmbran's Community Radio Station, 107.5 CROWfm was launched on Saturday November 27. The station provided a lively mix of music of news, talk and entertainment for Cwmbran and South Torfaen for 28 days. The "Brain of Cwmbran" quiz show between teams from Cwmbran pubs was presented by K-Nine. The station went off air, at 4 pm on December 24, playing out with Whitesnake's "We Wish You Well" (K-Nine's choice )

When you copy a memory from one location to another you simply get a copy of the memory data - there is no link or reference maintained internally between the source and destination memories.

If it's a relatively simple scene, why not program it directly onto a submaster and use that each time it is required ?

On the Frog 2 - A cue as an entity has a wait time, which if programmed which makes the cue run automatically when the previous one has completed. In addition ... every fixture parameter programmed in the cue (intensity, colour, gobo, pan, tilt etc) has it's own delay and fade time.

It sounds like the position chase also contains colour and probably beamshape data as well. If you only want to record the position parameters into the chase hold down the POSITION key and then press PROGRAM when programming the chase. The memories screen should indicate which attributes are actually programmed in the chase; you can also check on the preview screen.

Frog Reference No 5509 - Updating palettes - "Saving Show Please Wait" message appears frequently when it may not need to - to be investigated.

Assuming you were in partial mode when recording the palette - then that is correct. If a selected fixture (red LED on) is NOT programmed in the palette being output, it's output values will not change.

Ensure that the desk is in partial mode. Only tag those fixtures you want in the palette. Note that when you output a palette - only the selected fixtures which are programmed in the palette will change to their programmed values. For example: Set fixtures 1-6 to red and record them into colour palette 1. Select all fixtures (eg 1-12) and home the colour - all fixtures go to white. Select fixtures 1-3 and output colour palette 1 - fixture 1-3 only go to red; other fixtures do not change. Select fixtures 7-12 and output colour palette 1 - no change to outputs since fixtures 7-12 are not programmed in that palette.

Pressing F3 and then the Memories, Submaster or SX button (Mambo) is the method used for initiating the individual adjustment of chase modifiers. For further details: CLICK HERE

I don't think that the syntax you described can be used for tagging/untagging fixture parameters :? Fixture parameters are tagged automatically when changed and can also be tagged/untagged manually via the mouse or the command FIXTURE X <attribute> N ENTER.

It may be that the cue you are clicking on is an Auto cue and as soon as the current cue completes, the next cue (auto) will run. I would need to set up a desk and experiment to verify this possible explanation.

If you want to run separate chases with your fixtures on the submasters without affecting the main 'look' from the memories on the playback stack (playback X) then you should run the desk in PARTIAL Mode. In full mode - everything ie all generic channels and ALL fixture parameters are recorded into the memory/submaster data. Consequently, everything will be output when you play the memory or raise the submaster. Partial mode gives you a lot more flexibility especially with the submasters. Remember though that even in partial mode the HTP channels (generic channels and fixture brightness parameters) are ALWAYS RECORDED, so if you don't want any generic channels or particular fixture brightnesses to come on when you raise the submaster fader, ensure that all unwanted HTP channels are set to zero when you record the submaster data.

Brightness parameters are processed HTP - therefore check that there is not another source which is causing the fixture brightness channels to be output at full. This could be from the Program Window, Current memory on the playback x or another submaster.

A movement speed of -100 will almost certainly be the cause of jerky movement of fixtures ! A speed of -100 is the highest speed in the anticlockwise direction. Most fixtures cannot keep up with the rapidly changing DMX values that are being sent to them and therefore appear to move jerliky. It is recommended that smaller speeds (-30 to +30) are used to obtain smooth movement effects.