Bug 373406 - Timeline position indicator and other features not working in new update
Summary: Timeline position indicator and other features not working in new update
Status: RESOLVED WORKSFORME
Alias: None
Product: kdenlive
Classification: Applications
Component: User Interface & Miscellaneous (show other bugs)
Version: 16.08.2
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Jean-Baptiste Mardelle
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-12-08 01:42 UTC by Kokoro
Modified: 2019-01-02 12:39 UTC (History)
2 users (show)

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


Attachments
screen shot (85.94 KB, image/png)
2016-12-08 01:42 UTC, Kokoro
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Kokoro 2016-12-08 01:42:50 UTC
Created attachment 102680 [details]
screen shot

Hello, I am having problems with the new update of Kdenlive when ever I try to use it.
The problems are: The Timeline position indicator does not move at all. It just stays at the beginning of the timeline. When I try to move it, a gray line shows where it is supposed to be, but the timeline position indicator does not move to that spot. Also when ever I try to separate sound from video, the sound does not go away. Only the sound wave symbol goes away from the video clip. Also where do I find the zoom in and out guide features that used to show on the right side of the video clip monitor?  

I really hope this gets resolved soon because I need to finish up some projects with this program.  

Thank you very much!

I also uploaded a screen shot to show what is going on.
Comment 1 Wegwerf 2016-12-10 10:35:47 UTC
Number of processing threads set to 1?
Comment 2 Kokoro 2016-12-11 06:33:14 UTC
(In reply to Wegwerf from comment #1)
> Number of processing threads set to 1?

Oh I'm sorry, I don't know what that is. Where can I find that in the program?
If I change the processing threads to one, would that fix it?
Comment 3 emohr 2019-01-02 12:39:05 UTC
It seems the problem is solved. We closed this bug. If it still appears in the latest version, please feel free to re-open it and update the affected version number.