Bug 416507 - Gain when applied to audio, stays at 0%. If I change it to 20% click away from track and click back it is again at 0%.
Summary: Gain when applied to audio, stays at 0%. If I change it to 20% click away fro...
Status: RESOLVED FIXED
Alias: None
Product: kdenlive
Classification: Applications
Component: Video Effects & Transitions (other bugs)
Version First Reported In: 19.12.1
Platform: Microsoft Windows Microsoft Windows
: NOR critical
Target Milestone: ---
Assignee: Vincent PINON
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-01-20 18:49 UTC by MikeNewman
Modified: 2021-02-14 22:00 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:
fritzibaby: timeline_corruption+

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description MikeNewman 2020-01-20 18:49:47 UTC 
SUMMARY


STEPS TO REPRODUCE
1. apply gain to audio eg.20%
2. click other track
3. click again on audio (gain gets back to 0%

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 MikeNewman 2020-01-23 18:13:06 UTC 
I noticed that when I open kdenlive, I can see values on gain effect but after a while, after few clicks, value is again to 0%. And when I close app and open it again, the value is visible
Comment 2 emohr 2020-01-26 18:38:18 UTC 
I followed your steps. I cannot reproduce. The gain stay at 20% even after clicking other tracks and changes some value of other effects and come back to the audio with the gain effect. Still 20%. 

Please delete the kdenliverc file and try again see here: https://userbase.kde.org/Kdenlive/Manual/Windows_Issues#Cannot_open_projects_made_with_previous_version.2C_timeline_snaps_back.2C_cannot_import_clip
Comment 3 MikeNewman 2020-01-27 10:31:12 UTC 
I tried today and gain percentage was all the time visible and didn't change. I am not an expert but I think this could be connected with graphic driver - Intel® HD Graphics 620 - I think it was updated during this time. Could it be that this was a cause?