ice

Correct... and when such a chase is set up, a random option would discard the sequence, but turn a fixture white by random; so you'll never know which one it'll be... would be a great effect indeed. Next desk with partial programming is so gonna rock

You're missing the point! 24 fixtures; now programmed like: step1: fix1 = white, fix 2-24 = yellow step2: fix1= yellow, fix2 = white, fix3-24 = yellow step3: fix1-2=yellow, fix3=white, fix4-24 = yellow and so on... programming a few of these effects (cool effects!) is duck, but outcome is great; that could be done a lot quicker with somekind of effect generator (or chase-generator?)

Effects generator on brightness; dimming waves... sweeeeet

Jup those are true issues, and have to be thought of indeed... but maybe Zero could make somewhat of a framework which validates the correctness of showfiles (by given algorithms) in which users can write there own C (or what language are u guys using???) code for manipulation... Some kind of module-based piece of software? Just making some ideas here

Depends on what it offers... when Zero88 decides to release the format of the showfiles (which I doubt they ever will?) I could write my own software doing the same thing, maybe even other users here could cook up some neat programs! That means more functionality, but also more chances of errors (buggy software)... but we've got the beta-testers

More like a "what can go wrong topic" isn't it Well I've got one too; 2 weeks ago we played with a band in the south of Belgium (Mons). The ride there was terrible; al the stuff loaded into a van which only did about 110 km/h tops. On a 10% slope the speed dropped to approx. 70 km/h in 4th gear Once arrived the party was held in a tent in the yard of the parents of the bride, so far so good; but we could reach the tent with our van. Solution: pushing all cases through 150 meters of sand. THAT SUCKED! We had to set up behind a screen, there was too little space but there wasn't any other solution... at first the father of the bride didn't want us to build any FOH because it would mess up the created mood. Build it anyway and threw some white cloths over FOH. Oh well... the band was very satisfied with us, too bad that didn't really help us dragging all the cases back to the van around 4am... :x Why don't they mention these thing when a band gets booked? :wink:

Because of the many questions here answered with "can't be done; desk wasn't meant to do that, or desk layout doens't allow that" etc etc I wondered if it would be an idea to implement some extra stuff in the offline Phantom Frog :idea: Features like copying pallets from one fixture to another arent too hard, and the deks doesn't have to know that data was copied from somewhere else does it? That would mean the offline desk would become more like a sepate piece of software, in stead of an emulator of the deks. And why not? Let's use the PC for what it was meant to do: manipulating data! Feature list I would LOVE: * copying of (single-)pallets from one fixture to another (of course same fixture types) * possibility to print out the DMX patch (so all other stagehands know what they're doing) and I know for sure I thought up a load more last evening when I was thinking about this, but of course... didn't write anything down :cry: Maybe other users have ideas about this? Maybe it could even go beyond the Phantom Frog and have a shell of its own? In the new world of offline programming Zero88 should extend Phantom Frog (and other offline programs) features; that's going to be the future!

Okay, here goes! I'm Jasper Siegmund, 19 years old and I live in Etten-Leur; a small city near Breda in the Netherlands. I'm a college student, studying IT in Breda. I'm a registered freelance lighttechnician, but I work mostly for 3 companies (IDAK/MUSS/TRALIE) which are situated in Etten-Leur. Mostly I do band-gigs, the fairly large ones. Sometimes I travel with real small sets; just 2x6 par 56', some effects and that's it! Sometimes the larger sets with our 10 Pro518, 4 Mac250s and some hired washlights or other fixtures. I do a lot of stuff; theatre, bands, local (house)parties, schoolplays, you name it... I really like my work and I'm trying to combine it with school in a decent way, not always very easy but I'm managing! oh and this is me on the left:

Guess I must have been the only one who knew about that one Quite useful sometimes!

Here goes: Absolute: all selected fixtures will have the same values, depending on the one you selected last. For instance: fix 1-4 have pan-parameter 10-20-30-40 and you selected fixture 2 as the last one. Turning the wheel up a bit will correspond in values 21-21-21-21 Relative: almost the same as absolute, but turning the wheel will now correspond to: 11-21-31-41; ie the separate values are being raised individually. Fan: apply a fanning effect to the parameter, very useful for pan/tilt features, as creating waves by offset, rotation effects etc. The way it's used: * fan first: the primary selected fixture will be first in fanning, that means it's value won't be changed, the last fixture will be changed according to the value on the wheels, all fixture parameter values in between will be raised like: 25%-50%-75% (in this case 5 fixtures). Example; tilt is at 0; set fan-first, select 5 fixtures en turn the wheel to 100. The individual fixtures will now have values; 0 - 25 - 50 - 75 - 100. Fan middle is the same, although it now runs from the center of the selection. Example; dmx value 150 (all fixtures) gets raised to 200 for the selected fixture. Resulting values: 100-125-150-175-200; great for making pan-crosses with movingheads! Fan-last; same as fan-first, but in a reversed way. I hope it explains a bit, my English is not that good. Just try the option and you'll know what I mean. I use it a lot in the position section, in others it's not that useful.

Note that when using Fade as a modifier, you should have a LTP time set up; otherwise the fade won't work. Where do you use the F/S? Memories; chase? I've used it quite a bit in V9.6 and didn't notice anything strange I guess.

Thanx, your show's not too bad either! Very nice

Don't know if there's a limit on the number of photo's in this topic; but here's some I've done. It's a quite large choir (80 persons) which sang some numbers from eurosong contests. I've done 6 shows (I think?) on our Leap Frog. I used: * 4x Mac 250 Krypton * 4x Movitec 250WL * 10x Pro518 * 3x Pro400 and some house-light conventionals in the different theaters. The pictures: A guy who competed in the junior eurosong contest: and (from another gig) ME! On the left btw...

That's kind of similar to the solution I've used lately: memory 1 = scene 1 memory 1.1 = scene 1 with fixtures at 0% has a fade-time, dwell 0... memory 1.2 = scene 2 with fixtures at new position no fade times but dwell according to the time your fixtures take to move into the new position memory 2 = scene 2 with fixtures at correct brightness level. Just use Auto as trigger for scene's 1.2 and 2, and a press of the go button will automatically do it's thing. Just one problem (same as Pauls solution); what when the director wants something changed? Right... go ahead copying or editing 3 memories. Ok, that maybe isn't such a big deal, but is still takes more time than editing just one.

Use your time preparing shows! Pfff I adore my free time during non-weekend periods

Had the same problem, it's not a bug just a quite illogical way of programmin I guess (in my case at least). The one thing you have to remember: the fade up/down times apply to THAT memory only. So fade-in is applied when going from x-1 to x, and fade down when going from x to x+1. So when you want the scene combination to fade in a particular way you've got to edit the fade down of x-1 and the fade-up of x! I made that mistake a lot of times when programming, cause it seems to make more sense that fade fade up/down times on the "selected" line apply to the transition made on a press of the "GO" button. That's not the case. Maybe you've got another problem but it sounds a lot like mine Just finished a show with OS9.6 and I used the memories a lot (with fade times), worked perfectly fine for me!

One problem Richard: when you've got a chase running on one of the subs, the fixture could have brightness 0, but should not be moved. If should work on fixtures which were not tagged in chases / scenes used on submasters at that moment. But I agree that such a function would be nice; makes a lot of work useless; so saves us some time

Ok that would be another option indeed, I've ran into this a couple of times, and it's really VERY annoying when the desk comes up with that error message :twisted:

Exactly, the .x numbers should be dropped, and a new inserst should automatically increase the rest. Okay, not a simple question, and I know it's covered in the manual, but maybe something to check out for the future desks

Hmmm I ran into the same problem, had some things on theaterdimmers which shouldn't be dimmed. We're only packing our desk, so no own dimmers! An option in the superuser to set a channel to switch would indeed be a nice option maybe for Frog 2 desks; when raised above a certain trigger level (like the subs) the channel is FF, otherwise 00.

That's indeed a good idea Laubfrosch! You should have mentioned that earlier

Don't exactly know if this is already covered, but I wonder why it isn't possible to insert a memory between for instance mem 14 and 14.1. I've ran into this a few times: and not being able to insert means a load of copying. Inserting a new memory scene should always possible! Just increase the 14.1 to 14.2 and change all jumps and stuff accordingly. Okay maybe not an easy task but "you cannot insert a memory here" is really the dumbest screen message I've seen until now. The desk has loads of memory and tells me I can't insert a memory at a location!? Okay another problem would be: 14 to 14.9 are used, and u want to insert at 14.1. Desk asks: all memories taken, create new or split? Split: 14.9 becomes 15 (memories >15 move to +1) and 14.1 is created again. Create new: 14.2 is created, 14.3..14.9 becomes 15..15.5 Those are some solutions to the problem, anyhow: the amount of copying when you want to insert at 14.1 really takes a load of time, and I don't really get why I can't insert a memory at that location.

Wouldnt count on that... why would you want that to happen? It's not like there's any use to it...??

ZIP drive?

One of our LDs had a similar problem I think, I'll ask him to read this post and give his comment.