Bug: LTP overrites Fadings, new value isnt stored as LTP

[LiWi]

when I change a dimming-value manually it is set as new value unsing LTP as it should.
If I start a fading-process (new Scene) on that channel, the value is faded properly, but after the fade-in of the Scene the value jumps back to the last manual value instead of keeping the dimming-value as new LTP.

Therefore you cant adjust any value while the Show is running without ruining the whole further Show!
Adjusting a single channel within a running Show can result in immediate Brightness-Changes from 0 to 100% later in the show, that blind everyone if you dimmed that channel manually (we are using 10 kW LED Power)...

[TomHat]

Hello,

Sorry to read you're experiencing issues using our software... Which version of Daslight4 are you using ?

Regards,

[LiWi]

Which version of Daslight4 are you using ?

Aug 02 2018 (18.802.8699.1345)
1.9.1-24139-SVN:36877-(Jul 12 2018)

[TomHat]

Right... I'm sorry I haven't been able to reproduce your problem. Could you please send me your showfile along with an explanation on how to reproduce the problem ?

Thanks in advance, and sorry for the delay.

Regards,

[LiWi]

It seems that different midi-mappings corrupted the dvc-file, because after deleting and reassigning all midi-controls of the same file the Problem is now different:
Now there are no jumpbacks, but the manual value is not overwritten by a newly selected preset. The Manual midi-value has the effect as it is used as a htp-value. This means you have to completely pull down all changed faders to make preset-changes take effect. If you rise them again you have an immediate brightness-jump because your LTP-Midi-value starts at 0.

i cant upload files because the board tells me .dvc is an invalid Extension. also .zip does not work.

[TomHat]

Hello,

Then please send your showfile directly to [email protected]

Regards,