Bug 498396 - Feature: Add frame export timecode to filename (and differentiate) based on if extracted from either clip monitor or project monitor
Summary: Feature: Add frame export timecode to filename (and differentiate) based on i...
Status: CONFIRMED
Alias: None
Product: kdenlive
Classification: Applications
Component: Rendering & Export (other bugs)
Version First Reported In: 24.12.0
Platform: Other Linux
: NOR wishlist
Target Milestone: ---
Assignee: Jean-Baptiste Mardelle
URL:
Keywords: junior-jobs, triaged
Depends on:
Blocks:
 
Reported: 2025-01-08 21:02 UTC by fabrice salvaire
Modified: 2026-02-05 10:40 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description fabrice salvaire 2025-01-08 21:02:54 UTC
It would be helpful to have an option to add the time to the filename when we export a frame.
Comment 1 luzpaz 2026-01-17 11:41:54 UTC
Can you specify what your expectation of the filename will look like..?

Looks like for the logic for this is in  
https://invent.kde.org/multimedia/kdenlive/-/blob/master/src/monitor/monitor.cpp#L1404-1417
Comment 2 Bernd 2026-01-19 01:30:36 UTC
(In reply to fabrice salvaire from comment #0)
> It would be helpful to have an option to add the time to the filename when
> we export a frame.

What "time" do you have in mind: The time of when the export took place, the timecode of the extracted frame, the time the video was created, the time the video was modified, or what exactly is time in this context? Does it include date as well?
Comment 3 luzpaz 2026-01-20 19:20:06 UTC
(In reply to Bernd from comment #2)
> What "time" do you have in mind: The time of when the export took place, the
> timecode of the extracted frame, the time the video was created, the time
> the video was modified, or what exactly is time in this context? Does it
> include date as well?

Not speaking for OP but when I read it I assumed it was 'the timecode of the extracted frame'.
Comment 4 Bernd 2026-01-21 19:24:20 UTC
(In reply to luzpaz from comment #3)
> Not speaking for OP but when I read it I assumed it was 'the timecode of the
> extracted frame'.

That's my assumption as well but we could be wrong, so we need to be precise.

We also need to find a way to differentiate between the timecode for a frame extracted from the clip monitor and one from the project monitor. Perhaps with another prefix like "c" for clip and "p" for project monitor extracts.

Today the frame number is used which can be easily translated to timecode but having it right there is more convenient, of course.
Comment 5 Bug Janitor Service 2026-02-05 03:56:17 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 6 luzpaz 2026-02-05 10:40:33 UTC
> We also need to find a way to differentiate between the timecode for a frame extracted from the clip monitor and one from the project monitor. Perhaps with another prefix like "c" for clip and "p" for project monitor extracts.

Good idea.

I've updated the name of the ticket and changed its status so it won't get auto-closed by the bot.