[Richard CSL]

So I have set a cue stack chase to run 5 times Number of repeats in the timing options,
I have also set the cue stack to release in cue stack options, activate release, release after last step.
Can I now activate a different cuestack automatically.

This is for a nightclub use so they don't have the lights doing the same thing all night.
Also does this possibly come with a random "Jump to"n cuestack option. where n is a choice of entered cue stacks. (don't want it to automatically turn on service lights, smoke machines etc or strobes)
I have asked this qustion on the Chamsys forum, but did not understand the answer "posted below"

""
I've seen programmations for clubs in the next way:
- make a cue stack set as chase timing, for example Cue stack 1 in the stack store
- set it to random
- all cues in this cue stack are empty
- in the macro field fill of aal the cues, for example: F2>99, this release Cue Stack 2 till 99
- in the same field set for example also E2 in cue1 for activating cue stack 2, E3 for Cue2,....
This way it will execute randomly the cue stacks and release the others at the same time.""

I also asked the following.
Cue stack , view options, chase, number of repeats set to 3. runs through but does not release at end.
set to release after last step, only allows the stack to run through once.

So how do I get the stack to release after 3 run through and not pause on the last cue? (ie stack still active)

also how do I get a nice neat fade out at the end of the cue stack, I have set the release time to 3 seconds, but on using the execute screen the chase ends abruptly without the fade?
the only overrides would be service lights , smoke machines and strobes.
I will be putting all this on the execute page, and I notice stacks behave differently on the execute page than on fader main screen.
help needed.

[Richard CSL]

Judging from the lack of replys, I guess that chamsys magic q in execute screen mode might not be suitable for nightclub use,

damn back to Daslight it is then,

[paulears]

I suspect its perfectly capable - but probably the best way to find this would be to give Chamsys a ring tomorrow and ask - Wol and others often pop up to answer magicq queries during the week - but it's the weekend and I suspect work is the thing best not thought about at weekends. I don't doubt there's a very simple way to do it, but I read your post and couldn't reply because to me I couldn't quite work out what you were trying to do, and what the purpose was. Somebody did ask quite recently about running cue stacks that looped so many times then did something else and I think this may have been a club type question too - not sure. There were a few solutions suggested, so maybe if you can find that one, the answer may make sense. I didn't stick the answer in the part of my brain that keeps that kind of material, because I couldn't imagine the need for me to do it.

So I guess two days isn't really that long over the weekend when many people are not around.

I'd seriously consider just giving them a ring tomorrow before giving up so easily!

[Richard CSL]

Thanks for your reply Paul. I will give them a ring.

By the way the purpose is that if you leave a disc jocky to control lights, they forget, so the lights do the same thing all night.
the reasoning is an automated scrolling of cuestacks in the absence of DJ input.

Mostly all dj's want to do is turn the strobes on , which will incidently only run for 5 secs max, ( then they will have to press the button again)

[paulears]

I get the point - the only problem is timing. I'd have thought long cue stacks just end up being random events - whereas having lots of 'looks that do something' on each exec button repeating allows you to have fasts/slows/blus/res/strobes etc in columns - each a different version allows them to stab the button in time with music changes. If they want totally unattended operation then a 6 hour cue stack would work and be very boring and separate - the alternative would be giving them lots of easy to operate looks operated manually? The ones I have seen tend to be fully auto - for idiots, and smaller, tighter stuff for DJs who understand lighting?

[Richard CSL]

I was always intending to give all the individual looks with limited time runs and full control, but in case a change has not happened in say 5 mins the cue stacks could automatically revert to say 2min run then activate the next stack, or each stack could run for a time then change gobo or colour.
This is why I am asking for tips from somebody who actually has installed MQ in a club. To see how they got round the "DJ" problem.

[paulears]

To be very honest - the one I installed in a club a couple of weeks ago had the exec screen modified severely because of the need for really non-technical staff needing to be able to use it. In the end, I had to try to use very descriptive language - fast yellow swirls - strobing gobos - left-right fast, because the non-technical people were getting so confused. I quite like your idea of using a kind of timeout - so if no button prods received, change to a different cue and start the timing again? I'm not sure how to do that - the previous posts suggested macros, but I was confused. I'm certain Magicq will respond to your request and be able to tell you how to programme it.

[darossld]

Hi,
One way to do this is to create a large stack of cues, different disco effects, etc... Separate the cues from the stack so each one is an individual executer button - each look can be selected on a button by an interested individual - on each executer button cue you also put a second follow on cue that after perhaps 2 minutes triggers a macro that jumps back to the initial cue stack, effectively taking over if no-one hits an executer. If someone is controlling it then as long as they hit a button within 2 minutes they will retain control, or can jump in at any time if you add a release macro to disable the cue stack.
If you have timing on the cue stack then it will begin to step through the stack until an executer is selected which then can then release the stack and take over. If the stack is changed to a chase and has a very low bpm then you can use the random function to vary the order of the looks throughout the night.. or you could trigger several stacks, one for movement, one for gobo, etc. each with different fade/delay times to give you a completely random show if no-one is controlling it...
If you want to leave one look up you can just pause the stack/chase, or have a executer that doesn't have the second 'takeover' cue and therefore will remain active until someone turns it off or overrides it.

D

This post has been edited by darossld: 12 August 2012 - 05:32 PM