https://bugs.kde.org/show_bug.cgi?id=498682

--- Comment #2 from yyy5566778...@126.com ---
(In reply to emohr from comment #1)
> When following your steps I get the correct length presenting by the timer.
> After speed-up by 150% I get a clip length in my case of 6.38 (down from
> 9.58 origin length). The timeline preview monitor as the final rendered file
> shows 6.38 which is correct. This is how the timer is working.
> 
> I guess you still want that the timer shows original length of the clip
> (9.58). You can do that with an additional sequence:
> -     Create a second sequence2
> -     Put the clip in sequence2
> -     Put the sequence2 into sequence1
> -     On the imported sequence2 -> right click -> enable “Time Remap”
> -     On the “Time Remap” tab adjust the speed
> Now the counter keeps the length of 9.58 even on the rendered file.
> 
> Is it that what you like to achieve?

Yes. I used an additional sequence to achieve this. 
And found another problem that after I speed change the 'sequence' clip in
timeline, and video in that timeline has active proxy clips, they will be used
instead of the original clip for exporting, causing low quality sections in the
rendered video. 

I think effects applied to clips in project bin should be treated as the
effects are rendered into the clip before putting to the timeline, so any
changes applied in timeline , including speed changes, should have effect on
them. 
Showing time after the speed change makes sense when timer is applied in
timeline, but makes no sense when timer is applied in the project bin.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to