Kirkup_xp

Check the grand master isn't down, and Blackout isnt activated. Which fixtures and which version of the fixture library are you using?

I would probably program Stack 1 as my main cue stack, containing the cues to be called by the DSM. This would behave in much the same way as the Fat Frog. For the cue you describe, I would program the generics into the memory within that state, then program the moving heads into one or two seperate cue stacks, setup as chases. The Macro just tells the desk that when you trigger the cue, it should also perform the commands specified - in this case, activating the two chases. The following cue (end of a song, for example) would then instruct the desk to 'release' the other running cue stacks.

On the Frog2 you have 10 physical playback masters on the front panel. Each of these can be used to control an individual cue stack with up to 999 memories. These playback masters, 1 to 10, can be paged between 1 and 100. This means that you can create multiple complex cue stacks for particular songs, chases, etc. Any one of the cues can have macros assigned to it, individual fade and delay times per parameter of any fixture. The basic command syntaxes for recording cues are: RECORD 1/1 ENTER (records stack 1, cue 1) 1/1 TIME 5 ENTER (sets the fade time of all attributes on 1/1 to 5 seconds) 1/1 TIME COLOUR 3 ENTER (sets the fade time of all colour attributes to 3 seconds) STACK 1 SETUP (opens the Stack1 setup window, enabling you to choose various options including move whilst dark and convert the cue stack to a chase). LOAD 1/1 ENTER (reloads cue 1/1 into the programmer for editing) UPDATE (updates the currently loaded cue) One difference between the Fat Frogs and the Frog2 is the fact that you cannot program an individual step of a cue stack as a chase. Instead, you should program a memory which contains a macro to trigger the chase. Although at first this may seem a hinderance, it adds the much requested ability to have a 'look' running at the same time as a chase. Hope this helps Peter

Yes, the fixture listed as Pro 400 is indeed the Martin Robocolour Pro 400.

As this file is now contained within the fixture library, I have removed the download from this thread.

Can you try downloading the latest fixture library (16.00), available here and see whether that fixes the problem. We've recently corrected this problem in the fixture library and this updated library file should fix it. If you continue to have problems with this fixture, let us know and we'll investigate furthur. Peter

Indeed, as you say, version 10.x allows full partial programming down to single parameter level. Palettes can be overlaid as you describe.

If you have trouble sourcing a Frog2 for hire, let us know and we'll be able to put you in touch with companies who have them in hire stock.

Have you re-enabled Partial mode after the upgrade? As far as I know you should be able to program down to parameter level in each area of the desk (Memory, Sub, Palette or SX).

Unfortnately the Solo function of a submaster flash button only refers to the HTP attributes of a fixture. All fixture parameters are mixed LTP, so as soon as you trigger another submaster or SX, the previously outputting data is overwritten with the new data. If you require this sort of functionality, you'd really be looking at a Frog2, which has a stomp/release system similar to that of a Hog or Pearl.

Have you thought about using the x-playback? I know its not the traditional method of running a live show, but it could work for your needs. You could program each song in a bank of cues (say: Song1 - cues 1-20 Song2 - cues 30-50 Song3 - cues 60-80 etc Once these are programmed, you would use the (big blue) Go button to trigger each stack. You could influence the brightness of the programmed fixtures using the Playback X Master. To jump to a song, simply press MEMORY, then key in the number from an external keyboard and hit Enter. Then hit Go. This might actually be quicker than jumping around submaster pages. One more thing. I know its obvious, but do check that you're running the latest software version on the desk. Previous software versions were limited to only 10 pages of submasters, and the behaviour of partial mode has changed significantly in recent revisions. I should also add that what you're hoping to achieve would be much easier with a Frog2, which features 10 playbacks on the front panel, pageable 1 to 100, as well as user definable faders (subs, masters, inhibits, etc) and user definable keys (macros, palettes, cues, etc). A touchscreen and two monitor outputs (which can be USB touchscreens) give you masses of buttons for busking. Oh, one more thing... unfortunately, © on your list isn't possible. Its a nice idea though... perhaps when Paul (who maintains the Frog feature list) reads this he may add it to the database of potential additions. Best of luck with the show. Peter Edit: One more thought. If you get given a set list before the gig, you could set up the Playback X using the "jump" column so that it runs sequentially throughout the gig. Using my above example, if the band decided to perform the songs in the order 1,3,2, I would place jumps as follows: After cue 20, I would jump to Cue 60 After cue 80, I would jump to Cue 30 I hope this makes sense.

Hi It is entirely possible to seperate out the brightness on the Frog. The method for doing this is to program all your cues involving the moving lights with the moving lights at 0%. Then, when you create your brightness submaster, detag all the fixtures and leave the brightness at full. The HTP elements of a fixture (ie the Brightness) are mixed throughout the desk on an HTP basis, so whichever submaster is highest will gain control of the fixtures brightness. One thing you will find different to the Hog syntax is the fact that the submasters are not cue lists. As such, you can't have more than one position on a submaster, except as a chase. If you really need this multiple programming, you could program it as a chase set to manual trigger, using the step button to step through the various positions. This might cause you problems on a page where you have more than one of these chases... pressing Step will trigger all active chases. Remember, to create a chase on a submaster, first create it as a memory and then transfer it to a submaster using the 'transfer no time' or 'transfer with time' buttons. Another feature to be aware of is the ability to lock the palette pages, so that the channel flash buttons become bump buttons for the palettes without having to hold down the attribute. To do this, hold down F1 and press the attribute you wish to lock to. Now pressing each channel flash button will trigger the palette on that key. To unlock the pages, press F1 again. Good luck... let us know if you have any more questions, and also let us know how you get on. Peter

As long as you store the base positions as palettes, the effects could be based on them and stored as raw data in the cues/submasters. They would pick up the updated positions and their base position would be correct in the new venue. HTH

Hi Cplater1 The Jester outputs DMX, so theoretically it can control any device with a DMX input. You should be aware that controlling fixtures via faders is somewhat complicated, particularly when busking. However, it is perfectly achievable with a little effort. Spend some time working out what level each gobo is found at and you should have very little trouble. Positioning the lights might be a little complicated, but if you're just looking for some basic movement effects, program a couple of chases using whichever faders control the Pan and Tilt of the fixtures and that should do the trick. Be aware that if the lights offer 16-bit position control, you should turn this off as the control you will be feeding the lights will be 8-bit only (the Jester does not support 16-bit parameters). I hope this helps a little. Give it a try and you'll soon work out how to control the fixtures. Peter

Yes, it does. If you require more, think about doublnig up (eg having a position palette where fixture 1 is pointing at its first 'special' position and fixture 2 at its first 'special' position, even if they are different positions). If you run out of position palettes, program raw data and make a note of the cues you need to update.

You've already hit on the biggest time saver for touring shows - using position palettes. If you're stringent and stick to using only position palettes for all the positions in your show, then you can just turn up at the venue, rig, then update the position palettes and the changes will filter through your cuestack. One thing you might find useful is to get a digital camera and take a photograph of each fixture in each position, in the original venue. Then, when you tour, you've got a permenant record of what it should look like. Apart from that, make sure you keep a paper copy of the show... even if its just a rough record of what goes on in each cue. Itl'l serve as a useful backup if you accidentally remove a cue or overwrite something. On the subject of backups, keep a copy from each venue. You might arrive at a new venue which has a similar setup to a previous venue so rather than making the changes again, you could reload that venues show and make the changes from there. HTH Peter

Hi Audioman Sorry to hear you've had a few crashes on the Frog2. As i'm sure you'll appreciate, the desk software constantly evolving and bugs are being eliminated every day. The bug you talk of sounds like one from a fairly old version of software. Can you let us know what version of software you are running on the desk? We're currently working on the release of version 2.0.21, which addresses this and many other bug fixes, as well as adding new features. I hope your initial impressions of the desk overall were good and that these small software problems haven't put you off. Keep an eye on the forum, the latest software should be up any time now. Let us know if you come across any more bugs or have any furthur questions. Peter

The first step to do this is to ensure the desk is in Partial mode. This is done by entering Super User (hold down +, hold down - and press ENTER) Scroll to Desk Setup, then press ENTER Scroll to Program Mode and press ENTER Use the arrow keys to toggle the value in the field to Partial. Press ENTER to confirm and then scroll to Exit Desk Setup. Enter. Exit Super User. Enter. *Now select cue 4 (the first of the cues which has excess programming). Press EDIT Select the fixtures. Press and HOLD each of the fixture buttons until the yellow LED stops flashing Release the fixture button Press EDIT and then ENTER to confirm you wish to overwrite the existing cue. Repeat from the * above for cues 5 to 19. Don't worry when carrying out the above that the fixtures will go to their old programming values when you hit 'edit'. This is normal, as you are loading in the existing programming. As long as the yellow LED is not flashing (it will be constantly on) then the fixtures will not be programmed into the cue when you hit EDIT the second time. For future reference, the sequence when programming for the first time is even simpler... -Set the desk into Partial mode (this should be done at the start of the show, whilst patching the desk, ideally) -Set up the first cue (the yellow LED will flash, to indicate that something on the fixtures has changed) -Press program -Make the changes required in order to obtain cue 2 -Assuming nothing has changed in the fixtures, the yellow LED will be constant and the fixtures will not be programmed -Press Program Now, if you wish to change the fixture in cue 1 and 2, simply edit cue 1 and the changed fixture data will track through to cue 2. Once you start getting the hang of it, this programming method is very quick and easy. (Advanced lesson below... feel free to ignore it) Lets say, for example, you make the change then in cue 3 to a new position. Pressing Program will record a new cue, with the new position in it. Now go back to cue 1 and change the colour. The data will filter through and cues 1 to 3 will all run in the newly programmed colour. If, however, you had 'tagged' the colour attributes in cue 3, they would have remained static. Tagging is effectively telling the desk whether or not to store a single attribute in the cue. To change the tag status of an attribute, simply nudge the wheel a little. Hold down WHEELGROUP to check whether a parameter is tagged. Tagged parameter will be displayed with numeric values, whilst untagged parameters will display ---. To untag a paramter, nudge the wheel with WHEELGROUP held down. I should add that this functionality has recently changed and you should ensure that the desk is running the latest release of software, (10.4), which is available here. Hope this helps.

Hi ChrisP Hope I can help a little. One option would be (and bear with me, this may seem a bit backwards) to 'unprogram' the moving lights from cues 4 to 19. The first step to do this is to ensure the desk is in Partial mode. This is done by entering Super User and going to Desk Setup, Program Mode and toggling to Partial. By removing any existing programming of the moving lights in those cues, you instruct the desk not to make any changes to the lights when those cues are activated. To remove the lights from programming, hold down the fixture select buttons until the yellow LEDs go on (instead of flashing). Now if you re-record the cues, the moving lights will be removed from the cues. You will notice (on the monitor) that the data in the columns C B P has disappeared for cues 4 to 19 (assuming you re-recorded all of them). This is another way of checking that the moving light data has been removed. Now running sequentially from cue 3 to cue 4 will not alter the moving lights. Because the desk has no data for the moving lights, it leaves them alone when the cue is activated. Your operator could pre-empt these changes by using blind mode (While in the Memories screen, press Preview, then Edit) to remove the fixtures whilst leaving the output on stage as it was. This will ensure that when you come to edit live, the fixtures don't return to their originally programmed position, saving you (the designer) the stress of having to deal with the fixtures being in the incorrect cue throughout the sequence. If the cue list was programmed in Partial mode originally, you would only have had to update Cue3 and the cue structure would have remained intact until Cue 20. I hope the above is clear and makes sense. If not, let me know and i'll try and clarify for you. Sorry its not quite a "1 thru 3 @ cue last" solution, but once you're used to programming the desk in Partial mode, it becomes almost second nature. Best of luck Peter

Chases cannot be recorded directly to the submasters, due to the memory structure of the Frogs. In order to have a chase on a submaster, first record it as a memory. Then select the memory and press TRANSFER NO TIME (or TRANSFER WITH TIME, depending on whether you want a fade time on the submaster). Now select the submaster you require and press ENTER. To make a chase loop, set the 'shots' to 0. Any higher number of shots will set the chase only to run that number of times. HTH

You don't need a visualisation package to preprogram your data on Phantom Frog. Ok, so you can't do position palettes, but everything else can be done with a little thought and a user manual infront of you. There are DMX lookup tables available for the most common CMY moving heads to give you colour data relative to Lee or Rosco gels, and the user manuals of the fixtures will tell you which DMX values will create a particular gobo or shutter effect. Spending time doing this on Phantom Frog, although boring, will save you hours in the venue. Then, when you get there, you can just replay each pallet and make the changes as required. The things which you can't program in advance (as I see it) are- Positions, Focusses and possibly Zooms. None of these could be done with the addition of a visualisation package.

Hi Eldar It sounds to me as if maybe you have the fixtures assigned to the incorrect start addresses. Each CX2 takes up 4 channels, so you should address the fixtures as something like 49 and 53 (the channels 1 to 48 are taken up by the generic channels, by default). Make sure that the units themselves are addressed to the same addresses as the DMX patch on the Frog. To do this, go into Super User and then Desk Setup, Assign Fixtures. Check that fixture 1 and 2 are set to Martin CX2 (4chan). If not, you'll need to get the fixture library from the main Zero88 website and load these in again - select "Select Fixture from floppy disk", then follow the commands to select the correct fixture profile. Now go into the Desk Setup menu again and go to Patch Functions, Manual Patch. Press the Fixture Select button 1 and use the + and - keys to set it to 49, then press Fixture Select button 2 and set it to 53. Now exit super user, saving the settings as you do so. Let me know if that solves the problem, Peter

Attached is the profile for the CS4 without dimmers. Please read these notes carefully before patching the fixture: When patching this fixture type, care must be taken to patch it correctly. In order to use the 4 lamps of the fixture, you must patch 4 generic channels on the desk as the first 4 channels in the start address. You must then patch the attached fixture type as the start address +4. Example: Start Address 001 Generic 1- 001 Generic 2- 002 Generic 3- 003 Generic 4- 004 Fixture 1 - 005 Hope this is clear. Please let me know of any problems with using this fixture profile.

I'll create you a fixture profile for this fixture and upload it on Saturday if thats okay? I'm working away from my PC tomorrow, so won't be able to do it then. If there is more urgency for this profile, let us know and we'll do our best to get something to you ASAP.

Using the cue stack, it is only possible to playback one chase memory at a time. However, if you program chases onto the submasters, you can play back 12(24) chases at a time. Every submaster can have its own chase, direction and attack stored. Programming and replaying chases is covered in the Jester manual. Hope this helps. Peter