I am having this issue where I add a 30 fps video clip to the project bin and kdenlive thinks it’s a 1.67 fps video and wants to change the video profile to 2 fps (because apparently 1.67 fps is non-standard frame rate). In addition to that, it plays and renders the aforementioned video clip as if it really was a 1.67 fps video. I’ve been trying different combinations of settings to try and find a workaround for this problem to no avail. So far trying proxy clips proved to fix the problem during timeline playback but it comes back in the rendered file. It only happens with timelapse videos where you record for a very long duration but the result is a very fast moving (like 10x) short video. I have used the very same clips in previous versions with no such problems.
I also tried clip properties by trying to change the frame rate to 30 fps but it either concludes with kdenlive crashing or the clip becomes a completely white color clip.
Note: VLC and SMPlayer play the video with normal frame rate i.e. with no frame loss.
I feel like the problem is where kdenlive gets metadata from. Any ideas how to fix it?
I have an amd radeon rx 6600 gpu and intel if 10400f cpu with 32gb ram
I noticed yesterday, after I opened this post, that other video editing software showing the same behavior (shotcut and flowblade) but not openshot. Is it maybe because these 3 use the same framework? if the problem underlying this behavior stems from the MLT framework, I shall open a bug report regarding libmlt++7 package, am i getting it right?
I can click on it to change the value but it’s not the point. I can see the result during timeline playback and on the rendered file itself. It’s decreasing a 30 fps video clip to a mere one frame-per-second video clip, this is how. I’m here to understand why and try to fix or find a workaround.
i cannot reproduce your issue. Sure Kdenlive can have a reduced playback if you are not using proxies or lowering the preview resolution but that does not affect the rendered result… Can you share more info about the lowered fps in the rendered result?
sure, I can give all the details required but I don’t know what details are needed. I can record my desktop then upload it to youtube to show you what I’m experiencing. Maybe that will help?
Note: as I mentioned above, it only happens with videos recorded using timelapse mode. No problem with bigger resolution and bigger size videos.
distro - kde neon - most recent
kdenlive flathub and ubuntu repos installation - both the same result along with shotcut and flowblade.
of course. I’ll record an extensive session for about a minute to show the kdenlive playback, render result and the original clips playback on VLC and SMPlayer.
ok I uploaded it to youtube and made it unlisted meaning only people with the link can see it. The problem is I couldn’t post it here in the message and I couldn’t figure out how to send a DM so I added it to my profile under “website” section.
Can you look at it and confirm that you can see it?
Just to be sure: I would like to have the video source (the time-lap recording) to check the fps discrepancies, not a recording of your editing session
But I understand if it is sensitive material that you don’t want others to see …
It’s not sensitive at all, I’m trying to create an intro clip for my youtube channel to step up the game but sadly, it appears, mlt isn’t letting me to do so.
It’s on my profile again.
google drive link contains 3 of the video clips as sample files.
Ok, I can confirm that playing the video outside of Kdenlive shows the timelaps as intended. Playing it in the clip or project monitor in a 30-fps project shows it like a slideshow
So, Kdenlive doesn’t see this as a 30fps clip but takes the real frame rate for playback.
Exactly. So you could reproduce the situation. The problem is where the mlt is getting the metadata from or how it interprets it. It was never the case before. I used the very same video clips on kdenlive last year and it all went as expected.
I’m kind of relieved that it is not my distro or hardware. Thank you berndmj and frdbr
update: I tried timelapse recording with my current phone and it is working as expected with new clips. I think it would be impossible to reproduce this for devs using other videoclips that were recorded with timelapse mode on their devices. Thus, I’m not opening a bug report. Instead, I’m converting those footage to mp4 as a workaround. This way the converted videos do work as intended on kdenlive. Kdenlive will want to transcode them again anyway but hey! I can work with this at least.
Just for future reference, and possibly testing, what device are you creating these on?
And could you please create a bug report anyway and attach a short example video showing the problem that you are ok with publicly sharing for testing purposes.
If some commercial hardware is producing busted metadata, that should probably be reported to them, and we should probably determine whether they really are using it wrong, or if we are wrongly ascribing meaning to some ancilliary field they stored the original capture frame rate in.
If it happened to you, it will happen to others - so it’s great that you found a workaround, but if these files are being created and are out in the wild, we should properly understand them and decide what to do about them.
those files are created by a chinese android phone. Branded Casper, a Turkish company. Model via a3 plus. I doubt many are still around but I’ll open a bug report regarding the issue. I believe the same company makes some of the Blu phone models -a US brand-. This one for example, is exactly the same with my casper one which created problematic frame rate videos. (which again, didn’t cause any problems mere months ago with older versions of the mlt framework and kdenlive)
