Disable Thumbnails to improve seeking (Using mouse wheel)

dkblackhawk

New member
Hey, been a user of VideoRedo for a while, this was a problem back in version 5 and I think I might have found the underlying issue...

When you use the mouse to seek fast, it works flawlessly, skipping to next frame is perfect.

However when using the mouse wheel on the seeker bar, it is much slower. From what I have gathered, thumbnails are still being generated even when the option to view them is turned off. It lines up in my testing as when I'm seeking fast, the thumbnails can't keep up. However one second and it causes it to regenerate which I assume leads to the lag.

So...my question is, is there a true option to turn off thumbnails or am I missing out on something else here? If I don't make sense, I can provide a video to what I mean.

Thanks.
 

Dan203

Senior Developer
Staff member
What resolution do you have the thumbnails set to? If you have them set to anything other than frames then it can slow down seeking.

Now as to why it's happening even when the thumbnails are turned off.... I'll have to look into that to see why that is the case.
 

dkblackhawk

New member
What resolution do you have the thumbnails set to? If you have them set to anything other than frames then it can slow down seeking.

Now as to why it's happening even when the thumbnails are turned off.... I'll have to look into that to see why that is the case.
Not sure on resolution but the size is set to small. Thanks for looking into this!

3026
 

Dan203

Senior Developer
Staff member
Not sure on resolution but the size is set to small. Thanks for looking into this!

View attachment 3026
Sorry I should have explained. If you enable thumbnails and right click on them you can set the frequency of them. That's what I meant by "resolution". The longer ones take longer to render because we have to physically seek to say every 10 seconds in a video, decode the frame, then seek to the next one. We can't reasonably hold enough in the buffer to decode enough frames to fill that in. In single frame mode those are pulled from the buffer for the current position, so it's much more fluid and doesn't affect seeking much at all.
 

dkblackhawk

New member
Sorry I should have explained. If you enable thumbnails and right click on them you can set the frequency of them. That's what I meant by "resolution". The longer ones take longer to render because we have to physically seek to say every 10 seconds in a video, decode the frame, then seek to the next one. We can't reasonably hold enough in the buffer to decode enough frames to fill that in. In single frame mode those are pulled from the buffer for the current position, so it's much more fluid and doesn't affect seeking much at all.
Thanks

Also think I found out the issue. I use various capture devices. One outputs at High@L5.1 and the other outputs at High@L4.1

When using L5.1 content, seeking with the mouse wheel is slow. Just figure I would update, no clue if that is even fixable to be honest.
 

Dan203

Senior Developer
Staff member
It's probably more to do with the size of the GOPs (i.e. the distance between key frames) When the file has large GOPs we have to decode the whole thing to display the frames in the middle, which can take longer depending on how many frames there are. Higher encoding levels allow for longer GOPs, so your capture card is likely using those with the L5.1 option. One way to speed this up is set the "force iframe seek" option in Tools->Options->Navigation to 1. That will force most seeking to seek to a key frame, so it doesn't have to decode any extra frames to display. But that is still not 100% going to help, as internally we still have to search for the key frames, which if the GOPs are really long can still take a while.

Some files these days are ridiculous. We've seen some with GOPs comprising hundreds of frames. For comparison the average MPEG-2 file is about 15 frames and the max is 32. But with H.264 and H.265 they can be hundreds of frames which can cause some issues with our seeking logic.
 

dkblackhawk

New member
It's probably more to do with the size of the GOPs (i.e. the distance between key frames) When the file has large GOPs we have to decode the whole thing to display the frames in the middle, which can take longer depending on how many frames there are. Higher encoding levels allow for longer GOPs, so your capture card is likely using those with the L5.1 option. One way to speed this up is set the "force iframe seek" option in Tools->Options->Navigation to 1. That will force most seeking to seek to a key frame, so it doesn't have to decode any extra frames to display. But that is still not 100% going to help, as internally we still have to search for the key frames, which if the GOPs are really long can still take a while.

Some files these days are ridiculous. We've seen some with GOPs comprising hundreds of frames. For comparison the average MPEG-2 file is about 15 frames and the max is 32. But with H.264 and H.265 they can be hundreds of frames which can cause some issues with our seeking logic.
That has improved it so much, thanks for the help!
 
Top Bottom