Bug 363032 - git master: volume effect looses its setting when applied to track
Summary: git master: volume effect looses its setting when applied to track
Status: RESOLVED FIXED
Alias: None
Product: kdenlive
Classification: Applications
Component: Effects & Transitions (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Vincent PINON
URL:
Keywords:
: 357053 (view as bug list)
Depends on:
Blocks:
 
Reported: 2016-05-13 15:57 UTC by Wegwerf
Modified: 2016-08-24 13:34 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Wegwerf 2016-05-13 15:57:21 UTC
When applying the volume (keyframable) effect to a track its properties are not recalled when reselecting the track header but instead always reset to 0db. 

Reproducible: Always

Steps to Reproduce:
1. Create new Kdenlive project with at least one audio track.
2. Add volume effect to audio track.
3. Set volume effect to -10db.
4. Select something else/another track/clip.
5. Select audio track header again.

Actual Results:  
Volume effect is reset to 0db.

Expected Results:  
Volume effect should retain its -10db setting.
Comment 1 Riskable 2016-05-22 20:01:24 UTC
I am also having this exact problem.  Super easy to reproduce...  Just try using the keyframe feature on the volume effect to add a bunch of keyframes and then move them around after re-selecting the track.  It'll get screwed up every time.

Also, not sure if this is related but you used to be able to grab little handles on the track itself to control the volume of keyframes (each keyframe got a handle).  That seems to be missing in the latest development version as of 5/22/2016.
Comment 2 farid 2016-08-10 14:39:51 UTC
I reproduce using today's build.
Comment 3 Vincent PINON 2016-08-20 20:42:15 UTC
Any keyframable effect actually fails as track effect...
Comment 4 Vincent PINON 2016-08-20 21:03:03 UTC
*** Bug 357053 has been marked as a duplicate of this bug. ***
Comment 5 Wegwerf 2016-08-23 15:41:12 UTC
This is fixed now with the recent git master; thank you very much for fixing this, Vincent!
Comment 6 Vincent PINON 2016-08-24 00:20:56 UTC
JB deserves the thanks, as usual :)
We should rename our app to JBNLIVE...
Comment 7 Wegwerf 2016-08-24 06:07:48 UTC
:D
Comment 8 farid 2016-08-24 13:34:14 UTC
(In reply to Vincent PINON from comment #6)
> JB deserves the thanks, as usual :)
> We should rename our app to JBNLIVE...

+1 :D