Preses fade + cue fade

BECOME PART OF THE COMMUNITY - Sign up here
  • Hi!


    I select a group of fixtures and create a dimmer preset with value 100 and a delay time 1.

    If i then use this preset to create a Cue in a sequence and add a delay 1 to that cue, the total delay time should be 2 before the dimmer turns on? But it doesn't, the delay time on the cue in the sequence is ignored.


    Is this working as intended?

  • No thats not how MA works (how you’re thinking).


    You should think of the Cue Delay time as a ‘generic’ delay that’s used if nothing else is specified.
    Adding Delay to the individual fixture parameter overrides the generic cue delay value.
    Its one or the other, not cumulative.

  • No thats not how MA works (how you’re thinking).


    You should think of the Cue Delay time as a ‘generic’ delay that’s used if nothing else is specified.
    Adding Delay to the individual fixture parameter overrides the generic cue delay value.
    Its one or the other, not cumulative.

    Ah thanks!


    But here is another one for you.

    Preset 1: Dimmer 100, fade 0.5, delay 0 thru 1

    Preset 2: Dimmer 0, fade 0.5, delay 0 thru 1


    When I select my fixturens and press preset 1, they are fading up as expected, but when I then press preset 2 they are all shut down immidiately with 0 fade and 0 delay.


    When I store them in a sequence with preset 1 in cue 1 and preset 2 in cue 2 they are working as expected.


    Why are the fade and delay times not included when i select my fixtures and then preset 1 and after that preset 2? It would be handy to not having to store them into sequences just to have a look at preset 2.

  • Hi Henk,

    your description is a known bug currently.


    The problem is that fixtures snap to their default values in the programmer before they use the individual timing.

    That´s the reason why preset 1 with 100% looks good in the programmer and preset 2 not. The fixtures snap to 0 (which is the default) and then use the individual timing - but then you can not see anything.


    This bug will be solved in one of the next versions.

  • Hi guys! I have a related issue. When using ind.fade on some fixtures (maybe delay to but I haven’t checked), when I change values on those fixtures for my next look the fade layer automatically gets activated. If I forget to adress that, the next cue will get the same ind.fade values as the cue before.
    I suppose that’s a bug?


    And also related to that; when I’m in an active cue with ind.fade in it, then programmer time does not work. Actually the individual fade values gets forced to become a ”programmer time” of sorts, when I change the values on the attributes that where using that particular ind.fade time.


    You probably know of these bugs allready, but I still wanted to adress them. There quite problematic.

  • Hey mlogdstrom,


    you are right, this behaviour will change. At the moment the individual timings are grabbed and you have to switch them off automatically. But we are working on it.

  • Hey mlogdstrom,


    you are right, this behaviour will change. At the moment the individual timings are grabbed and you have to switch them off automatically. But we are working on it.

    Wunderbar?

  • "Wunderbar" wasn´t suppose to have a questionmark after it, sorry:)

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!