Paul

Are you asking for 'macros' in the memory stack, that for example could be used to trigger submasters?

What if more than one submaster is running a chase, what do you expect the desk to record then?

Err, what are you asking? :? Which piece of equipment has failed? None of the Frog series desks use the 75176 RS485 Transceiver :?

No, that one's not possible either

Not possible on the frog series, sorry. However this is something you can do with the user definable faders on a Frog2.

You can copy data from one fixture to other fixtures. Works best if the fixtures are the same type, otherwise you get all sorts of odd results 1. Select the fixture(s) that you wish to copy the data to. 2. Hold down the relevant attribute selection button (brightness, colour, beamshape, position). 3. Select the fixture that you wish to copy the data from. Simple Ice you're right this has been mentioned before, CLICK HERE. edit: fixed link

Just dug out some of the other suggested acronyms for the FROG function... Channel Randomise On Attribute Keys Supply Parameter Attributes With Noise Pseudo Random Output Sequence Preferably Excluding Reset Operands For Absolute Terror - Frightening Random Outputs Guaranteed Quite Unusual Effects Engine Really Lighting Effect Generation System Bash Random Attributes In Nauseating Succession Random Attribute Value Effect Make Interesting Swirley Shapes Prompting Instant Great Gig Yells Keep Expecting Random Mayhem If Touched Create With Moving Bulbs Random Anarchic Nausea

The FROG function isn't really meant for the show, it's for the inevitable disco afterwards on smaller gigs. It means you can go to the bar, rather than run the disco... As I recall the desks were named Frog before K-Nine came up with the matching FROG acronym for the Auto-chase function. Other suggested names for the desk were Prospero, Super A&E and DX-K. Not so catchy really... It could have been worse, the development name for the Illusion desk was George...

Can you reproduce the crash?

The time used for the Fade transition between chase steps, seems (by experiment with Phantom Frog!) to be dependant on the setting of the speed pot when the chase is programmed. This can be overridden with the speed pot when the chase is played back. The Snap/Fade setting you're looking for is the one you see when editing the chase (Col Action, B/S Action, Pos Action), not the one you see on the memories screen (Colour, Beamshape, Position).

Hi Ian, Adding a battery to the current Linebacker would not be a simple task. Firstly, the electronics design is too power hungry to give any usable amount of battery life, and secondly, there's not much room in the box! Wireless DMX and/or a programming link to the console would be very desirable features. However adding a robust wireless link would have a significant impact on the affordability of the unit and we'd have to look at the commercial factors here. If there are any other suggestions for features on a new linebacker then we'd be interested to hear them. We do read everything on the forums - apologies that no-one acknowledged your first post. Paul.

The Demux24 can be set to output positive or negative on a socket by socket basis. The Demux48 is still available, in fact there's a batch going through production right now. Although they're now in Beta2 dark grey, as opposed to the Beta1 light grey as pictured on the website. It's positive by default, although you can fit an optional negative card. Edit 14/12/2005 Demux48 is now discontinued due to component obsolesence.

This all sounds like the internal battery is on it's way out, or there is a hardware fault on the desk. If it's still within it's 3 year warraty, get it back to us and we'll take a look at it. Keith Rogers is the man to contact (techsupp@zero88.com).

Using the speed pot to adjust rates set by the new beat function is an interesting idea, but would cramming in another chase modifier option with the existing panel controls/LEDs get confusing? I think this would be overloading the existing panel controls somewhat. The feature list for the next release will be made available only when it is finalised!

As you scroll up and down the memory stack using the +/- keys, the LEDs next to the chase modifiers will show you what is programmed in the selected memory (highlighted in yellow on the monitor). However, when you press one of the chase modifier buttons, it's changing the live adjustment of the modifiers, which might not be the same as what's programmed in the selected memory. I guess this is what you're seeing. It's a little confusing at first, but with one set of LEDs/buttons on the panel now providing 2 functions (since live chase modifier adjustment was added in release 9), there's not much else we can do.

Are you running the chases from Submasters or from the Playback X ?

We already have the following logged: Frog Reference 5437 - Memories with Auto Triggers and Edit Mode - Edit the Next memory, memory stack continues running if automatic triggers. I guess if you pressed GO, the same thing would happen as with an Auto Trigger.

20euro doesn't sound too surprising, have a look at the ones we use in Fat Frogs: http://uk.farnell.com/jsp/endecaSearch/par...jsp?SKU=3534029

Can you not already achieve this by using the Edit function, instead of performing the live temporary adjustment?

We already have the following logged for consideration: Frog Reference 5430 Allow previewed memory/submaster/SX to be changed without closing preview window. Edit: Frog Reference number for your suggestion: Frog Reference 5562 - Preview button to allow next memory to be previewed from the Outputs screen.

It's not the searching that takes the time. It's the commiting of memory/submaster/SX edits from the battery backed RAM buffer to the Flash memory if data has been removed from the palette. It might be that the desk is thinking that data has been removed when it hasn't, and is hence making more work for itself than it needs to. This is what we shall investigate.

Correct! Remember to consider palettes on a fixture by fixture basis though. If you remove a fixture from a palette, your memories won't change. If you alter a fixture in a palette, your memories will change.

>>>>>>>> Clearing Referenced Palettes If fixture data programmed in a palette is changed to “unprogrammed†or a palette is cleared – for any memories / submasters / SXs which referenced the data in the palette – the palette reference will be replaced by the actual DMX value in the palette before the data in the palette is cleared. <<<<<<<<

Data can be removed from the palette for example by untagging a fixture.

The problem is not the data that is in the palette, this is referenced as you say. The problem is the data that might have been removed from the palette. This is why the desk has to search all memories / submasters / SXs that reference the palette.