ice

Last week I was working with a band from the Netherlands (Di-Rect) and they we're using a Jands desk for operating. I saw a really cool feature which could be a real hit if you implement it into the frog desks. The lighttech. had some pallets (or the Jands-equivalent) for his programs. Of course he was editing them before the show to make 'em right. He could do this by selecting a pallet in some kind of edit-mode, and the fixture selected would home in color and beamshape parameters, making it really easy to locate the fixture and program the right position. When the next update will provide a pallet-lock option, maybe another button in that mode would represet "pallet edit" and this function would become reality? I don't think it's a load of programming work, and it would be really cool. Give it a thought!

I don't really get the use of executing all pallets at the same time... ? Mostly my pallets will be combined with eachother in most scenes, and I find the attribute programming rather cool, what you're implying is like full programming right? Please explain it some more!

I think it's a good idea for you to copy some memories. For instance: when you raise the sub, you can step into the next memory, which would be a copy of the previous one, but without the fixtures! This way, when you lower the sub the fixtures would indeed turn off...! Also, when you copy the 1st memory once more (so now in place 3) and hit that one, the fixtures would also return to their original position. Make sure to use position pallets for these things (check the manual for programming pallets, and program those pallets into your scene's; altering one pallet will result in all scene's updating!) and you'll be in heaven. Okay; you'll have to use 3 scene's but that only more accurate in my opinion, you can easily keep up with what you're actually doing!

A1: You have a problem This can only be done by using the desk in partial mode. Full mode always programs everything on the desk, so that means your moving lights to. When you want to use moving lights in you scene's you'd really want to use the partial mode for easy programming. In partial mode; fixture have to be tagged (yellow LED flashing) in order to be programmed. Un-tagged fixtures won't be programmed. I never use full mode, so I don't know if there's a way to untag fixtures. U should change the mode of your desk to partial, and remove the movinglights from the scene's you use on your submasters. That's done by using the edit-button (press twice when you're editing a chase!). That allows you to untag the fixtures (by pressing the fixture buttons for more than 5 seconds), now your problem should be gone. A2: That's nearly impossible. My guess would be that the brightness parameter of your MACs is maintained somewhere else (playback X??). When you only raise the submaster, lowering it should bring the dimmer back to 0% again, there's no doubt about that! Maybe someone from Zero know this better than I do??

When you've programmed a pallet into a scene / chase and display that chase the parameters of the fixtures display the "normal" DMX values ipv Pxx. Why is that? I'd rather see them displaying the pallet numbers for easy reference of what you're outputting from where. Is there a reason for not doing this?

Of course you could use the search function.... all this has been talked about long ago.

sorry missed that one

Hi there, I was wondering if the "outputs" screen could be expanded with a screen which displays what you're running. For instance: when running a scene from the memories screen, and some chases in different submaster pages I easily get lost in "what's what!?". I dont think it should be to difficult to create another page, displaying: memories: memory name - next memory name submaster 1: name of scene/chase running on submaster 1 and the submasterpage that scene/chase is in submaster 2: name of scene/chase running on submaster 1 and the submasterpage that scene/chase is in etc. etc. I would really love such a thing, since I don't seem to be able to remember what's running where when using a lot of different things at the same time

Sounds to me as if your brightness was being controlled by either submaster / memories output, if so you can't turn it below the highest of each (HTP channels!). I also experience problems with the wheels, but those problems seem to be a hardware fault; sometimes they just don't respond for a few seconds, turning them a few times makes the problem disappear so I guess I'll open up the desk to check the connections.

What I find to be te problem is the ammount of subs one can use at the same time, 12 isn't that much when you're working with, say, 4 different fixtures types, which u want to program type-wise, giving all fix. some chases in color, some in gobo, and of course some movement. Maybe even brightness! Outputting those will result in 4 subs up, and only 8 left for 3 different types; see where I'm going? If any other operator has brilliant ideas about programming this way, let me know!! I really gave this problem a lot of thought, but don't seem to come up with any other solution than combining or losing stuff.

Yesterday I was running a show with 4 new MAC Krypton heads. I was running a memory with some basic lighting (conventional), a submaster with 2 conventionals chasing, and one in a different submasterpage (conventionals started in 3, then I moved to 9) with the 4 heads. I did something (I just don't know what!) which triggered a weird thing. The heads intensity was somehow transferred to the submasters which were running the chase. The chase itself disappeared (went out) and lowering the submaster resulted in the heads dimming. The yellow flashing of the subs to indicate the're on another page also stopped. Is this a bug? (could't replicate, I'm sorry) Or did I make a mistake somewhere? I'm really bothered by the fact that I don't have a single clue what could have happened!

Create a chase by holding the "type" button, it will go into chase mode. Then record each step by pressing program. The chase is now stored in your memories, and can be transferred to a submaster by "transfer no time". That should be all I think!

Any chance/way of converting that? Don't have Corel.

Great

We're currently running a production on our desk (Leap Frog) with 4 movingheads. Due to a lot of work the desk is programmed in another show this month, so it'll probably be replaced by a Fat Frog for that single occasion. Now I was wondering if there could be problems when we use our Leap Frog showdisk in the FatFrog?? Is it a matter of 12 fixtures which won't be loaded (no problem since only fix. 1-4 are used) or will the desk complain about an invalid showdisk? I really can't afford to get in any problems that week, that's why I'm checking in advance (I cannot check it myself unfortunately). I'll make sure the software versions are the same so that won't give any problems.

Parameter level programming is one thing, this is just a small part of it I guess. Just let us know the outcome of that meeting, please?

I'll start working on the other one when I've got a file... ??? That would be the normal "Frog Series" issue.

Any idea on a release-date? Pleeeeease do me a favour and release it before 17 jan. Really could use those features on a show I'm working on.

I don't think translation software will work properly, since the highliting (CAPS for instance) of words has to remain. About that knife: doesn't everyone own a gerber or leatherman or something? I certainly do, so replace that gift will ya A file would certainly be excellent.

Already thought about a Dutch version, don't know if I'll start to really write it. Maybe some other users here (i know Pipo is from Belgium right?) are interested in a team-up to translate it to Dutch? How are you actually going to do it daoops? It would be cool if K-Nine could send us the original version so the entire layout of the manual is preserved. Or is there a way to easily edit the PDF files? (preferably with a spell-check )

This simply can't be done. It's impossible to program only C/M/Y values or gobo's etc. onto a submaster since you can't program on attribute level. There are some more topics here about transparant programming, you should read them to understand what the desk can / can't do.

Not to mention the sound some fixtures make during blackouts when running full-speed My solution is really more like a workaround, I know it doesn't work in some situations.

I know that, but it really bothers me that it always stores the entire group. So when beamshape contains shutter and gobo, I always create 6 shutters fast-slow, 6 shutters fast-slow but unsync'ed, 6 fixed gobo's and 6 rotogobo's/prisms... When you use this approach, a nice setting with different gobo's will be killed by using one of the strobebuttons, since the gobo info will be reset. This means I'll have to program strobes for each different gobo too, add extra prism pallets, etc. etc. A load of work which isn't really nescessary in my opinion. I would really like to hear the programming issues concerning my request, if there are any?

What I always do is create a "KILL" memory to fix this problem. Just hit "home" for all your fixtures and program those positions into a memory (by holding "position" and pressing PROGRAM). Transfer that to a submaster, and pressing the flash button will result in the fixtures homing and a full stop. The only nasty thing comes up when u use different groups of fixtures. You wouldn't want to stop the entire show I guess Just use page 9 of the submaster and program a few KILLS for your different groups. If anyone has a better solution I would love to hear it, but this always worked for me. When the next software version is released I think it's possible to program the shape generator into your pallets. Then you could program the "none" shape into the final pallet and the problem would be solved entirely (just select the fixs you want to stop and apply the pallet)

Wouldn't that be the FROG function which sort of creates chases itself?