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
    [quote=robbie_bruce;43921]After much deliberation, we have decided using the next cue's "out" time does provide the most flexibility.

    do you imply that the out time will be constructed by your educator? i would be glad for that to be the case.


    i'd like for my understanding of the actual operations of the educator to be confirmed or corrected:
    [INDENT]for each Lkel, Timing will begin as default. upon commencing a merge/release/etc., if Timing has not been explicitly set and still remains as default, Timing will be replaced to satisfaction, specific to the target of the operation.

    for each individual FadeDelayPath, each individual Time element will be derived over several iterations of a statistical sampling of a domain or subset of similarly-purposed Time elements already existing in the operation's target.

    the iterations are recursive. a return of multiple values will continue; a return of zero values will signal the final sampling set. a return of a single value will be considered deterministic and cause escape.

    recursing will be in order of Cue -> Kind -> Function -> Feature -> Type.

    how will the value be derived from the final sampling set? the minimum/maximum/average/mean of the entire set? something more complex, such as the average of the two nearest UserNum's?
    [/INDENT]


    as for path:
    [INDENT]i think whether or not path education should be optional is a much more interesting question to pose. as an individual, i would be completely pleased with path education in the case of Linear defaulted features. in the case of non-Linear defaulted Features, i would like education to be applied, but only when the target already contains the same Feature for the same Type.


    also, the case of a cue-only release gives me pause. can the scope of this change request be expanded to the playback area? specifically, i think it would be wise to signal that the InterpolationTable is to be applied in reverse.
    [/INDENT]
Reply
  • 0
    [quote=robbie_bruce;43921]After much deliberation, we have decided using the next cue's "out" time does provide the most flexibility.

    do you imply that the out time will be constructed by your educator? i would be glad for that to be the case.


    i'd like for my understanding of the actual operations of the educator to be confirmed or corrected:
    [INDENT]for each Lkel, Timing will begin as default. upon commencing a merge/release/etc., if Timing has not been explicitly set and still remains as default, Timing will be replaced to satisfaction, specific to the target of the operation.

    for each individual FadeDelayPath, each individual Time element will be derived over several iterations of a statistical sampling of a domain or subset of similarly-purposed Time elements already existing in the operation's target.

    the iterations are recursive. a return of multiple values will continue; a return of zero values will signal the final sampling set. a return of a single value will be considered deterministic and cause escape.

    recursing will be in order of Cue -> Kind -> Function -> Feature -> Type.

    how will the value be derived from the final sampling set? the minimum/maximum/average/mean of the entire set? something more complex, such as the average of the two nearest UserNum's?
    [/INDENT]


    as for path:
    [INDENT]i think whether or not path education should be optional is a much more interesting question to pose. as an individual, i would be completely pleased with path education in the case of Linear defaulted features. in the case of non-Linear defaulted Features, i would like education to be applied, but only when the target already contains the same Feature for the same Type.


    also, the case of a cue-only release gives me pause. can the scope of this change request be expanded to the playback area? specifically, i think it would be wise to signal that the InterpolationTable is to be applied in reverse.
    [/INDENT]
Children
No Data
Related

www.etcconnect.com