• State Verified Answer
  • +1 person also asked this people also asked this
  • Date
    Daire Cavanagh
  • Date
  • Replies 2 replies
  • Subscribers 187 subscribers
  • Views 49 views
  • Users 0 members are here

Bug: Curves affecting given Intensity in Subs and Cues

We have encountered a bug where by applying a curve to a Channel in patch will change the Intensity value in the Sub.

This is a custom multi-cell fixture with cells being CW/WW/Blue and the master being a Virtual Master Dimmer.

We have also applied this to normal dimmer profile and we have the same result.

The same behaviour is also seen in Cues.

Software version: V.3.3.3 Build 10

Hardware: Apex 10

The showfile has been sent to eos(dot)moderator(at)etcconnect(dot)com from stellwerk(at)opernhaus(dot)ch

The Channel numbers we tested it with are Ch. 711 and 1084. Seen in Cue 1/5 + 101.5 + 102 and Sub 8

Parents
  • +1

    We had a look at your showfile, and this is currently expected behaviour. There was a change in 3.3.0 to make Eos maintain resulting DMX output upon changing a channel's curve if {Preserve Native} is enabled.

    The {Preserve Native} function in Patch is meant to maintain outputs of already recorded data even after patch changes. When patch changes are made after preserve native is enabled, DMX output levels should not change in recorded data. In turn the stored values in palettes, cues, etc. change to still output the same DMX level.

    Before 3.3.0 this applied to patch changes like when changing a channel's fixture type, in 3.3.0 the same logic was extended to also affect changes caused by a curve change.

    Does this help explaining what you're seeing?

Reply
  • +1

    We had a look at your showfile, and this is currently expected behaviour. There was a change in 3.3.0 to make Eos maintain resulting DMX output upon changing a channel's curve if {Preserve Native} is enabled.

    The {Preserve Native} function in Patch is meant to maintain outputs of already recorded data even after patch changes. When patch changes are made after preserve native is enabled, DMX output levels should not change in recorded data. In turn the stored values in palettes, cues, etc. change to still output the same DMX level.

    Before 3.3.0 this applied to patch changes like when changing a channel's fixture type, in 3.3.0 the same logic was extended to also affect changes caused by a curve change.

    Does this help explaining what you're seeing?

Children
No Data
Related

www.etcconnect.com