First of all, thank you very much for maintaining kdenlive. It has been a great source of fun. The main reason I'm writing is to humbly suggest re-implementing its rendering log. I'd like to use it to find and fix rendering bugs. I followed the instructions in kdenlive_render's man page to create one by setting the environment variable named "KDENLIVE_RENDER_LOG". I set it before before trying to render in kdenlive $ export KDENLIVE_RENDER_LOG=1 ; export LANG=C ; kdenlive and before running kdenlive_render with a render script generated by kdenlive #! /bin/sh RENDERER="/usr/bin/kdenlive_render" MELT="/usr/bin/melt" SOURCE_0=<a .mlt script> TARGET_0=<a .webm file> PARAMETERS_0="-pid:7095 in=0 out=1565 $MELT atsc_720p_2997 avformat - $SOURCE_0 $TARGET_0 f=webm vcodec=libvpx acodec=vorbis crf=23 vb=0 quality=good aq=6 max-intra-rate=1000 cpu-used=4 threads=1 real_time=-1" KDENLIVE_RENDER_LOG=1 $RENDERER $PARAMETERS_0 I expected to find a render log file named like /tmp/kdenlive_render.log.XXXXXXXX Unfortunately, I didn't. I opened Debian bug report 884267. Patrick Matthäi, who maintains Debian's kdenlive package said he grepped through the source code, the render log is gone, and I might report a bug here, at kde.org. Please bring back kdenlive's render log. I think it would make debugging easier. Thanks, Kingsley
Thanks for your report! As far as I know the render log has not been removed. I recently got one. I think it will only be created if the rendering crashes, not if it was successful. Please check with a recent version (https://kdenlive.org/en/download/) and give some feedback. (You can try to crash the render by aborting the job)
Hi Julius! Thank you very much for your thoughts on my little bug report. If I understand correctly, I did as you asked. I clicked on the "Abort job" button in the rendering window of version 20.12.0-2 of kdenlive. However, I still see no file named like /tmp/kdenlive_render.log.XXXXXXXX I tried it with and without exporting KDENLIVE_RENDER_LOG=1 and LANG=C before running kdenlive. If it would be convenient, comfortable, and all those good things, feel free to explain where you find render logs. Maybe I looked in the wrong place. Thanks, Kingsley On 05/16/2021 13:52, Julius Künzel wrote: > https://bugs.kde.org/show_bug.cgi?id=387867 > > Julius Künzel <jk.kdedev@smartlab.uber.space> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Resolution|--- |WAITINGFORINFO > Status|REPORTED |NEEDSINFO > CC| |jk.kdedev@smartlab.uber.spa > | |ce > > --- Comment #1 from Julius Künzel <jk.kdedev@smartlab.uber.space> --- > Thanks for your report! As far as I know the render log has not been removed. I > recently got one. I think it will only be created if the rendering crashes, not > if it was successful. > > Please check with a recent version (https://kdenlive.org/en/download/) and give > some feedback. (You can try to crash the render by aborting the job) > > -- > You are receiving this mail because: > You reported the bug.
I can find the render log in the same directory as the output file. If I want to render to to /home/julius/videos/test.mp4 and abort it, I have a file called /home/julius/videos/test.mp4.log
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!