Sluggish seek and sometimes play/pause

[Sorgair]

This starts to happen between version 3.7 and 3.8, so it is from one of the new features added in 3.8 I assume. It happens on all versions since 3.8 as well, including the latest version, on all files; I am using mouse and keyboard to seek.

When clicking somewhere on the timeline to seek, it takes between instant to 3ish seconds to seek, whereas before in version 3.7 it is always instant. I suspect it has to do with the keyframes being shown on the timeline, as anything that makes the timeline look different (such as selecting a start/end keyframe) usually lags the UI.

I have tried using both the .zip and .exe download.

I'm on windows 10, and my pc specs are good enough that seeking shouldn't randomly be slow.

[mifi]

just to be sure, you mean this version from 2020, right? https://github.com/mifi/lossless-cut/releases/tag/v3.8.0

could be related to #1097 but I'm baffled by you experiencing this on such old versions

[Sorgair]

yeah it's that version, I went back to when the keyframe timeline was first added to find it

since I think I'm the only one with this, it could just be I have some problem with my OS since I haven't reset it in 6 years

also, watching videos of other people using lossless cut, mine takes far longer to open, where opening it from windows search hangs for ~3 seconds, leaving the search menu open, then for the first ~10ish seconds the window is just white. also, some other things show up very slowly, for example, the sunflowers appear for me 2 seconds after everything else

[mifi]

also, watching videos of other people using lossless cut, mine takes far longer to open, where opening it from windows search hangs for ~3 seconds, leaving the search menu open, then for the first ~10ish seconds the window is just white. also, some other things show up very slowly, for example, the sunflowers appear for me 2 seconds after everything else

are you using the .exe download or the .zip?

[Sorgair]

it happens on both

[mifi]

which os? is your computer very old? maybe you can try to delete the losslesscut directory from appdata (note you will loose all settings)

[Sorgair]

i tried deleting the directory but it didnt work

I'm on windows 10, it could be and probably is because I haven't reinstalled windows in 6 years, but everything is up to date

[mifi]

can you try with the newest version now?

[DGrv]

Hi, I have the same problem since a while.

I am on windows Microsoft Windows [Version 10.0.19044.2251]

I tried various thing but I am not an expert with the devtools. My opinion it is that it is coming from the build (version) of ffmpeg and ffprobe or at least it seems to be linked from what I explain below.

I tried old version of losslesscut 3.42, 3.39 but this is the same. I was then wondering if it was really using the build in ffmpeg or mine but could not be sure. That's why I would suggest that you create a console.log for the version and the path used for ffmpeg while opening losslesscut like you do for the version of losslesscut. ffprobe`` is already running something during opening.

Anyway you created a settings that the user can change the ffmpeg used #400

I used an old build from ffmpeg here ffmpeg-N-101328-g85ab9deb98-win64-gpl-shared-vulkan\bin and choose it as default.

It is working again like in the past, smooth like a swiss army knife :)

I hope it is helping you out.

[mifi]

@DGrv hi. just to be sure, you're using an external version of ffmpeg and it makes seeking faster? And if you disable external ffmpeg again seeking becomes slow? I don't understand how that can happen. Care to record a screencast that shows the problem?

[DGrv]

Mmmmm, seems that I do not succeed to reproduce it ... really strange. After disabling external ffmpeg again it is staying smooth. I do not understand it neither now. The 2 open points on my side are now the raw video from my camera (unfortunately I do not have anymore raw video from my gopro since I got it stolen few days ago) and that I updated few drivers the last days (after the last post) and the driver for the video card was I think one of them.

So my last post may be just bull shit but at least people can try ...

I will test with new videos from someone else with the same camera and same settings and if I can anyhow reproduce this behavior I will do for sure a screencast. Sorry for this.

[mifi]

Ok, thanks for reporting back, I will close for now - can reopen if problems resurface