| Summary: | Rendering progress view is broken | ||
|---|---|---|---|
| Product: | [Applications] kdenlive | Reporter: | Noam Raphael <noamraph> |
| Component: | User Interface & Miscellaneous | Assignee: | Jean-Baptiste Mardelle <jb> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | berndmj, bjorn.petter |
| Priority: | NOR | ||
| Version First Reported In: | 24.05.2 | ||
| Target Milestone: | --- | ||
| Platform: | Microsoft Windows | ||
| OS: | Microsoft Windows | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | The log file while rendering | ||
|
Description
Noam Raphael
2024-07-12 06:23:01 UTC
Similar to this: https://bugs.kde.org/show_bug.cgi?id=490250? (In reply to Noam Raphael from comment #0) > Created attachment 171595 [details] > The log file while rendering > > *** > If you're not sure this is actually a bug, instead post about it at > https://discuss.kde.org > > If you're reporting a crash, attach a backtrace with debug symbols; see > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports > *** > > SUMMARY > > > STEPS TO REPRODUCE > 1. Render a video > > OBSERVED RESULT > The progress view is broken. For example, it may show "Remaining time > 00:00:00 (frame 81 at -52 fps)" when it's actually near the end > > EXPECTED RESULT > Show the true rendered frame, and a reasonable ETA estimate > > Kdenlive: 24.05.2 > Package Type: Unknown/Default > MLT: 7.25.0 > Qt: 6.7.1 (built against 6.7.1 x86_64-little_endian-llp64) > Frameworks: 6.3.0 > System: Windows 11 Version 23H2 > Kernel: winnt 10.0.22631 > CPU: x86_64 > Windowing System: windows > GPU: > Movit (GPU): disabled > Track Compositing: qtblend > > ADDITIONAL INFORMATION > > I believe this is caused by melt.exe producing garbled output, perhaps > because of windows line endings, or parallelization, or both. See the > attached log file. For example, it includes this: > > percentage: 10Current Frame: 11075, percentage: 1011079, percentage: > 10Current Frame:11083 > > The rendering was without using multiple CPUs. > > Thanks! > Noam I have seen a similar behaviour here (Windows 11, Kdenlive 24.05.2). In Kdenlive 24.02.2 the progress tracker was working properly and accuretely. Git commit 3b7d3effdc553f0452fa0470d27246daa83cfcb7 by Jean-Baptiste Mardelle. Committed on 12/08/2024 at 14:48. Pushed by mardelle into branch 'release/24.08'. Fix rendering progress sometimes incorrect M +12 -4 renderer/renderjob.cpp M +1 -0 renderer/renderjob.h https://invent.kde.org/multimedia/kdenlive/-/commit/3b7d3effdc553f0452fa0470d27246daa83cfcb7 Problem should be solved in my recent commit. Would be great if you can test the daily build and let me know if it is fixed. You can download the Windows build from the upcoming 24.08 version here: https://cdn.kde.org/ci-builds/multimedia/kdenlive/release-24.08/windows/ (In reply to Jean-Baptiste Mardelle from comment #4) > Problem should be solved in my recent commit. > Would be great if you can test the daily build and let me know if it is > fixed. You can download the Windows build from the upcoming 24.08 version > here: > https://cdn.kde.org/ci-builds/multimedia/kdenlive/release-24.08/windows/ I tried build 8658 (24.11.70), and now the progress tracking works as expected. Thanks for the prompt reply and fix :) (In reply to bjorn.petter from comment #5) > (In reply to Jean-Baptiste Mardelle from comment #4) > > Problem should be solved in my recent commit. > > Would be great if you can test the daily build and let me know if it is > > fixed. You can download the Windows build from the upcoming 24.08 version > > here: > > https://cdn.kde.org/ci-builds/multimedia/kdenlive/release-24.08/windows/ > > I tried build 8658 (24.11.70), and now the progress tracking works as > expected. Thanks for the prompt reply and fix :) I saw now that was a different build than the one you asked me to test, but I assume the one I tested also has the fix. Sorry for the confusion. ๐๐งน โ ๏ธ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. 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. Closing as RESOLVED WORKSFORME. |