Cue Only Timing is changing

We are looking at changing the way Cue only fade out times are being used to be more compatible with the hog2..

Hog 2 uses the current cue fade in time as the "out" time when you Go the next cue. It really never worked right for multi part timings..

Hog 3 current uses the list release time for the "out".

I think we are all in agreement that this doesn't really make a lot of sense.

We are going to change it to use the "next" cue's longest fade in time instead. This should work for most users but I want to know if changing it will require us to put another option in the list options to retain using release times for those of you who use it this way.

I would rather not clutter up this window any more than it already is and just change it.

Are there any objections to just making the change without this option?

Best regards,
Robbie
Parents
  • 0
    I do like the idea of using out times in this particular case because it makes perfect sense. However I am not sure it is intuitive as out times usually only have value when intensity is going down.

    Let me throw this out since we on the subject and it directly relates to cue only lists. In the not too distant future, we will build in timing rules for things such as merge in the case there is not an existing value rather than just tossing in the default we make some sort of educated guess.

    These rules could be also be applicable to how we fade out the existing cue in a cue only list.

    For example, using the longest fade time of a particular type.. Second order being a type and kind.. However, it may be unpredictable and requires perhaps too much thought to know what you are going to get in this case..

    In the merge example it may cover 90% of the cases which would greatly increase the likelyhood that you don't have to do a merge then follow it up with setting the timing which I agree is a big pain in the ass.

    I think out time does give the most flexibility but it does present yet one more thing to consider when merging into a cue only list..

    Just something else to consider when working with Cue Only lists..

    -Robbie
Reply
  • 0
    I do like the idea of using out times in this particular case because it makes perfect sense. However I am not sure it is intuitive as out times usually only have value when intensity is going down.

    Let me throw this out since we on the subject and it directly relates to cue only lists. In the not too distant future, we will build in timing rules for things such as merge in the case there is not an existing value rather than just tossing in the default we make some sort of educated guess.

    These rules could be also be applicable to how we fade out the existing cue in a cue only list.

    For example, using the longest fade time of a particular type.. Second order being a type and kind.. However, it may be unpredictable and requires perhaps too much thought to know what you are going to get in this case..

    In the merge example it may cover 90% of the cases which would greatly increase the likelyhood that you don't have to do a merge then follow it up with setting the timing which I agree is a big pain in the ass.

    I think out time does give the most flexibility but it does present yet one more thing to consider when merging into a cue only list..

    Just something else to consider when working with Cue Only lists..

    -Robbie
Children
No Data
Related

www.etcconnect.com