Inaccurate frame count when jumping forward & backwards using default shortcuts

Bug
1

Operating System = Windows 11

Shotcut version = 26.9.27

Hello,
In Shotcut 26.9.27, I noticed that if I use the default shortcut, PgUp, to jump backwards 1 second in the middle of a track, it actually jumps back a total of 00:01:01. However, if I use PgDown to jump forward 1 second in the middle of a track, it only jumps forward a total of 00:00:29.

If I use PgDown to jump forward at the beginning of a track, it only jumps to 00:00:28. This also happens for the other default shortcuts that jump forward and backwards on the timeline but, the longer the jump (5 seconds, 10 seconds), the bigger the inaccuracy.

This also causes my “Set Jump Time” of 00:00:00:15 to jump backwards 17 frames and forward only 14 frames.

All of my video files have a frame rate of 30.000000 and the results are the same no matter which time format is selected.

-Mike

2

I do not reproduce it. I tested in the timeline with video modes with 24, 25, 29.97, 30, and 59.94. I also tested Source-only with automatic video mode and a video with 29.97 fps. What is your video mode frame rate, not the source frame rate? Click Timeline > Output and then see Properties or look in the

3

Hi Dan,

My video mode is set to Automatic and when I go to Timeline > Output > View > Properties, it says 30.000000 fps. I’m using the same camera with the same settings to record video so the clips should have the same specs but this is the first version, 26.9.27, I’m seeing the jump discrepancies.

I first noticed it when using ALT+PgDown (with my jump time set to 15 frames), which I use a lot, while editing my first video in the new version.

If you can’t reproduce it, that’s ok, it’s not a huge deal. Thanks!

-Mike

4

I only tested page up and down since that is the first thing mentioned and would be the most obvious. I used the drop-frame timecode format. Now, I tested setting the jump time with alt+page and did not reproduce that either. I wonder what the difference is that causes that for you.

5

I’m not sure if it matters but let me explain how I was getting my results. I created a new project with 2 video tracks. I put a video on each track and split them both in the same spot, I then jumped from the spit on the V1 and then drug the clip on V2 until it snapped to where the playhead landed. The V2 clip shows exactly how many frames it moved when dragging.

-Mike