SUMMARY In Stable releases 21.08.2, 21.08.3, and Beta build 21.11.80, using the Size function on an .mts file with the Transform effect or the Position and Zoom effect will show the effect correctly in the Preview Render, but will not render the video barring the first frame when the project is fully rendered. The audio track renders as normal, it is only the video that is affected. STEPS TO REPRODUCE 1. Apply the "Transform" or the "Position and Zoom" effect to an .mts video clip. 2. Set the "Size" value to any variable. 3. Render and play back the exported video. OBSERVED RESULT The audio and any .mts video without either effect will play as intended, but the video altered with the steps above will show as blank (except for possibly 1 frame). EXPECTED RESULT The rendered video should not display as blank in an exported project, and the Size effect should be rendered as well. SOFTWARE/OS VERSIONS Windows: 10 Pro, Version 19044.1348 ADDITIONAL INFORMATION I have not noticed any other effects causing this problem, but I will update this report should I come across any. Video will be provided should repo steps not reproduce the issue.
Unable to reproduce on 21.08.3 or 22.03.70 Nightly, created myself a .mts clip by converting from .mp4 via ffmpeg and applied the size effects. Renders and displays normally as .mts or .mp4.
@paloverde7839@gmail.com Make sure in rendering -> more options -> parallel processing is disabled.
Please review the video I've linked below. The project and the rendered video were using version 21.12.0. Thank you for your patience.
https://youtu.be/gSYFRnct3RM
I tested on Windows with 21.12.0 and the master, following your steps. I cannot reproduce. What are your project settings and what are the clip details (1080p 29.97fps? Please upload your project file here so we can further check.
I have linked a .zip file containing 3 files: "mts Zoom Render Failure Example Clip.mts" (the input video), "mts Zoom Render Failure Example.kdenlive", and "mts Zoom Render Failure Example.mp4" (the output video). The project file is not the same as the one in the YouTube video (that was a temporary project), but I've included the rendered version of it, which was done with the same settings as the one in that video. The project and output video include 3 examples: Translate, Position & Zoom, and Zoom Pan (which seems unafflicted by this issue). I have been working with files from the same camera in projects with the same settings at 60 and 30fps, and they all are suffering the same issue, even though some of the edits were not producing the issue months ago on previous kdenlive versions. Due to privacy concerns, I will not be uploading those. Interestingly, Windows 10 reports the clip as 1080p 29.97fps, but says the same thing for every clip recorded by the aforementioned camera, even though the framerates are clearly higher on playback. The included project's settings on my end are as follows: Frame size: 1920 x 1080 (16:9) Frame rate: 60 fps Pixel Aspect Ratio: 1 Color Space: ITU-R 709 Interlaced: no Video Tracks: 2 Audio Tracks: 2 Audio Channels: 2 channels (stereo) Thumbnails: Audio checked, Video checked Preview profile: Automatic Thank you for your assistance. https://drive.google.com/file/d/1ERHLLWmtvsADGIMjL1y_xFfXImf5e3gu/view
I downloaded a .mts file from the web and put it through the same kdenlive version and settings as the previous post, and upon replicating and rendering the effects done in the Failure project, I found that the entire clip rendered successfully. Just to be sure it wasn't fixed across the board, I loaded up the Failure Example Clip in a fresh project with the same settings as before and found the same result as before. I suspect the clips from that camera are encoded in a way that kdenlive accepted before, but no longer does. If a difference between the Failure Clip and the below-linked Success Clip can be found, that could be the key to fixing this bug. The following .zip file contains: "mts Zoom Render Success Example Clip.mts" (the input video), "mts Zoom Render Success Example.kdenlive", and "mts Zoom Render Success Example.mp4" (the output video). The parameters are exactly the same as the contents of the previous .zip. I hope the issue will be discovered and fixed soon, and I am willing to assist in any way I can to help get there. If need be, I can try and sift through previous kdenlive versions to figure out which build initially produced this issue. Thank you for your time. https://drive.google.com/file/d/1hHMaHVMxWaZiSDdP4fimkI_u6X4Px6Tv/view?usp=sharing
I went back and tested the versions I successfully rendered projects with, and after observing versions 20.04.1, 20.08.2, and 20.12.1b similarly fail as the above versions (20.04.1 showed the second part of the clip but didn't apply the effect), I am beginning to think this is a hardware compatibility issue somehow. I built a new computer in September of last year and am now using an AMD CPU/NVIDIA GPU combo as opposed to the Intel CPU/AMD GPU combo I was using to successfully render projects with my old computer. I do still have that computer available to me, and I intend to test my theory by the end of the week. Please let me know if there is anything I should additionally test. Additionally, I have confirmed that this issue is affecting me on version 21.12.1, even after a clean reinstallation of kdenlive.
What you can try is a test with transcoded clips. Take 1 of your clips, right click in the project bin -> transcode -> choose 1 of them (i.e. remux with MKV), and try again to render. Make sure all video drivers are updated.
I tried to remux with several different transcode options that I thought were relevant to the clip (DNxHD 1080i 30 fps 220 Mb/s [the clips are labeled as 1080i], DNxHD 1080p 30 fps 220 Mb/s, Lossless Matroyska, Remux MPEG-2 PS/VOB, Remux with MKV), but all of them produced the same result as rendering with no transcoding. I'm thinking that I'm going to have to resort to trying file conversions, but I'll have to re-add a bunch of effects and keyframes exactly as they are now. If there's any more info I can provide or anything else I can try in kdenlive, please let me know. I was hoping to test my other computer last week, but I was busy with other things going on. I still intend to report how that turns out.