Options
Related

Copy troubles

Hi,
I will perform a training as trainer in the beginning of November so I revise my classics and more specifically the functions which I do not use every day. I found a trouble when I try to copy parameters from a fixture to an other with mask in a specific destination. I tried 3 commands:
Fixture 1 Thru 4 Copy 8 Thru 11, Enter
1 ) 1 Thru 4 Intensity Copy List 3 Cue 1 Fixture 8 Thru 11, Enter (the one that is in the manual page 157)
2 ) 1 Intensity Copy List 3 Cue 1 Fixture 8 Enter
3 ) List 1 Cue 2 fixture 1 Position Copy List 3 Cue 1 Fixture 5 Enter

Every times it's the fixture from source that is stored in the cue instead of the one of destination.
1 ) In Cue 1 of List 3 I have the fixtures 1 Thru 4 instead of 8 Thru 11
2 ) In Cue 1 of List 3 I have the fixture 1 of fixture 8
3 ) In Cue 2 of List 1 I have the fixture 1 instead of Fixture 5

Am I doing something wrong or is there a trouble in the software?

Thanks
Stephane
Parents
  • 0
    I'll start with Steph's first post because I think I've got that understood now and I have logged as a solid issue that I can show to development.

    In these cases the failure is occurring because the syntax involves taking data from fixture 1 in location A and giving it to fixture 2 in location B. The source and destination are understood by the console in broad terms as location A and location B but the more detailed part of the destination which is the fixture destination is lost. Here is a re-post and summary as I have written it into our bug logging system:


    [1] [Thru] [4] [Intensity] [Copy] [List] [3] [Cue] [1] [Fixture] [8] [Thru] [11] [Enter]

    This syntax results in List 3 cue 1 getting data for fixtures 1 Thru 4 instead of 8 Thru 11



    [1] [Intensity] [Copy] [List] [3] [Cue] [1] [Fixture] [8] [Enter]

    This syntax results in List 3 cue 1 getting data for fixture 1 and instead of fixture 8



    [List] [1] [Cue] [2] [Fixture] [1] [Position] [Copy] [List] [3] [Cue] [1] [Fixture] [5] [Enter]

    This syntax results in List 1 cue 2 getting fixture 1 instead of Fixture 5


    So to summarize, when a source and/or destination contain two pieces of data (such as fixtures in a palette or groups in a cue) we tend to mess up the secondary details of the destination (the fixtures and/or the groups). Now, its not clear whether the console logic demands the larger part of the source and/or destination to come first in the syntax but I think its actually interchangeable.... just broken. More to come!
Reply
  • 0
    I'll start with Steph's first post because I think I've got that understood now and I have logged as a solid issue that I can show to development.

    In these cases the failure is occurring because the syntax involves taking data from fixture 1 in location A and giving it to fixture 2 in location B. The source and destination are understood by the console in broad terms as location A and location B but the more detailed part of the destination which is the fixture destination is lost. Here is a re-post and summary as I have written it into our bug logging system:


    [1] [Thru] [4] [Intensity] [Copy] [List] [3] [Cue] [1] [Fixture] [8] [Thru] [11] [Enter]

    This syntax results in List 3 cue 1 getting data for fixtures 1 Thru 4 instead of 8 Thru 11



    [1] [Intensity] [Copy] [List] [3] [Cue] [1] [Fixture] [8] [Enter]

    This syntax results in List 3 cue 1 getting data for fixture 1 and instead of fixture 8



    [List] [1] [Cue] [2] [Fixture] [1] [Position] [Copy] [List] [3] [Cue] [1] [Fixture] [5] [Enter]

    This syntax results in List 1 cue 2 getting fixture 1 instead of Fixture 5


    So to summarize, when a source and/or destination contain two pieces of data (such as fixtures in a palette or groups in a cue) we tend to mess up the secondary details of the destination (the fixtures and/or the groups). Now, its not clear whether the console logic demands the larger part of the source and/or destination to come first in the syntax but I think its actually interchangeable.... just broken. More to come!
Children
No Data

www.etcconnect.com