SUMMARY I started editing my video as I always do but yesterday when I was editing another video and tried to render it my kdenlive crashed. LOG: [mp4 @ 000000000588ba00] Using AVStream.codec to pass codec parameters to muxers is deprecated, use AVStream.codecpar instead. [mp4 @ 000000000588ba00] Using AVStream.codec to pass codec parameters to muxers is deprecated, use AVStream.codecpar instead. Current Frame: 27, percentage: 0 [swscaler @ 0000000016fed5c0] Warning: data is not aligned! This can lead to a speed loss I'm using transform and fade effects; OBSERVED RESULT The video render crashes. EXPECTED RESULT The video to be rendered. SOFTWARE/OS VERSIONS Windows: 10 (64-bits) macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION I was using 20.08.0 and got this error so I tried to update it to 20.08.2 but the error persists...
Note: I did a mistake when copying the error log the full log is: [mp4 @ 000000000584ba00] Using AVStream.codec to pass codec parameters to muxers is deprecated, use AVStream.codecpar instead. [mp4 @ 000000000584ba00] Using AVStream.codec to pass codec parameters to muxers is deprecated, use AVStream.codecpar instead. Current Frame: 27, percentage: 0 [swscaler @ 00000000198cc040] Warning: data is not aligned! This can lead to a speed loss Current Frame: 618, percentage: 7
In the rendering dialog click "more option" -> disable "parallel processing" -> set Threads to "0" (zero). Try again.
(In reply to emohr from comment #2) > In the rendering dialog click "more option" -> disable "parallel processing" > -> set Threads to "0" (zero). Try again. I disabled parallel processing and set threads to 0 but the error persists: [mp4 @ 0000000009cc1cc0] Using AVStream.codec to pass codec parameters to muxers is deprecated, use AVStream.codecpar instead. [mp4 @ 0000000009cc1cc0] Using AVStream.codec to pass codec parameters to muxers is deprecated, use AVStream.codecpar instead. Current Frame: 2, percentage: 0 [swscaler @ 0000000018e71e40] Warning: data is not aligned! This can lead to a speed loss Current Frame: 623, percentage: 7
The paths are set correct? Goto settings -> configure Kdenlive -> Environment -> make sure the paths of FFmpeg, FFpplay, FFprobe has the same root directory as MLT.
(In reply to emohr from comment #4) > The paths are set correct? > > Goto settings -> configure Kdenlive -> Environment -> make sure the paths of > FFmpeg, FFpplay, FFprobe has the same root directory as MLT. I didn't understand exactly what you mean with "root" folder so I'll send you the paths as how they are... FFmpeg C:/Program Files/kdenlive/bin/ffmpeg.exe FFplay C:/Program Files/kdenlive/bin/ffplay.exe FFprobe C:/Program Files/kdenlive/bin/ffprobe.exe MLT profiles folder C:/Program Files/kdenlive/share/mlt/profiles Melt path C:/Program Files/kdenlive/bin/melt.exe But I already did render videos with Kdenlive before, I'm not sure if it would help but it is...
The log says the crash happens at frame 623 (if 25FPS this means 25sec), is there a clip with special dimensions here (swscale resizes an image and likes the dimensions to be multiple of 16). Or maybe an effect/transition here...
(In reply to Vincent PINON from comment #6) > The log says the crash happens at frame 623 (if 25FPS this means 25sec), is > there a clip with special dimensions here (swscale resizes an image and > likes the dimensions to be multiple of 16). > Or maybe an effect/transition here... Frame 2 Start of a Transform effect. Frame 623 End of that same Transform effect. That transform effect makes a zoom with rotation, but I already rendered it before in a "test video" just to see how my video was going... This the first transform effect I created.
Frame 623 may be the last rendered correctly, then it would be the clip/effect just after?
(In reply to Vincent PINON from comment #8) > Frame 623 may be the last rendered correctly, then it would be the > clip/effect just after? After this clip there is 1 small clip without any effect more before the next Transform, as I said before my video uses a lot of transform and fade effects, although the video isn't complete yet cause of that bug so I would add more later. So for now the video got only 2 minutes but at the end it would be 6 minutes or longer...
I downloaded the new version of Kdenlive and tried to render it but then I got a different error: [wav @ 0000000002a915c0] Discarding ID3 tags because more suitable tags were found. [wav @ 0000000002a83640] Discarding ID3 tags because more suitable tags were found. [wav @ 0000000002bab4c0] Discarding ID3 tags because more suitable tags were found. [wav @ 0000000002baf2c0] Discarding ID3 tags because more suitable tags were found. [wav @ 0000000005a42f40] Discarding ID3 tags because more suitable tags were found. [wav @ 00000000059696c0] Discarding ID3 tags because more suitable tags were found. [wav @ 00000000084dac40] Discarding ID3 tags because more suitable tags were found. [wav @ 00000000084e2940] Discarding ID3 tags because more suitable tags were found. [mp4 @ 0000000005a6ffc0] Using AVStream.codec to pass codec parameters to muxers is deprecated, use AVStream.codecpar instead. [mp4 @ 0000000005a6ffc0] Using AVStream.codec to pass codec parameters to muxers is deprecated, use AVStream.codecpar instead. Current Frame: 27, percentage: 0 [swscaler @ 0000000014b30040] Warning: data is not aligned! This can lead to a speed loss Current Frame: 617, percentage: 7 [wav @ 00000000166b1580] Discarding ID3 tags because more suitable tags were found. [wav @ 00000000151de980] Discarding ID3 tags because more suitable tags were found. Current Frame: 1655, percentage: 20
Please try with Windows_Nightly_Build. Use the standalone version so you don't have to install (ending (7z"). https://binary-factory.kde.org/job/Kdenlive_Nightly_mingw64/lastSuccessfulBuild/artifact/ This version contains some fixes.
Now error after frame 1655, divide by fps to know at which timecode to look for clip/effect/transition
(In reply to Vincent PINON from comment #12) > Now error after frame 1655, divide by fps to know at which timecode to look > for clip/effect/transition Frame: 27 I'm not sure about how to open a 7z file but I'll try... If something happen I'll reply...
(In reply to fernando404.luizf from comment #13) > (In reply to Vincent PINON from comment #12) > > Now error after frame 1655, divide by fps to know at which timecode to look > > for clip/effect/transition > > Frame: 27 > > I'm not sure about how to open a 7z file but I'll try... If something happen > I'll reply... Quick note... When I did run Kdenlive 20.08.3 (the newest version) then I tried to editing another video and my preview was flashing green... I checked if the problem was with my video file but it wasn't, I tried with mp4 and flv.
Green flashing: Similar to this https://invent.kde.org/multimedia/kdenlive/-/issues/753 ?
(In reply to emohr from comment #15) > Green flashing: Similar to this > https://invent.kde.org/multimedia/kdenlive/-/issues/753 ? No, it's just like adding a color effect that lets the video green like... Normal video... few moments... greenish video... few moments... normal video...
Can you upload the files and the project that are causing the crash so I can debug?
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!