• Date
    colin wood
  • Date
  • Replies 21 replies
  • Subscribers 10 subscribers
  • Views 3030 views
  • Users 0 members are here
Options

More use of the Move command

Hello,

I would like to see the Move command have the same functionality as Copy. At present it is rather limited.

For example, I can move a cue, but only within the same list. I'd like to be able to move a cue from one list to another please.

Far more important to me though is this...

I'd like to be able to apply Fixture and Kind Masks to the Move command, just like with Copy.

For example, I decided I want fixtures 5>10 to fade out in cue 5, rather than cue 4. So...

Cue 4 Fixture 5>10 Intensity Move Cue 5. It would save so much time having to open editors and knock out parameters.

Thoughts on this anyone?
  • I kind of like this...but.

    So basically you are looking a faster way to copy to target cue and remove from the source.

    In your example I would just merge to cue 4 using remove and forward off.

    Or did I misunderstood something?
  • Very very Nice feature request. Will save me à lot of time with fixing lighting and video cue lists running on the same console. As extra functionality would be nice for programming e.g. 3part FX. Record cue 1 wich contains information for fixture 101/104/107 or group 11. Just copy the cue and move the programming to the next fixture/Group.
    Syntax would be:
    Cue 1 copy Cue 2
    Cue 2 Fixture Group 11 Move Fixture Group 12
    Group 12 will contain fixtures 102/105/108 for example.


    Another thing that would be nice is move programming in a whole list or just a part to another fixture. Syntax example:
    List 12 Cue 14 thru 24 Fixture 401 Move Fixture 403


    Would be very usefull if you need to re-arrange layers in Mediaservers...


    Greetz
  • Sami, I see your point but what if there was a Cue 4.5?

    I think a lot of flexibility could be achieved with additional move functionality.
  • In Sander's example I'm wondering what happens to the source fixtures?
    Are the values removed or replaced with default ones?
  • Well srautane, you're MOVING the values, so the source fixtures would get default values. The will be knocked out
  • Colin, I get the idea what you are looking for but we have to keep in mind how this works with tracking.
    What we are going to do to the source fixtures? Remove values or replace values with default? Do we need cue only/forward off for the source?
  • I support this request because I often find myself copying values between fixtures and then opening the cue and knocking out the source fixtures (especially using media servers...). That's why I would suggest the move function should delete the source values because replacing them with defaults would not make sense in my opinion. Also I would not save any time the other way round because I still need to knock out the sources.


    Just my two cents :)
1 2 3

www.etcconnect.com