Kdenlive 20.12.0 AppImage with Ubuntu 18.04

I added two videos and an MP3 audio to a project, added some transformations, added fade in's / fade out's, added two texts, cut the videos and moved the needed parts, changed the speed of the second video. When I was happy with the result in the preview monitor I rendered it. I viewed the rendered video and, shocking, Kdenlive used the wrong part of the second video. Let's say the source video is 10 minutes long, I used 04:00 - 05:00, in the preview I see 04:00 - 05:00, but when I render the video shows something like 07:12 - 08:12.

I've got no clue what's going on there and how I can repair this project without starting from scratch. Any help appreciated.

Nobody?

What could be the reason for rendering something different than the preview?

Some questions (trying to figure out what the problem could be):

1. after importing clips, how did you cut them ? I mean, with the clip monitor (setting in/out points) or directly in the timeline ?
2. did you previewed the timeline with the correct monitor (the project monitor, not the clip monitor) ?
3. did you set some IN/OUT points in the timeline ?

(If you set some in/out points in the timeline, you can render a partial and specific part of your project, not the whole timeline.. if enabling an option while setting the render parameters before exporting )

hgdrn wrote:Kdenlive 20.12.0 AppImage with Ubuntu 18.04
Kdenlive used the wrong part of the second video. Let's say the source video is 10 minutes long, I used 04:00 - 05:00, in the preview I see 04:00 - 05:00, but when I render the video shows something like 07:12 - 08:12.

this can be a bug.. but with only "words" can't try to reproduce (and maybe fix)...
the 2nd clip you are talking is placed on timeline from project bin? .. it has a speed change and cuts a the same time? is taken from a previously cutted video on timeline?

if you can reproduce the issue.. please make a video (to share) about this grabbing the screen... just to understand every change you made to clip.

kryxkave wrote:1. after importing clips, how did you cut them ? I mean, with the clip monitor (setting in/out points) or directly in the timeline ?
2. did you previewed the timeline with the correct monitor (the project monitor, not the clip monitor) ?
3. did you set some IN/OUT points in the timeline ?

(If you set some in/out points in the timeline, you can render a partial and specific part of your project, not the whole timeline.. if enabling an option while setting the render parameters before exporting )

I used the workflow I have been using all the time, and I've rendered some hundred videos until today. This is the reason why I don't understand what has gone wrong here.

1. Videos were added to the project, then dragged to the timeline on two different tracks one after the other. Videos were cut in the timeline by moving the pointer and pressing Shift-R and deleting the unneeded parts.
2. I only use the project monitor
3. No, I don't think so, no IN/OUT points in the timeline, but I will check that.

In fact, there were a lot of steps with adding and removing effects until the result was closest to that I was hoping to create. I want to show two videos with split screen, both recorded with a bike dash cam, where one can see the differences from two years ago to today. Because I didn't cycled the exact same speed I need to adjust the speed of one video.

In former Kdenlive versions I've often experienced problems with fade in's or fade out's at wrong positions after having added/removed them quite often. The project file then had a lot of internal **** I didn't see in the timeline but created these problems in the rendered video. But since Kdenlive 19 or so these problems were gone.

Thus, I think due to the numerous steps of adding effects, removing them, adding other effects, changing the parameters, removing them again (.... repeat dozens of times) there is now something wrong with the project file that produces these problems. But that is just a guess.

bartoloni wrote:this can be a bug.. but with only "words" can't try to reproduce (and maybe fix)...

Thanks for your answer. Yes, it's quite complicated to describe it with words. I hoped that this might be a common problem and someone just answered "Yeah, common problem, just click here and click there, restart and everything will be fine".

bartoloni wrote:the 2nd clip you are talking is placed on timeline from project bin? .. it has a speed change and cuts a the same time? is taken from a previously cutted video on timeline?

if you can reproduce the issue.. please make a video (to share) about this grabbing the screen... just to understand every change you made to clip.

I will make some screenshots, grab the screen with the previewed video and the result and upload everything to YouTube this weekend. Please stand by.

hgdrn wrote:Kdenlive 20.12.0 AppImage with Ubuntu 18.04.

I noticed you're not using the last version of KDENLive.. is there a specific reason for that ?

Anyway... I recalled just now I had a similar problem in Windows, but it was with a quite old version of KDENLive, at the beginning of 2020, I think.. surely previous to 20.12.x.

For this reason at the time I was sadly forced to switch to Shotcut for some editings.. how painful has it been.
But with the next update, luckily, everything was fixed.. and I returned immediately to use KDENLive.

kryxkave wrote:

hgdrn wrote:Kdenlive 20.12.0 AppImage with Ubuntu 18.04.

I noticed you're not using the last version of KDENLive...

That#s correct, 20.12.2 fixed it, rendered video is OK. Problem solved.

hello, i appear to be having the same issues in the most recent update, im editing an hour long piece of footage, cuting on timeline with the cutting tool, moving it back to the beginning from the centre then when i render the cut product its rendering the beginning of the cut 1 hour video, im at a loss, i have parallel processing off in render as it caused issues previously, ive reinstalled it fresh and its not fixed it, no clue, so some help would be nice if anyones feeling generious

I had a similar issue, in my case it turned out the export frame rate didn't match the frame rate of my clips.