QT Timer Error

turn off "svplight" extension if you're not using it

will be fixed in the next build

I think I figured it out.
The problem is svtube extension.
High CPU load problem does not happen with local files but only online video. After enabling/disabling svtube it works normal. Still waiting on explanation for QT Timer error message tho so I can totally fix this.

Ah ok thx
one more question.
How do I turn off performance quick estimation at the start of SVP?

sorry forget it I thought that was the problem but it works now.
for others with same problem --> the QT Timer error is because tube.cfg

For some strange reason when these value are missing in tube.cfg the error is caused

  "ui/autohide": 5,
    "ui/split_list": 30,
    "verbose": 0,

Sorry but really just one more question I swear haha.because you are developer
How can I make the output FPS exactly 60.0 FPS instead of 59.940?
I tryed editing override.js  smooth.rate.num and smooth.rate.den so that the result FPS is calculated exactly 60 and frc.cfg with target/tolerance at 0 , but it still produces 59.940 FPS

>the error is when some cfg options are missing which normally happens at the first run only
ah ok I put SVP on OEM installs so I'd never open it first but good to know

>it definitely works but it won't change numbers displayed in log and OSD
Yeah it still showed up as 59.940 so I will measure the actual pushed frame count to be sure.
I dont know "smooth.rate.abs", what does it do?
It does not come up in override.js by default and I also couldnt find it in your documentation.

>Are you sure your screen is exactly 60 Hz?
Yes my TV has a couple of refresh rate ranges 60.00, 59.00 - 59.99, 50 and 24.
Until now I just used this command to get it down to exactly the FPS that SVP produces.

xrandr --output HDMI-0 --mode 1920x1080 --rate 59.94

I think SVP doesn't get monitor hz output from device but just uses the reported values of OS for reresh rate so that works but not all monitors can do that so the output needs to be 60FPS output.

I tried using the "fixed frame rate at 60" option in GUI and log/OSD still shows 59.940.
Does this option also not show the correct values like with changing smooth.rate.num and den ?
Switching to "fixed rate 50"  ,75, 90 or anything else shows the correct value in the log but only fixed frame rate 60 does not. What causes this incorrect output?

> Playback [1ac0734]: playing at 60.0238 [23.976 *358/143]
I wonder how many digits after comma you tolerate?
0.238 is still a little much for me because of micro stuttering.

ok man I finished testing your tip.

smooth.rate.num            = 60;
smooth.rate.den            = 1;
smooth.rate.abs        = true;

I left everything else commented in override script to be safe.

Here output of playing 23 and 25 and 29 FPS source:

Media: video 1920x1080 [PAR 1.000] at 23.976 fps [constant] (via video player)

Playback [cf90e8d4]: playing at 59.9401 [23.976 *5/2] 

Media: video 1920x1080 [PAR 1.000] at 25.000 fps [constant] (via video player)

Playback [f9e76a81]: playing at 60 [25 *12/5]

Media: video 1920x1080 [PAR 1.000] at 29.970 fps [constant] (via video player)

Playback [258f03f3]: playing at 59.9401 [29.97 *2/1]

Only 25FPS source shows 60FPS output in log, but nothing else.
To be sure I checked actual framerate output through player and in composite manager and output was 59FPS.
You said that log/OSD shows it wrong but maybe I am missing something?