crewtimer / crewtimer-video-review

Utility app for connecting to FinishLynx or recorded video
MIT License
0 stars 0 forks source link

Small hyperzoom timestamp bug #33

Closed basrijn closed 2 months ago

basrijn commented 3 months ago

Hyperzoom is awesome!

I think I found a small bug, I was trying to check if the little magnifying glass (estimated ts) disappeared when I hit the next full frame. It was not showing, but I was @ 2ms skip and that jumped over my actual timestamps:

It only seems to do it on the first full frame, after that it keeps going by 1ms. I don't see the magnifying glass disappear. Does it keep in the interpolated images, or does it show the actual native frame when it hit a point where there is one available?

glenne commented 3 months ago

Can you try this on the 1.0.3 release? I made some fixes in that area.

crewtimer.com/help/downloads

Glenn

On Wed, Jul 3, 2024 at 7:51 PM Bas Rijniersce @.***> wrote:

Hyperzoom is awesome!

I think I found a small bug, I was trying to check if the little magnifying glass (estimated ts) disappeared when I hit the next full frame. It was not showing, but I was @ 2ms skip and that jumped over my actual timestamps:

  • I set to 1 ms resolution
  • Checked actual frames (at x.145, x.154, x.163)
  • Jump to the frame before .145 (.137)
  • Zoom in
  • Scroll 1 ms forward. All good, until I jump from .144 to .145, it shows .137 instead
  • Scroll one more forward and I see .145

It only seems to do it on the first full frame, after that it keeps going by 1ms. I don't see the magnifying glass disappear. Does it keep in the interpolated images, or does it show the actual native frame when it hit a point where there is one available?

— Reply to this email directly, view it on GitHub https://github.com/crewtimer/crewtimer-video-review/issues/33, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAITQ6CQUKPJG4HWXSIQYATZKS2B3AVCNFSM6AAAAABKKVBQH2VHI2DSMVQWIX3LMV43ASLTON2WKOZSGM4DSOBRGY3DMNQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>

glenne commented 2 months ago

Fixed in 1.0.3 release