25.10.2025, 20:21
Quote:So you are using QTGMC and sRestore with some DVD input. (aiming for 29.97fps usually is wrong in this case, but your choice)
I chose that to match the framerate supposedly of the source. I'm open to becoming educated on what I am misunderstanding.
Quote:Does the speed also drop if you do not use sRestore? (sRestore is a pain and sadly enforces linear processing)
It appears to run at "full" speed.
I do notice that all encodes at start ramp up to a high frame rate (over 200) then framerate steadily declines over the length of the encode. For this 22 minute item the ending frame rate had fallen to 156 FPS. I assume this is normal behavior and is just something to do with how frame processing, cache/buffers and calculating an estimated remaining job time looks in the UI.
Quote:Does it make a difference if you enable 'Filtering->Vapoursynth->Misc->Script->Limit Cache (MB)->3/4 of system ram' ?
It started out looking better (running at about 40 fps) but went to the same place within a couple minutes.
once it hit about 5% I was down to about 2 fps.
Quote:Does it make a difference if you enable hardware decoding? (no clue whether that even works for lav or bestsource) Or try another source filter?
Turned on hardware decode and it does not appear to have made a difference.
I can live without using the bob and rSize combo.
I attached debugs for the above attempts in case it's of any use.
Once again thank you for the help and I am impressed with and liking these tools. I just have no learned what 98% of the tools/options do so have a lot to learn as I go.
P.S. I did get a compile error for ffmpeg when compiling the vapoursynth addons and had to comment out a line that was no longer supported.
Line # 98 in build-and-install-vapoursynth.sh
--enable-avresample