ice

The same as this topic I guess: but still; why?

That first point you mention is rather irritating. You can't alter speed / position / whatever parameter without completely freezing the movement or getting weird effects. When a fixtures is moving by the effect generator, why isn't that displayed as being an effect?

Select the channel and raise the value all with the navigation keys (after pressing edit of course). Or a quicker way; edit -> press the flash button of the channel you want to alter -> punch in 0-100 (in your case 35) on the numeric keypad of your keyboard.

Thanx for the trouble, but I meant to set straight the error. I'm not really interested in the new console, let alone we can't afford one (certainly not in 2 months). Just wanted to set the error straight for folks who do want one

Hmmm that's true, but you can reach HOME with only one press, starting a pallet takes two (hands). But I can manage using the first pallet.

It's not the number of fixtures which determines the need of pallets? I do a fairly large band with horns and stuff, that takes about 12 pallets. They play about 40 songs (not all in one evening of course), and in most cases I use chases for those songs (colour / gobo / strobe etc), so I use pallets in those chases (so I don't have to reprogram those). But there's only 12 left, so those 40 songs have to be done with 12 pallets, which I think is way too little. In the best case I have a position pallet for each song, so I can make different positions for every song they've got. The only way to do that now is program some position not in a pallet but in the chase. That sucks because I now have to reprogram every step of the chase :S Also; because of the lack of programming down to attributes, it's impossible to mix pallets. So you now have to program a strobe setting for each gobo, same with prisma. Convinced?

Rolight in the Netherlands.

Problem solved, the MACs still ran on louzy software Sorry to bother you guys, the Frog once more seems to be excellent

I know that's also beta, but the version we're running is 1.3.4. I'm getting an update tomorrow, and I'm gonna take the console with me to check if it's fixed. Oh by the way: we now own 2 Frogs... Rrrrribbit!

An online FROG function http://allaboutfrogs.org/funstuff/randomfrog.html Something to build into F2?

I believe I found the cause of the problem. While our dealer assured us of the software being the latest version, I found out we're running a beta, and a official 1.4.3 was released on the Internet. So I'll go and update (again...) and hope all problems will be solved. I'll keep you informed about this.

There are laws for that, but that would mean you'd have to walk them twice as much

Depends on how your console is set up. If programming mode is "full" then everything is always recorded. When it's set to "partial" only tagged (not selected!) fixtures are programmed. For more info; rtfm! Nope, when you want to black out chase 1, just pull down the fader. The brightness channels als HTP: Highest Takes Percendance, so whatever output on whatever fader or wheel is the highest the console will output. If you really want to black out you should use the shutter parameters, since that one's LTP (Latest Takes Percedance). Once more; check the manual, it's all in there (the manual doesn't care how brand new your console is I guess )

What you need is called "pallets"... read the manual!

By tagging fixtures you're selecting the fixtures you want to program. So if you want to program the brightness of those fixtures, just alter it to the desired level. Brightness is an HTP parameter, and therefore always programmed in every scene or chase. If you want to black out fixtures, just turn it to zero, or use the shutter for that purpose (don't know why you would though...) As it says in the manual: always use the playback X fader at 0% while programming....!

That makes no difference. The new software in the heads have improved moment qualities, so the weird things happening before are solved (the heads couldn't keep up with very fast moves). I've looked up the serial number of the console: 007380101470005 And the tag says it's manufactured in November 2001, so that's a while ago. I can't find an explanation for this problem; Robe's work perfectly, no jerky moves at all; but the Kryptons shake like duck (nothing to work with really). Martin doens't recognize my problem and because they work properly on another controller, or with a slow movement speed set up they're blaming wiring / console. The wiring is definitely not the cause of it, so that leaves the console I'm afraid.

Question: why would you even want to do that? Just program some memories and use the keypad to go back & forth? I don't really get where you're going with this.

My dealer told me he wasn't expecting the console until august. Why is that?

Any ideas on fixing this one? It doesn't seem to be solved yet. I didn't have much problems with until I really needed some smooth fades, and didn't have time to play with the movement speeds. Sorry guys but even movement made by the position effects generator is louzy. I used: 4 macs 250 krypton; I set up a circle movement with no Y and 100% X. Set the speed to 2, and there they went! The movement was jerky (and ugly), nothing to work with. On the other hand (strangely) our Robe washes don't seem to have the same problems. So that's why I thought it was one of the software bugs the Kryptons had. Went for an upgrade, and checked out movement at the same speed on a different controller (non-Frog); too bad it was super smooth. That only leaves one cause here, and that's the console. I'm going over to program some more stuff tonight, so I'll make sure to write down the serials codes and stuff. Oh by the way; I checked out the fine channel manually (reading it out at the head) and that seemed to jump. I know that's rather normal because the "rate" told me the Frog sends about 20 DMX packages per second. But could that be the cause of this problem? I know the Kryptons movements are very, very well calculated, so maybe it moves 20 times a second causing this jerky movement?

Why do you even want to use a Frog for the Catalyst systems? That seems to be your problem.

Very nicely done, photographs are really good. Unfortunately the photos of my show we're taken by the sound engineer from behind his console

Switch your flash function to "off" and press the flashbutton; works just as quickly I think.

Uhhh how am I going to explain in English It's a choire of approx. 50 persons (10 guys I think) which was combined with an orchestra (you see in the back). There was also a seperate percussion stage on the left. This show was given in a sports arena, so we had to do a lot of work on it; we did the rigging, lighting and sound. You can view more photos @ http://www.idak.nl/?action=photoalbum (Dutch website of a company I do some work for sometimes). The decor used was the same as used for the concert of Marco Borsato in "De Kuip" in Rotterdam this summer. It's very cool, made by Heavy Decor; those guys have a lot of decor in the scrapyard style; http://www.heavydecor.nl (also Dutch). Had a lot of fun, too bad there was a shortage of time: we did some work at tuesday 11pm - 2am, than again on wednesday 10am - 11pm, I programmed on thursday, which was also the last rehearsel (how do you spell that? and how is that called in English?). Made some quick adjustments on friday, and friday night was the first show! Did 4 shows and then got it all down and loaded in 3 hours. Got home broken

New show: Done with 4 MACs 250, 6 Robe 250XT's, 6 518's and a bunch of conventionals.

It works for more fixtures too. For instance; program a shutter chase: FX1 strobes -> FX2 strobes -> FX3 strobes etc. Select all fixtures and scroll in a gobo, it'll stay there for all fixtures until you restart the chase!