![]() |
[BUG] Incorrect range signalling - Printable Version +- Selur's Little Message Board (https://forum.selur.net) +-- Forum: Hybrid - Support (https://forum.selur.net/forum-1.html) +--- Forum: Problems & Questions (https://forum.selur.net/forum-3.html) +--- Thread: [BUG] Incorrect range signalling (/thread-3979.html) |
RE: Incorrect range signalling - r3dfx - 13.03.2025 Sorry, I wouldn't call myself an advanced user( I can't find SetMemoryMax setting. It says " Sometimes reducing this value can allow you to increase X for a speedup" on avisynth wiki... I see only Limit Cache option in Script settings This is a typical .vpy script of my job: # Imports RE: Incorrect range signalling - Selur - 13.03.2025 You are using Vapoursynth not Avisynth. ![]() And yes, the "Limit Cache"-option is basically the same. (but rarely needed) You might want to try limiting the thread count. Since your video is AVC, and LWLibavSource using hardware decoding ('Libav hardware decoding mode') might also help (or hurt the performance and handling of the source. (You could also try whether using DGDecNV or FFmpegSource2 does change things for you.) En-/Disabling OpenCL and/or DFTTest2 might also change things. Cu Selur RE: Incorrect range signalling - r3dfx - 13.03.2025 Yes, I know that I use vapoursynth. I thought QTGMC library is identical for them ![]() Thank you for the tips, will try! Unfortunately I have to wait like 30 or 40 minutes to notice a difference ![]() UPD: I can't enable DFTTest2 (always greyed out) UPD2: I tried enabling DGDecNV + OpenCL and it seems to partly fix the problem (I really hope). Unfortunately my software RAID0 on chinese SSDs (cringe, I know) isn't working well for this. Now, on 50%+ it starts oscillating between encoding and writing to disk... ![]() RE: Incorrect range signalling - Selur - 14.03.2025 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 ![]() 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:
While using software decoding with LWLibavSource and encoding, I get 73%CPU usage (no GPU usage) and ~580fps. ![]() 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 RE: Incorrect range signalling - r3dfx - 14.03.2025 (14.03.2025, 14:26)Selur Wrote: => I suspect anti virus or similar interfering on your system, did you check your taskmgr what else was running in the background? I run all my jobs parallel with regular activities like watching videos or using browser You get how much fps!? 😲 Though, yoг use Zen 4 16 core processor, while I have 8 core Zen 2( Nevertheless, these are some crazy differences, I will try other settings RE: Incorrect range signalling - Selur - 14.03.2025 Finger crossed. Funny thing about the speed is, that I usually get ~1-5fps when I encode, due to filtering. ![]() Cu Selur RE: Incorrect range signalling - r3dfx - 14.03.2025 Well, I discovered something strange: I no longer have NVENC and other GPU accelerated options... Recently I swapped my GTX1050ti for RTX3060m (yes, m) and that can potentially be the issue, although GPU accelerated sources like DGDecNV use it just fine RE: Incorrect range signalling - Selur - 14.03.2025 Starting with NVEncC 8.00 beta1, driver 452.39 or later are required, maybe your drivers are too old. try calling "NVEncC --check-features" Cu Selur RE: Incorrect range signalling - r3dfx - 14.03.2025 Well, I have 572.16, though, it a modified Nvidia driver. This is an m index chip on a pci-e card and all regular programs like OBS, Davinci Resolve are treating it as a regular 3060/3060m with full NVENC support This is how Nvidia control panel reports this GPU & driver version: UPD: latest dev doesn't start at all. Moreover, it somehow prevents process from being killed! After Initializing tabs sign, Hybrid.exe precess enters suspended state RE: Incorrect range signalling - Selur - 14.03.2025 Hybrid will do two things:
|