This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

[BUG] Incorrect range signalling
#34
Deinterlacing SD content, I get a constant ~660-667fps/s with 60% CPU and 70-80% GPU. (No speed drop on 2 1/2 hour source.)
clip = qtgmc.QTGMC(Input=clip, Preset="Fast", TFF=True, opencl=True) # new fps: 50
with OpenCL and Neo enabled.
[Image: grafik.png]
DFTTest2 should be available when an NVIDIA card is detected, which should be the case. (for SD content, using DFTTest2 is a bit slower for me, speed is ~656-660fps)

During my tests, the source was located on a normal hdd and the temp folder lied on a m2s drive and I used NVEncC as encoder.


Using software encoding and:
  • Bestsource in cpu mode I only get ~140fps. (speed starts at 400 and quickly goes down)
  • Bestsource in cuda mode I get ~585fps. (speed starts slow and increases)
  • LWLibavSource in cpu mode I get ~580fps. (speed quickly hits 580fps)
  • LWLibavSource in gpu mode I get ~580fps. (speed quickly hits 580fps)
  • FFMpegSource2 I get ~590fps (speed quickly hits 590fps)
so on my setup the decoder doesn't matter much.

While using software decoding with LWLibavSource and encoding, I get 73%CPU usage (no GPU usage) and ~580fps.
[Image: grafik.png]
Speed does start up at 600fps, but the quickly settles around 580fps.

The only setup could see a slowdown was when using Bestsource in cpu mode, but even then the speed dropped quickly (after a few seconds).

=> I suspect anti virus or similar interfering on your system, did you check your taskmgr what else was running in the background?
Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply


Messages In This Thread
Incorrect range signalling - by r3dfx - 23.01.2025, 13:01
RE: Incorrect range signalling - by Selur - 23.01.2025, 16:15
RE: Incorrect range signalling - by r3dfx - 23.01.2025, 16:30
RE: Incorrect range signalling - by Selur - 23.01.2025, 16:44
RE: Incorrect range signalling - by Selur - 23.01.2025, 18:17
RE: Incorrect range signalling - by r3dfx - 23.01.2025, 18:40
RE: Incorrect range signalling - by Selur - 23.01.2025, 18:42
RE: Incorrect range signalling - by r3dfx - 23.01.2025, 20:08
RE: Incorrect range signalling - by r3dfx - 10.02.2025, 20:55
RE: Incorrect range signalling - by Selur - 10.02.2025, 21:01
RE: Incorrect range signalling - by r3dfx - 10.02.2025, 23:49
RE: Incorrect range signalling - by Selur - 11.02.2025, 04:26
RE: Incorrect range signalling - by r3dfx - 11.02.2025, 12:28
RE: Incorrect range signalling - by Selur - 11.02.2025, 19:04
RE: Incorrect range signalling - by r3dfx - 05.03.2025, 18:01
RE: Incorrect range signalling - by Selur - 05.03.2025, 18:09
RE: Incorrect range signalling - by Selur - 05.03.2025, 18:10
RE: Incorrect range signalling - by Selur - 05.03.2025, 18:46
RE: Incorrect range signalling - by r3dfx - 05.03.2025, 19:52
RE: Incorrect range signalling - by Selur - 05.03.2025, 21:09
RE: Incorrect range signalling - by r3dfx - 05.03.2025, 21:44
RE: Incorrect range signalling - by Selur - 05.03.2025, 22:08
RE: Incorrect range signalling - by r3dfx - 11.03.2025, 23:05
RE: Incorrect range signalling - by Selur - 12.03.2025, 06:10
RE: Incorrect range signalling - by r3dfx - Yesterday, 17:11
RE: Incorrect range signalling - by Selur - Yesterday, 18:30
RE: Incorrect range signalling - by r3dfx - Yesterday, 19:04
RE: Incorrect range signalling - by Selur - Yesterday, 19:19
RE: Incorrect range signalling - by r3dfx - Yesterday, 19:53
RE: Incorrect range signalling - by Selur - Yesterday, 20:01
RE: Incorrect range signalling - by r3dfx - Yesterday, 20:44
RE: Incorrect range signalling - by Selur - Yesterday, 21:38
RE: Incorrect range signalling - by r3dfx - Yesterday, 22:10
RE: Incorrect range signalling - by Selur - 6 hours ago

Forum Jump:


Users browsing this thread: r3dfx, Selur, 3 Guest(s)