| Summary: | Crashing | ||
|---|---|---|---|
| Product: | [Applications] kdenlive | Reporter: | newreelmediallc |
| Component: | Rendering & Export | Assignee: | Jean-Baptiste Mardelle <jb> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | critical | CC: | fritzibaby, glyn, julius.kuenzel, snd.noise |
| Priority: | NOR | Flags: | fritzibaby:
timeline_corruption+
|
| Version First Reported In: | 20.08.1 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
newreelmediallc
2020-12-14 00:35:24 UTC
(In reply to newreelmediallc from comment #0) > SUMMARY > The software crashes constantly. I am new to it as well as to video editing > so I don't know what else to do other than mess with profile settings and > proxy clip settings. > > STEPS TO REPRODUCE > 1. Gopro footage, many clips, shot in 5k and 30fps, profile settings > automatically adjusting to 5120 x 2880 29.97fps. > 2. Proxy clips enabled hoping to fix crashing > 3. Add a fade in or speed up > > OBSERVED RESULT > Preview choppy before software closes > > EXPECTED RESULT > Smoothly edited and displayed footage... > > SOFTWARE/OS VERSIONS > Windows: > macOS: > Linux/KDE Plasma: > (available in About System) > KDE Plasma Version: > KDE Frameworks Version: > Qt Version: > > ADDITIONAL INFORMATION What resolution is your video preview window set to? I'm having a similar problem, and when my preview window is set to 270p or 360p it crashes, but higher resolutions seem fine. The default is 1:1, but you can scale it down to sometimes avoid having to use proxy clips. (In reply to newreelmediallc from comment #0) > SUMMARY > The software crashes constantly. I am new to it as well as to video editing > so I don't know what else to do other than mess with profile settings and > proxy clip settings. > > STEPS TO REPRODUCE > 1. Gopro footage, many clips, shot in 5k and 30fps, profile settings > automatically adjusting to 5120 x 2880 29.97fps. > 2. Proxy clips enabled hoping to fix crashing > 3. Add a fade in or speed up > > OBSERVED RESULT > Preview choppy before software closes > > EXPECTED RESULT > Smoothly edited and displayed footage... > > SOFTWARE/OS VERSIONS > Windows: > macOS: > Linux/KDE Plasma: > (available in About System) > KDE Plasma Version: > KDE Frameworks Version: > Qt Version: > > ADDITIONAL INFORMATION Hi, thanks for your report! Do you use the appimage (it is highly recommend to do so)? First of all please checkout the latest version https://kdenlive.org/en/download/ and try again. If it is still happening: do you use the preview resolution scaling as described by Glyn? (In reply to Glyn from comment #1) > What resolution is your video preview window set to? I'm having a similar > problem, and when my preview window is set to 270p or 360p it crashes, but > higher resolutions seem fine. The default is 1:1, but you can scale it down > to sometimes avoid having to use proxy clips. Which version and os do you use? Can you pinpoint the problem to specific things like framerate, resolution,… or give a more specific introduction how to reproduce? (In reply to Julius Künzel from comment #3) > (In reply to Glyn from comment #1) > > What resolution is your video preview window set to? I'm having a similar > > problem, and when my preview window is set to 270p or 360p it crashes, but > > higher resolutions seem fine. The default is 1:1, but you can scale it down > > to sometimes avoid having to use proxy clips. > > Which version and os do you use? Can you pinpoint the problem to specific > things like framerate, resolution,… or give a more specific introduction how > to reproduce? Hi Julius, I am running 20.12.2 and Linux Mint 20.1 All I have to do to reproduce, is open a project, and make sure the video project preview window is set to 270p or 360p. and it crashes after a few seconds. If I alter the preview resolution to anything higher than this, the frame rate is slower, but it doesn't lock up and quit. Is this happening with the AppImage as well? Can you test please? (In reply to farid from comment #5) > Is this happening with the AppImage as well? Can you test please? For me it is yes. I have 20.12.2 installed, as well as the AppImage of the same version. The results were the same. (In reply to Glyn from comment #6) > (In reply to farid from comment #5) > > Is this happening with the AppImage as well? Can you test please? > > For me it is yes. I have 20.12.2 installed, as well as the AppImage of the > same version. The results were the same. Since this is always reproducible, could you upload a project with some small videos so I can debug further? (In reply to farid from comment #7) > (In reply to Glyn from comment #6) > > (In reply to farid from comment #5) > > > Is this happening with the AppImage as well? Can you test please? > > > > For me it is yes. I have 20.12.2 installed, as well as the AppImage of the > > same version. The results were the same. > > Since this is always reproducible, could you upload a project with some > small videos so I can debug further? Hi Farid, Your question has prompted me to test further, and I think I've managed to figure out the problem. I originally posted the issue in this post https://bugs.kde.org/show_bug.cgi?id=432550 As you can see from the original post, Kdenlive seemed to be crashing on the server hardware, while the desktop pc (which has much lower spec hardware) didn't quit when scaling. To test, I have booted the desktop pc with the server drive, and Kdenlive works fine when scaling, so it is most likely a hardware thing. I have tested both the installed 20.12.2 version, and the appimage version. I wonder what hardware others who are having scaling issues are using... I did try different Nvidia driver versions, and that didn't seem to fix the issue either on the server. I have since sold some of the server components, so can't do any testing directly on the server, but I hope this helps to pinpoint the issue. If I recall, the earliest Nvidia driver version available that I tested was 340. As you can see from the specs on the other page, I was running an Nvidia Quadro card. I would suspect that most people having issues would be running Geforce cards though. It would be helpful if you can provide something like a backtrace. See https://kdenlive.org/en/bug-reports/ for some basic instructions. Btw do you use Movit (GPU mode)? (In reply to Julius Künzel from comment #9) > It would be helpful if you can provide something like a backtrace. See > https://kdenlive.org/en/bug-reports/ for some basic instructions. > > Btw do you use Movit (GPU mode)? Hi. I no longer have the same hardware to test with. However, I have since upgraded to another PC, which also has a Xeon and Nvidia Quadro card, and I don't have the same issues with this hardware as I did with the previous Xeon's (E5-2650 v2's), and a Quadro K620 card). The processor is a Xeon E3-1240 v2, and Nvidia Quadro P620. It seems to run fine when scaling and rendering using 20.12.2. It did quit when using 20.12.3 though (which is an issue which seems to keep cropping up no matter what hardware I use). It seems to be when using CPU rendering. It hasn't happened when using the GPU with NVENC H265. The motherboard chipset is Intel C216, rather than the C602 chipset I tested on before. Therefore, it can't be Nvidia cards in general or Xeon processors in general which are causing the problem. Maybe it could be the motherboard chipset? No, I don't use the Movit library. @newreelmediallc@gmail.com We made some improvment with fade and speed. Please test with daily build to see if the issue still persists. https://binary-factory.kde.org/job/Kdenlive_Nightly_Appimage_Build/lastSuccessfulBuild/artifact/ Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! (In reply to emohr from comment #11) > @newreelmediallc@gmail.com > > We made some improvment with fade and speed. Please test with daily build to > see if the issue still persists. > > https://binary-factory.kde.org/job/Kdenlive_Nightly_Appimage_Build/ > lastSuccessfulBuild/artifact/ Hi. Thanks for that! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |