Program Time Filter

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

    Is there a way to make a program time filter?

    I would like to have all my pan+tilt movements with 2 sec time while working with the programmer, but I still want to have 0 time using color, dimmer, etc.

    On a theater/dance environment it's always a good practice to make smooth position movements while programming...


    I was wondering if I could do this without continuously using macros...

    Maybe on user settings? Maybe on Fixture Types menu? Maybe parking individual times? ...

    I've tryed some stuff, but still didn't find an answer.

    Help is appreciated.


    Thanks in advance

  • Off the top of my head, I'd make a Sequence where you store Rel Pan/Tilt values of 0 and then Fade Pan/Tilt of your desired time.


    Then edit the settings of the sequence to:

    Playback>Priority = Super

    Protect> Off when Overridden = Off


    Then Go+ the Sequence. Now all of the stored fixtures will have the fade time of your liking with 0 Rel Offset.


    At the moment you are required to store either Absolute and/or Relative values so that's why we set Rel to 0. This would probably break things if you are using Relative values already.


    The drawback here is because the Priority is set to Super, it's above the Programmer and all playbacks, so you have to be careful what you store in that sequence. Also, you could easily capture the FadeTime or Relative values by accident (Please Please)


    I'm, sure there is another way but that's probably what I'd do if I was not using Relative values.

  • Thank you, hoss

    I will sure try your super priority sequence solution.


    I tryed numerous times, but can't find the way to store relative pan/tilt values and fade times on the default preset (I am using it all the times to have a home position, color, beam, etc). It was my first guess.

    Although I would need a macro to keep cleaning the stored relative and fade times, I thought it would easily work...

  • Using the default is a good idea but it seems all the Store Default keeps is the Absolute value stored in the preset and applies it to the Default entry of the selected fixture in the patch. So fade and relative get thrown away.


    Maybe in the future default will include more feature groups.


    Along those lines, another ,way less flexible and heavy handed approach would be to change the fixture types DMX Change Time Limit value. The issue here is it would be Global to the fixture type and I have no idea who you would macro it; somewhere deep in cd root 13.9.5 and I'm sure this has the potential to break things if you aren't careful.

  • Along those lines, another ,way less flexible and heavy handed approach would be to change the fixture types DMX Change Time Limit value. The issue here is it would be Global to the fixture type and I have no idea who you would macro it; somewhere deep in cd root 13.9.5 and I'm sure this has the potential to break things if you aren't careful.

    I will check this. It's quite a challenge, thought. :)


    I was replicating your "super priority sequence solution" and it didn't work. Probably I am be doing something wrong.

    I don't know why, but when I call a position preset (with no fade or relative values recorded) it would put the fade values of the super sequence to zero.

    It only works while writing absolute pan/tilt values.

    I checked that I only recorded the relative values (zero) and fade time in the sequence, and also checked all the settings you mentioned.

    No Freeze or any time fade connected...

    Any guesses why it doesn't work?

  • Strange it does work for me.


    To test I wrote the following:

    Group 1

    Attribute "Pan" At Relative 0

    Attribute "Tilt" At Relative 0

    Attribute "Pan" At Fade 5

    Attribute "Tilt" At Fade 5

    Store Preset 2.1 "5 Sec"

    Clearall

    Group 1 At Preset 2.1

    Store Seq 1

    Set Seq 1 Property "OffWhenOverridden" 0

    Set Seq 1 Property "Priority" 0 Sets to Super

    Clearall

    Go Seq 1 Takes 5 Seconds to "take"


    Now If I take one of my presets they happen in 5 Seconds Pan and Tilt. I just double checked with and without freeze and it works here as well.


    Here is the file I tested with.

  • Thank you so much for your time, hoss

    Unfortunately, I can't replicate it. It's like super priority isn't working.

    It seemed to be working when I used your Preset 2.2, but then I found out that it has (by mistake?) recorded relative and fade time on it.

    I assume that the idea is that a super prioritized sequence wins it all. But that's not what's going on here.


    I am using onPC on a mac. Tomorrow I'll try it on our MA3 Light console.

  • A little more futzing around to see what I did wrong and You are absolutely right. I hadn't noticed I recorded both Fade and Relative in 2.2.


    I see the issue, and I recall others having it as well.


    It seems the only way to store fade is to include an Absolute value? I tried a few times just now and I can't make it work, must have been confirmation bias.


    Either way I would have expected that would work.


    I was going to try with a lower priority sequence with an absolute value stored, but then the fade gets stomped as soon as you touch a preset with an absolute value.


    Now I need to figure out what I did to think i had it working, sorry for the wild goose chase. now I'm determined (to fail).

  • :)

    I think we both arrived at the same point. It seems that relative values are not enough to make a sequence to have super priority.

    I was wondering if there's a way to park fixture fade time, but I guess not.


    Oh well... for now I'll just keep doing as always: using a fader with program time. It works fine! ^^


    Thanks anyway!

  • Well it seems to work in 1.7. I couldn't wait and updated on onPC, read the first line in the release notes then exited the notes and loaded the fixed up test show. and lo and behold it works, I re-did the preset to include time only time (no rel) and kept the super sequence and it seems to work like you would like.


    They were watching the while time laughing at us I'm sure.


    Hmm, nevermind, kind of works, or maybe doesn't. not sure it's too nice today to figure it out though.

  • They were watching the while time laughing at us I'm sure.

    Exactly! ^^


    I downloaded the new version and just read the release notes.


    "Presets can now contain timing values only. For example, fade and/or delay. Together with this change, it is now

    possible to only call fade and/or delay times into the programmer. In cues, you cannot store timings only."


    I'll try it ASAP.