Bug 499221

Please review my properly formatted google doc user story.

https://docs.google.com/document/d/1j8r-GFvfvPOl8GzFa41-uUimcPCKP6wS4V5empQeTiI/edit?usp=sharing

Thank you for the request. 
We opened the same request 4 years ago https://invent.kde.org/multimedia/kdenlive/-/issues/886. 

Part of them is implemented with a menu entry in the clip monitor, to switch between 'normal timecode' and 'source timecode'.

Created attachment 177765 [details]
attachment-559878-0.html

Thanks for sharing.

Yes that is a similar concept but a bit difference as this is setting a 
masterclock based on compliance.
The other challenge is support for drop-frame timecode on the edit side.

As mentioned in the user story, when Opentimeline.io is working.
There could be issues as most 29.97 timelines will be set with a 
dropframe flag.

Best
Jeff

Jeffrey Krebs
CPO

E: jeff.krebs@bridgedigitalinc.com
M: 647 783 2228
www.bridgedigitalinc.com
linkedin icon
<https://www.linkedin.com/in/jeffrey-krebs-0063bb6?lipi=urn%3Ali%3Apage%3Ad_flagship3_profile_view_base_contact_details%3BJxM5E9g1RhSJnFWsZBCMFw%3D%3D>



------ Original Message ------
From "emohr" <bugzilla_noreply@kde.org>
To rockinjeff@gmail.com
Date 2025-01-28 9:04:40 AM
Subject [kdenlive] [Bug 499221] User Story: User-Definable Starting 
Timecode for Edit Sequences in Kdenlive

>https://bugs.kde.org/show_bug.cgi?id=499221
>
>emohr <fritzibaby@gmx.net> changed:
>
>            What    |Removed                     |Added
>----------------------------------------------------------------------------
>            Keywords|                            |triaged
>                  CC|                            |fritzibaby@gmx.net
>      Ever confirmed|0                           |1
>              Status|REPORTED                    |CONFIRMED
>
>--- Comment #2 from emohr <fritzibaby@gmx.net> ---
>Thank you for the request.
>We opened the same request 4 years ago
>https://invent.kde.org/multimedia/kdenlive/-/issues/886.
>
>Part of them is implemented with a menu entry in the clip monitor, to switch
>between 'normal timecode' and 'source timecode'.
>
>--
>You are receiving this mail because:
>You reported the bug.

Git commit 14d1bdb8893e853bf76189cc63c5f1d293c474ca by Jean-Baptiste Mardelle.
Committed on 10/05/2025 at 05:32.
Pushed by mardelle into branch 'master'.

Changing sequence timecode offset now updates timecode display in timeline ruler, monitor timecode and guides list

M  +1    -1    src/bin/sequenceclip.cpp
M  +5    -0    src/core.cpp
M  +2    -0    src/core.h
M  +1    -0    src/dialogs/markerdialog.cpp
M  +1    -0    src/mainwindow.cpp
M  +5    -2    src/monitor/monitor.cpp
M  +4    -2    src/monitor/monitor.h
M  +18   -14   src/project/dialogs/guideslist.cpp
M  +12   -1    src/project/dialogs/guideslist.h
M  +16   -0    src/project/projectmanager.cpp
M  +3    -0    src/project/projectmanager.h
M  +1    -0    src/timeline2/view/dialogs/clipdurationdialog.cpp
M  +2    -1    src/timeline2/view/qml/Ruler.qml
M  +6    -0    src/timeline2/view/timelinecontroller.cpp
M  +7    -0    src/timeline2/view/timelinecontroller.h

https://invent.kde.org/multimedia/kdenlive/-/commit/14d1bdb8893e853bf76189cc63c5f1d293c474ca

I have now implemented a start timecode (called Timecode offset) in the clip properties of Sequence clips. Setting an offset will affect the timeline ruler, monitor and guides timecodes. In my quick tests, the timeline  timecode seem to correctly handle drop frame tc.

Please have a look, you can find dev builds with this feature in:
https://cdn.kde.org/ci-builds/multimedia/kdenlive/master/

Created attachment 181161 [details]
attachment-55907-0.html

Thank you for your hard work.
I'll test

On Sat, May 10, 2025, 10:21 PM Jean-Baptiste Mardelle <
bugzilla_noreply@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=499221
>
> Jean-Baptiste Mardelle <jb@kdenlive.org> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>              Status|CONFIRMED                   |NEEDSINFO
>          Resolution|---                         |WAITINGFORINFO
>
> --- Comment #5 from Jean-Baptiste Mardelle <jb@kdenlive.org> ---
> I have now implemented a start timecode (called Timecode offset) in the
> clip
> properties of Sequence clips. Setting an offset will affect the timeline
> ruler,
> monitor and guides timecodes. In my quick tests, the timeline  timecode
> seem to
> correctly handle drop frame tc.
>
> Please have a look, you can find dev builds with this feature in:
> https://cdn.kde.org/ci-builds/multimedia/kdenlive/master/
>
> --
> You are receiving this mail because:
> You reported the bug.

Created attachment 181214 [details]
attachment-777194-0.html

That's great Jean-Baptiste. That worked!

Question, if a user wants to set a Non-dropframe frame flag under 29.97,
how is that achieved?

Usually it would be for example a user entering a semicolon (dropframe) or
full-colon (non-dropframe)
Your thoughts are appreciated on this.

Best
Jeffrey

On Sat, May 10, 2025 at 10:44 PM Jeffrey Krebs <rockinjeff@gmail.com> wrote:

> Thank you for your hard work.
> I'll test
>
> On Sat, May 10, 2025, 10:21 PM Jean-Baptiste Mardelle <
> bugzilla_noreply@kde.org> wrote:
>
>> https://bugs.kde.org/show_bug.cgi?id=499221
>>
>> Jean-Baptiste Mardelle <jb@kdenlive.org> changed:
>>
>>            What    |Removed                     |Added
>>
>> ----------------------------------------------------------------------------
>>              Status|CONFIRMED                   |NEEDSINFO
>>          Resolution|---                         |WAITINGFORINFO
>>
>> --- Comment #5 from Jean-Baptiste Mardelle <jb@kdenlive.org> ---
>> I have now implemented a start timecode (called Timecode offset) in the
>> clip
>> properties of Sequence clips. Setting an offset will affect the timeline
>> ruler,
>> monitor and guides timecodes. In my quick tests, the timeline  timecode
>> seem to
>> correctly handle drop frame tc.
>>
>> Please have a look, you can find dev builds with this feature in:
>> https://cdn.kde.org/ci-builds/multimedia/kdenlive/master/
>>
>> --
>> You are receiving this mail because:
>> You reported the bug.
>
>

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