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.

Bought new 12700K CPU bit Hybrid only utilizes 20 percent of it
#11
Could elaborate more and give very detailed description how to do that. I really appreciate your time Smile

Hello  Im on page 2 Smile
Reply
#12
What is unclear about what I wrote?
Quote:Create a file with the Vapoursynth script that would be used during encoding and test how fast that would be processed.To do this you would (before creating the job for processing) look at the Vapoursynth Preview (to make sure any used indexing file exists and to check that the script works) and the Vapoursynth Script Preview. Then you would create a test.vpy file with the content of the script shown in the Vapoursynth Script Preview and call:"PATH TO HYBRID/64bit/Vapoursynth/VSPipe.exe" -p "PATH to the test.vpy" NUL in a Windows Command Line prompt.This will do the decoding and filtering of the source without the decoding.While the decoding is running check the cpu utilisation.If the utilisation is low then the used script is the issue. (which is either the fault of one of the filters used, the source filter or the script can't get the source faster)
If the utlilisation is high the speed you see is the max speed you can get and the bottleneck is the encoder.
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#13
I suspect its the filtering bottleneck in both vaporsynth and avisynth when doing 60 frames interpolation, so question is: whats the way rounds this then to solve the problem and uncap 20 percent and reach 100 percent CPU usage?
Reply
#14
Without knowing what exactly is causing the bottleneck there is nothing I could suggest that makes sense.
Also increasing the cpu usage doesn't mean that the processing will go higher.
Depending on the exact scripts used and the system changing the used cache and threads or using other filters might help. Bu then the issue might not be the filtering or the encoding, could be the decoding, memroy speed, the file access times, some tool interfering. Could also be an issue with the efficiency core setting of the cpu,..

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#15
Here's an example on my system,....

Decoding speed with 4k Video on my system (Rypezn 9 3950X, Geforce GTX 1070ti):
I'm using a Vappoursynth script and just VSPipe, so no encoding is happening, just the decoding and filtering.
(source parameters, format: avc, color sampling: YUV420P8, bit depth: 8, resolution: 4096x2160, fps: 25, color matrix: 2020ncl, yuv luminance scale: limited, scanorder: progressive)

Just decoding:
----------------------
Using:
LWLibavSource + hardware decoding:
clip = core.lsmas.LWLibavSource(source="G:/TestClips&Co/files/MPEG-4 H.264/4k/4k_sample_4096x2160.mp4", format="YUV420P8", cache=0, prefer_hw=1)
-> Output 6263 frames in 46.48 seconds (134.76 fps)

LWLibavSource + software decoding:
clip = core.lsmas.LWLibavSource(source="G:/TestClips&Co/files/MPEG-4 H.264/4k/4k_sample_4096x2160.mp4", format="YUV420P8", cache=0, prefer_hw=0)
-> Output 6263 frames in 56.70 seconds (110.46 fps)

LibavSMASHSource:
clip = core.lsmas.LibavSMASHSource(source="G:/TestClips&Co/files/MPEG-4 H.264/4k/4k_sample_4096x2160.mp4")
-> Output 6263 frames in 55.06 seconds (113.76 fps)

FFMS2Source:
clip = core.ffms2.Source(source="G:/TestClips&Co/files/MPEG-4 H.264/4k/4k_sample_4096x2160.mp4",cachefile="E:/Temp/mp4_b30946f06bbf6d3e0309b51cccf4cf0c_853323747.ffindex",format=vs.YUV420P8,alpha=False)
-> Output 6262 frames in 42.96 seconds (145.75 fps)

DGDecNV:
clip = core.dgdecodenv.DGSource("E:/Temp/mp4_b30946f06bbf6d3e0309b51cccf4cf0c_853323747.dgi")
-> Output 6263 frames in 38.71 seconds (161.78 fps)

Note that:
a. different source might show different speeds
b. decoding speeds can wary from run to run about 10%
c. depending on the system software decoding speeds can vary a lot
d. this is all without encoding
e. cpu usage can vary a lot

Just decoding + SVP:
----------------------
DGDecNV + SVP: (software, preset: medium, GPU: off)
clip = havsfunc.InterFrame(clip, Tuning="smooth", NewNum=60, NewDen=1) # new fps: 60
-> Output 15029 frames in 656.85 seconds (22.88 fps) (~64-85% cpu usage of VSPipe)

DGDecNV + SVP: (software, preset: medium, GPU: on)
clip = havsfunc.InterFrame(clip, Tuning="smooth", NewNum=60, NewDen=1, GPU=True) # new fps: 60
-> Output 15029 frames in 1129.21 seconds (13.31 fps) (~51-80% cpu usage of VSPipe)

FFMS2Source + SVP: (software, preset: medium, GPU: on)
clip = havsfunc.InterFrame(clip, Tuning="smooth", NewNum=60, NewDen=1, GPU=True) # new fps: 60
=> Output 15027 frames in 201.62 seconds (74.53 fps) (~30-40% cpu usage of VSPipe)

So software decoding and using SVP through the gpu gives the best speed on my system, but the cpu usage isn't that high.

Note:
1. When encoding is added things are changed up!
2. high cpu usage does not necessarily mean high speed
3. different GPU and CPU the numbers can be totally different

=> There is no: "Use this and your cpu usage and speed will be top"
Only thing you can do is check what works best on your system, by identifing bottlenecks.

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#16
Hello Selur

SOLUTION: I reinstalled from Windows 10 to Windows 11 and it seemed to have solved the problem but thank you anyway for the help and time you spent explaining things.

Thank you

Regards
Reply
#17
So it wasn't Hybrid that was causing the issue, but something that was messed up with your system settings.
-> Happy you solved the issue.

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#18
Hello again,

It seems however that CPU is only used 100 percent when converting 1080p videos but when it comes to converting to 4K@60 fps it is only used at around 30 percent and is underutilized - conversion speed is only 2 FPS per second Sad . I am not sure what is problem. also when converting 4K the whole PC becomes very laggy.
Reply
#19
Guess something wrong with you computer.

I just checked h264 1920x1080 24 video converted to 48 fps using Interframe/SVP to FFV1 codec MKV.
CPU 6 core/12 threads i7-8700K overclocked to 4.6ghz
GPU Radeon RX 580
[Image: EEhD0Ne.jpg]

GPU disabled = 88fps
GPU enabled = 79fps

Have no idea why but speed is slower when GPU enabled. Must be something not too optimized in this plugin for GPU. Enabled GPU in other plugins usually makes processing 3-5 times faster.
CPU usage in both situations is about 50% Seems plugin use all cores but can't use all threads.
Reply
#20
@4K@60FPS:
Quote:also when converting 4K the whole PC becomes very laggy.
Hmm,... system should not get laggy, since Hybrid usualy calls everything with 'idle' priority.
you might want to check:
a. to input, temp, output folders lie on different drives?
b. is there something else using the disk?

About cpu usage with 1080p:
How is the cpu usage distributed between (vspipe,encoder) when you encode 1080p and 4k?

Assuming SVP is the bottleneck, you you try tweaking the SVP parameters, read: https://www.svp-team.com/wiki/Manual:SVPflow

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)