Filed Double-clicking FX parameters doesn't always reset them to the values saved as a snapshot

Discussion in 'Archive' started by ErikMinekus, Apr 21, 2018.

  1. ErikMinekus

    ErikMinekus NI Product Owner

    Messages:
    578
    Version and Setup:
    Traktor Scratch Pro 2.11.3.12
    macOS High Sierra 10.13.4

    BUG 1

    Reproduction Steps:
    1. Change the FX parameters in FX unit 1 and save them as a snapshot
    2. Restart Traktor
    3. Double-click on the FX parameters in FX unit 1 to reset them to the saved value
    Observed Results:
    The FX parameters in FX unit 1 will reset to a different value than what was previously saved as a snapshot. Only after clicking the RST button (when in Single Mode), or switching to a different effect and back, will the values correctly reset when double-clicking.

    Expected Results
    :

    The FX parameters should reset to what was saved as a snapshot.​

    BUG 2


    Reproduction Steps:
    1. Change the FX parameters in FX unit 1 and save them as a snapshot
    2. Switch to a different effect in FX unit 2
    3. Double-click on the FX parameters in FX unit 1 to reset them to the saved value
    Observed Results:
    The FX parameters in FX unit 1 will reset to the same values as those of FX unit 2. Only after clicking the RST button (when in Single Mode), or switching to a different effect and back, will the values correctly reset when double-clicking.

    It doesn't matter if the FX units are in Group Mode or Single Mode, any time you switch to a different effect in one FX unit, the default values of all the other FX units will reset to those of the effect you just changed.

    Expected Results:

    The FX parameters should reset to what was saved as a snapshot.​
     
    Last edited: Apr 21, 2018
    • Like Like x 1
  2. Friedemann @ NI

    Friedemann @ NI NI Team NI Team

    Messages:
    812
    Awesome bug description!! We could instantly reproduce it and will be able to copy this into our bug tracking system with zero effort.

    All others: please learn form this bug report!
    It has been filed as TP-12585

    Thanks
     
    • Like Like x 3