Bug 488433

Summary:	Rendering Time is no longer accurate
Product:	[Applications] kdenlive	Reporter:	Ash <Ashleybopp5>
Component:	Rendering & Export	Assignee:	Jean-Baptiste Mardelle <jb>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	anton140315, berndmj, byrongamer223, youssef.msellek, zirylax
Priority:	NOR
Version First Reported In:	24.05.0
Target Milestone:	---
Platform:	Microsoft Windows
OS:	Microsoft Windows
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	Image showing a configuration in which the bug appears. Image of an example in which the timeline and remaining time get stuck

Description Ash 2024-06-12 22:12:59 UTC

***
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
Kdenline normally has a spot on rendering timer, actually one of the best I've seen. It is broken in this newest update.

STEPS TO REPRODUCE
1.  Render a video you have created.
2. I am currently rendering H.264 (libx264+acc) Lossless, so its a mp4.

OBSERVED RESULT
Render time says "00:00:01", so the timer is wrong. The good news is that it is rendering flawlessly otherwise.

EXPECTED RESULT
An accurate timer listed as the video renders. The previous release had it extremely accurate.

SOFTWARE/OS VERSIONS
Windows: Windows 11

ADDITIONAL INFORMATION
I have not tested for other video formats. Thanks for reading.

Comment 1 zirylax 2024-06-24 16:43:20 UTC

Several people have experienced this bug

Comment 2 zirylax 2024-06-24 16:49:14 UTC

Created attachment 170917 [details]
Image showing a configuration in which the bug appears.

OS used: Windows version 10.0.19045 compilation 19045

CPU: Intel i7 9700 @ 3.00GHz

Comment 3 zirylax 2024-06-24 16:51:50 UTC

Created attachment 170918 [details]
Image of an example in which the timeline and remaining time get stuck

OS used: Windows version 10.0.19045 compilation 19045

CPU: Intel i7 9700 @ 3.00GHz

Comment 4 Bernd 2024-06-29 00:45:38 UTC

*** Bug 489412 has been marked as a duplicate of this bug. ***

Comment 5 Moutchou 2024-09-01 00:31:30 UTC

I am facing the same issue. Do I need to clone this bug to give it a higher priority in the dev team backlog ? Or this comment is enough ?

Comment 6 Bernd 2024-09-17 12:49:14 UTC

(In reply to Moutchou from comment #5)
> I am facing the same issue. Do I need to clone this bug to give it a higher
> priority in the dev team backlog ? Or this comment is enough ?

Further comments are fine.

24.08.1 was released recently and contains many bug fixes. Can you please check whether the issue still exists? Thanks! If it does, please come back and change the status of the bug to CONFIRMED

Comment 7 Bug Janitor Service 2024-10-02 03:47:23 UTC

🐛🧹 ⚠️ 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!

Comment 8 Bug Janitor Service 2024-10-17 03:48:16 UTC

🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.