Topic: Howto setup MPC-HC with SVP + RifeAI + MadVR ?

I deleted everything, even installed windows from scratch, but i dont find the correct way how to do it.

I searched and i think i have to set environment variables for vapoursynth, but i cannot see where ? The tools menu offers VLC and libmpv but not vapoursynth.

To combine this with MadVR i think step 1 madvr and the final picture through rife. Should be faster than the other way around.
And if this is working .. the final step would be to use this with videoprocessor.org -> like a videoprocessor, through anything in and do tonemapping etc + frame interpolation and throw it out smile

Who can help me setting up a player ?

Thanks a lot - Discord, Whatsapp, Telegram, Teamviewer ... whatever is needed

Re: Howto setup MPC-HC with SVP + RifeAI + MadVR ?

> The tools menu offers VLC and libmpv but not vapoursynth.

did you clicked that one?

Re: Howto setup MPC-HC with SVP + RifeAI + MadVR ?

yes - confirmed the upcoming message that it will modify path values etc -> started mpc-hc
then i started a movie ->

16:36:13.597 : AVSF: found new player instance
16:36:13.618 : AVSF: filters in use: LAV Splitter Source (internal) -> LAV Video Decoder (internal) -> * -> madVR
16:36:13.619 : AVSF: new video in mpc-hc64.exe (64-bit) [MPC-HC 1.9.24.0] on screen 0
16:36:13.663 : Media: video 3840x2160 [PAR 1.000] at 23.976 fps
16:36:13.663 : Media: codec type is HEVC, YUV/4:2:0/10 bits/BT.2020 PQ
16:36:13.664 : Playback: starting up...
16:36:13.667 : Playback [46781507]: Frame server (64-bit) 3.5.0.0, 3106, AviSynth+ 3.5 (r3106, 3.5, x86_64), C:\Windows\SYSTEM32\avisynth.dll
16:36:13.668 : Playback [46781507]: resulting video frame 2560x1440 [3840x2160 -> scaled -> 2560x1440]
16:36:13.668 : Playback [46781507]: 1 acceptible profiles, best is 'Automatisch' [0]
16:36:13.669 : Playback [46781507]: enabled while video is playing
16:36:13.670 : Profile: using automatic profile #1 /film
16:36:13.672 : Playback [46781507]: playing at 59.94 [23.976 *5/2] /10 bit
16:36:13.706 [W]: Control: failed to register shortcut Meta+Alt+K
16:36:15.505 : Playback [46781507]: black fields changed to TB: 276-276, LR: 0-0
16:36:15.506 : Playback [46781507]: resulting video frame 2560x1072 [3840x2160 -> cropped -> 3840x1608 -> scaled -> 2560x1072]
16:36:15.506 : Playback [46781507]: 1 acceptible profiles, best is 'Automatisch' [0]
16:36:15.506 : Playback [46781507]: keep previously selected profile 'Automatisch'
16:36:15.507 : Profile: using automatic profile #1 /film
16:36:15.510 : Playback [46781507]: playing at 59.94 [23.976 *5/2] /10 bit
16:36:18.127 : Playback [46781507]: switching to profile 'RIFE AI engine'
16:36:18.129 : Playback [46781507]: playing at 47.952 [23.976 *2/1] /10 bit
16:36:18.369  : Playback [46781507]: AVS - RIFE: failed to load model\n(C:\Users\patri\AppData\Roaming\SVP4\scripts\46781507.avs, line 62)\n(C:\Users\patri\AppData\Roaming\SVP4\scripts\46781507.avs, line 77)

based on the other thread -> it is using avisynth and not vapoursynth. So i disabled avisynth, added vapoursynth as external filter and enabled remote control .. but then SVP does not recognize the player. do you need logs or screenshot ?

4 (edited by jcflores 11-01-2023 17:15:07)

Re: Howto setup MPC-HC with SVP + RifeAI + MadVR ?

I'm trying out RIFE and I'm having problems following the tutorial here: https://www.svp-team.com/forum/viewtopi … 483#p81483

This may sound dumb but I can't find the option to enable it in the MPC options.
Also whenever I try to play any video via MPC with the RIFE AI profile, the result will always be black & white video with out-of-sync audio. Please help.

Thanks in advance.

Re: Howto setup MPC-HC with SVP + RifeAI + MadVR ?

grobalt
> but then SVP does not recognize the player. do you need logs or screenshot ?

if something is not working then looking through the log is a good idea!

jcflores
>  the result will always be black & white video

https://www.svp-team.com/wiki/RIFE_AI_i … n#Problems

still, TensorRT WON'T WORK VIA AVISYNTH!!!

Re: Howto setup MPC-HC with SVP + RifeAI + MadVR ?

grobalt wrote:

yes - confirmed the upcoming message that it will modify path values etc -> started mpc-hc
then i started a movie ->

16:36:13.597 : AVSF: found new player instance
16:36:13.618 : AVSF: filters in use: LAV Splitter Source (internal) -> LAV Video Decoder (internal) -> * -> madVR
16:36:13.619 : AVSF: new video in mpc-hc64.exe (64-bit) [MPC-HC 1.9.24.0] on screen 0
16:36:13.663 : Media: video 3840x2160 [PAR 1.000] at 23.976 fps
16:36:13.663 : Media: codec type is HEVC, YUV/4:2:0/10 bits/BT.2020 PQ
16:36:13.664 : Playback: starting up...
16:36:13.667 : Playback [46781507]: Frame server (64-bit) 3.5.0.0, 3106, AviSynth+ 3.5 (r3106, 3.5, x86_64), C:\Windows\SYSTEM32\avisynth.dll
16:36:13.668 : Playback [46781507]: resulting video frame 2560x1440 [3840x2160 -> scaled -> 2560x1440]
16:36:13.668 : Playback [46781507]: 1 acceptible profiles, best is 'Automatisch' [0]
16:36:13.669 : Playback [46781507]: enabled while video is playing
16:36:13.670 : Profile: using automatic profile #1 /film
16:36:13.672 : Playback [46781507]: playing at 59.94 [23.976 *5/2] /10 bit

16:36:13.706 [W]: Control: failed to register shortcut Meta+Alt+K
16:36:15.505 : Playback [46781507]: black fields changed to TB: 276-276, LR: 0-0
16:36:15.506 : Playback [46781507]: resulting video frame 2560x1072 [3840x2160 -> cropped -> 3840x1608 -> scaled -> 2560x1072]
16:36:15.506 : Playback [46781507]: 1 acceptible profiles, best is 'Automatisch' [0]
16:36:15.506 : Playback [46781507]: keep previously selected profile 'Automatisch'
16:36:15.507 : Profile: using automatic profile #1 /film
16:36:15.510 : Playback [46781507]: playing at 59.94 [23.976 *5/2] /10 bit
16:36:18.127 : Playback [46781507]: switching to profile 'RIFE AI engine'
16:36:18.129 : Playback [46781507]: playing at 47.952 [23.976 *2/1] /10 bit
16:36:18.369  : Playback [46781507]: AVS - RIFE: failed to load model\n(C:\Users\patri\AppData\Roaming\SVP4\scripts\46781507.avs, line 62)\n(C:\Users\patri\AppData\Roaming\SVP4\scripts\46781507.avs, line 77)

based on the other thread -> it is using avisynth and not vapoursynth. So i disabled avisynth, added vapoursynth as external filter and enabled remote control .. but then SVP does not recognize the player. do you need logs or screenshot ?

Im on the same bote, what do we need to do for mpc-hc +rife profile work properly like it thus with MPV

Re: Howto setup MPC-HC with SVP + RifeAI + MadVR ?

i cleaned up the logs and everything again smile

additional some (maybe useful) information

C:\Users\patri>python
Python 3.10.9 (main, Dec 22 2022, 16:59:33) [MSC v.1934 64 bit (AMD64)] on win32
>>> import vapoursynth
>>> print(vapoursynth.core.version())
VapourSynth Video Processing Library
Copyright (c) 2012-2022 Fredrik Mellbin
Core R61
API R4.0
API R3.6
Options: -

>>>

Post's attachments

active.log 5.06 kb, 261 downloads since 2023-01-11 

avisynth.png 79.54 kb, 65 downloads since 2023-01-11 

VapourSynth.png 63.73 kb, 67 downloads since 2023-01-11 

Re: Howto setup MPC-HC with SVP + RifeAI + MadVR ?

why the hell you have both filters enabled?

> Unable to initialize Vapousynrh API 4.0

dunno, maybe you have some older Vapoursynth version installed somewhere?

Re: Howto setup MPC-HC with SVP + RifeAI + MadVR ?

i tried alone as well, no difference, same behaviour.

Re: Howto setup MPC-HC with SVP + RifeAI + MadVR ?

as said .. fresh windows installation from this afternoon smile

Re: Howto setup MPC-HC with SVP + RifeAI + MadVR ?

I really don't know what to do to get this error

Re: Howto setup MPC-HC with SVP + RifeAI + MadVR ?

If you have any vapoursynth installed, you should uninstall it first.

1. install SVP
2. set environment and restart the PC
https://cdn.discordapp.com/attachments/290709370600423424/1062837335210860665/image.png

3. go to C:\Program Files (x86)\SVP 4\avsf and right click on register.bat and run as admin (to register vapoursynth filter)
4. add vapoursynth to MPC, if vapoursynth filter does not pop up the setting windows it's means something wrong with your vapoursynth setup.
https://cdn.discordapp.com/attachments/290709370600423424/1062837737130049587/image.png

Re: Howto setup MPC-HC with SVP + RifeAI + MadVR ?

aloola wrote:

If you have any vapoursynth installed, you should uninstall it first.

3. go to C:\Program Files (x86)\SVP 4\avsf and right click on register.bat and run as admin (to register vapoursynth filter)

Thanks Aloola this to steps fix the problems. I feel stupid for forget to do the step 3.

Re: Howto setup MPC-HC with SVP + RifeAI + MadVR ?

Thanks, something was odd, now i can access the vapoursynth menü in mpc-hc.
All boxes are check, remote control is enabled but SVP does not detect that a clip is running.

15 (edited by aloola 11-01-2023 23:24:25)

Re: Howto setup MPC-HC with SVP + RifeAI + MadVR ?

have you set vapour filter prefer yet?
https://cdn.discordapp.com/attachments/290709370600423424/1062874317597184040/image.png

also right click on MPC is there any vapoursynth filter running?
https://cdn.discordapp.com/attachments/290709370600423424/1062874544240594974/image.png

16 (edited by grobalt 11-01-2023 23:32:51)

Re: Howto setup MPC-HC with SVP + RifeAI + MadVR ?

yes ... ok, so if i set this a restart of mpc-hc is not good enough, SVP4 needs a restart as well .. progress, many thanks smile

ok, now working .. how can i figure out if madvr is the first "process" or svp ?

Re: Howto setup MPC-HC with SVP + RifeAI + MadVR ?

Now that I was able to enable vapoursynth whit MPC-HC, does it make any sense to use other profiles? I'm trying and I don't know if I have a serious case of placebo effect or it looks better, adding to the question does the TensorTRT option do something in this context? . Using another profile that is not RIFE.
Cons and Pros to used instead of AviSynth Filter

Post's attachments

MPC-HC+VAPOURSYNTH+MADVR.jpg 324.37 kb, 72 downloads since 2023-01-11 

Re: Howto setup MPC-HC with SVP + RifeAI + MadVR ?

Drakko01 wrote:

Now that I was able to enable vapoursynth whit MPC-HC, does it make any sense to use other profiles? I'm trying and I don't know if I have a serious case of placebo effect or it looks better, adding to the question does the TensorTRT option do something in this context? . Using another profile that is not RIFE.
Cons and Pros to used instead of AviSynth Filter

your profile is wrong
you should follow the guide
https://www.svp-team.com/forum/viewtopi … 483#p81483

https://cdn.discordapp.com/attachments/290709370600423424/1062949400957165598/image.png
should be look like this.

Re: Howto setup MPC-HC with SVP + RifeAI + MadVR ?

I think AI model has to be "rife" as well for the newest script or am i wrong ?

20 (edited by Drakko01 12-01-2023 11:49:39)

Re: Howto setup MPC-HC with SVP + RifeAI + MadVR ?

aloola wrote:
Drakko01 wrote:

Now that I was able to enable vapoursynth whit MPC-HC, does it make any sense to use other profiles? I'm trying and I don't know if I have a serious case of placebo effect or it looks better, adding to the question does the TensorTRT option do something in this context? . Using another profile that is not RIFE.
Cons and Pros to used instead of AviSynth Filter

your profile is wrong

My profile is not wrong. You didn't understand what I meant, I was talking about using other profiles apart from RiFE, and if the Tensort TRT option did anything for the other profiles. Besides that, if there was any point in using VapourSynth instead of AviSynth,for the other profiles.

Post's attachments

Play_RiFE_ok.jpg, 88.38 kb, 640 x 454
Play_RiFE_ok.jpg 88.38 kb, 145 downloads since 2023-01-12 

RiFE Profile_ok.jpg, 70.66 kb, 526 x 624
RiFE Profile_ok.jpg 70.66 kb, 153 downloads since 2023-01-12 

Re: Howto setup MPC-HC with SVP + RifeAI + MadVR ?

> and if the Tensort TRT option did anything for the other profiles. Besides that, if there was any point in using VapourSynth instead of AviSynth,for the other profiles.

no and no

Re: Howto setup MPC-HC with SVP + RifeAI + MadVR ?

OK Chainik, with other profiles I will use Avisynth then, thanks

Re: Howto setup MPC-HC with SVP + RifeAI + MadVR ?

there is no point in using VapourSynth instead of AviSynth <=> there is no point in using Avisynth instead of Vapoursynth

Avisynth is easier to install and use cause it doesn't need all these "environment variables", this's why it's the default engine
however if you already have Vapoursynth stuff up and ready then just use it

Re: Howto setup MPC-HC with SVP + RifeAI + MadVR ?

>there is no point in using VapourSynth instead of AviSynth <=> there is no point in using Avisynth instead of Vapoursynth


Ok, I see, thanks for the clarification. I asked the question because I never had  VapourSynth working with MPC and I always try to find the best way.Better smoothness fewer fewer artifacts, etc
According to the above, neither  is better or worse than the other or is there any benefit using one over the other. Leaving aside the gpu load

25 (edited by onurco 18-01-2023 23:48:23)

Re: Howto setup MPC-HC with SVP + RifeAI + MadVR ?

I have a high end computer with 12900K and rtx 4090. I was using ncnn/Vulkan with no issues with Vapoursynth. However I updated SVP today and tried the new NVIDIA TensorRT and when I activate it, command line appears on the screen and the video freezes as black screen. I waited 10 minutes but nothing happened. Then I tried to close the command line 3 times as it appears again, then MPC-HC wrote error message on the screen.

I checked the log in the error message and I am posting here what is in the log:

&&&& RUNNING TensorRT.trtexec [TensorRT v8501] # C:/Program Files (x86)/SVP 4/rife\vsmlrt-cuda\trtexec --onnx=C:/Program Files (x86)/SVP 4/rife\models\rife\rife_v4.6.onnx --timingCacheFile=C:\Users\onurco\AppData\Roaming\SVP4\cache\Program Files (x86)/SVP 4/rife\models\rife\rife_v4.6.onnx.1920x1088_fp16_trt-8502_cudnn_I-fp16_O-fp16_NVIDIA-GeForce-RTX-4090_3dcbe72f.engine.cache --device=0 --saveEngine=C:\Users\onurco\AppData\Roaming\SVP4\cache\Program Files (x86)/SVP 4/rife\models\rife\rife_v4.6.onnx.1920x1088_fp16_trt-8502_cudnn_I-fp16_O-fp16_NVIDIA-GeForce-RTX-4090_3dcbe72f.engine --shapes=input:1x11x1088x1920 --fp16 --tacticSources=-CUBLAS,-CUBLAS_LT --useCudaGraph --noDataTransfers --inputIOFormats=fp16:chw --outputIOFormats=fp16:chw
[01/19/2023-02:27:19] [i] === Model Options ===
[01/19/2023-02:27:19] [i] Format: ONNX
[01/19/2023-02:27:19] [i] Model: C:/Program Files (x86)/SVP 4/rife\models\rife\rife_v4.6.onnx
[01/19/2023-02:27:19] [i] Output:
[01/19/2023-02:27:19] [i] === Build Options ===
[01/19/2023-02:27:19] [i] Max batch: explicit batch
[01/19/2023-02:27:19] [i] Memory Pools: workspace: default, dlaSRAM: default, dlaLocalDRAM: default, dlaGlobalDRAM: default
[01/19/2023-02:27:19] [i] minTiming: 1
[01/19/2023-02:27:19] [i] avgTiming: 8
[01/19/2023-02:27:19] [i] Precision: FP32+FP16
[01/19/2023-02:27:19] [i] LayerPrecisions: 
[01/19/2023-02:27:19] [i] Calibration: 
[01/19/2023-02:27:19] [i] Refit: Disabled
[01/19/2023-02:27:19] [i] Sparsity: Disabled
[01/19/2023-02:27:19] [i] Safe mode: Disabled
[01/19/2023-02:27:19] [i] DirectIO mode: Disabled
[01/19/2023-02:27:19] [i] Restricted mode: Disabled
[01/19/2023-02:27:19] [i] Build only: Disabled
[01/19/2023-02:27:19] [i] Save engine: C:\Users\onurco\AppData\Roaming\SVP4\cache\Program Files (x86)/SVP 4/rife\models\rife\rife_v4.6.onnx.1920x1088_fp16_trt-8502_cudnn_I-fp16_O-fp16_NVIDIA-GeForce-RTX-4090_3dcbe72f.engine
[01/19/2023-02:27:19] [i] Load engine: 
[01/19/2023-02:27:19] [i] Profiling verbosity: 0
[01/19/2023-02:27:19] [i] Tactic sources: cublas [OFF], cublasLt [OFF], 
[01/19/2023-02:27:19] [i] timingCacheMode: global
[01/19/2023-02:27:19] [i] timingCacheFile: C:\Users\onurco\AppData\Roaming\SVP4\cache\Program Files (x86)/SVP 4/rife\models\rife\rife_v4.6.onnx.1920x1088_fp16_trt-8502_cudnn_I-fp16_O-fp16_NVIDIA-GeForce-RTX-4090_3dcbe72f.engine.cache
[01/19/2023-02:27:19] [i] Heuristic: Disabled
[01/19/2023-02:27:19] [i] Preview Features: Use default preview flags.
[01/19/2023-02:27:19] [i] Input(s): fp16:chw
[01/19/2023-02:27:19] [i] Output(s): fp16:chw
[01/19/2023-02:27:19] [i] Input build shape: input=1x11x1088x1920+1x11x1088x1920+1x11x1088x1920
[01/19/2023-02:27:19] [i] Input calibration shapes: model
[01/19/2023-02:27:19] [i] === System Options ===
[01/19/2023-02:27:19] [i] Device: 0
[01/19/2023-02:27:19] [i] DLACore: 
[01/19/2023-02:27:19] [i] Plugins:
[01/19/2023-02:27:19] [i] === Inference Options ===
[01/19/2023-02:27:19] [i] Batch: Explicit
[01/19/2023-02:27:19] [i] Input inference shape: input=1x11x1088x1920
[01/19/2023-02:27:19] [i] Iterations: 10
[01/19/2023-02:27:19] [i] Duration: 3s (+ 200ms warm up)
[01/19/2023-02:27:19] [i] Sleep time: 0ms
[01/19/2023-02:27:19] [i] Idle time: 0ms
[01/19/2023-02:27:19] [i] Streams: 1
[01/19/2023-02:27:19] [i] ExposeDMA: Disabled
[01/19/2023-02:27:19] [i] Data transfers: Disabled
[01/19/2023-02:27:19] [i] Spin-wait: Disabled
[01/19/2023-02:27:19] [i] Multithreading: Disabled
[01/19/2023-02:27:19] [i] CUDA Graph: Enabled
[01/19/2023-02:27:19] [i] Separate profiling: Disabled
[01/19/2023-02:27:19] [i] Time Deserialize: Disabled
[01/19/2023-02:27:19] [i] Time Refit: Disabled
[01/19/2023-02:27:19] [i] NVTX verbosity: 0
[01/19/2023-02:27:19] [i] Persistent Cache Ratio: 0
[01/19/2023-02:27:19] [i] Inputs:
[01/19/2023-02:27:19] [i] === Reporting Options ===
[01/19/2023-02:27:19] [i] Verbose: Disabled
[01/19/2023-02:27:19] [i] Averages: 10 inferences
[01/19/2023-02:27:19] [i] Percentiles: 90,95,99
[01/19/2023-02:27:19] [i] Dump refittable layers:Disabled
[01/19/2023-02:27:19] [i] Dump output: Disabled
[01/19/2023-02:27:19] [i] Profile: Disabled
[01/19/2023-02:27:19] [i] Export timing to JSON file: 
[01/19/2023-02:27:19] [i] Export output to JSON file: 
[01/19/2023-02:27:19] [i] Export profile to JSON file: 
[01/19/2023-02:27:19] [i] 
[01/19/2023-02:27:19] [i] === Device Information ===
[01/19/2023-02:27:19] [i] Selected Device: NVIDIA GeForce RTX 4090
[01/19/2023-02:27:19] [i] Compute Capability: 8.9
[01/19/2023-02:27:19] [i] SMs: 128
[01/19/2023-02:27:19] [i] Compute Clock Rate: 2.58 GHz
[01/19/2023-02:27:19] [i] Device Global Memory: 24563 MiB
[01/19/2023-02:27:19] [i] Shared Memory per SM: 100 KiB
[01/19/2023-02:27:19] [i] Memory Bus Width: 384 bits (ECC disabled)
[01/19/2023-02:27:19] [i] Memory Clock Rate: 10.501 GHz
[01/19/2023-02:27:19] [i] 
[01/19/2023-02:27:19] [i] TensorRT version: 8.5.1
[01/19/2023-02:27:20] [i] [TRT] [MemUsageChange] Init CUDA: CPU +436, GPU +0, now: CPU 13780, GPU 1771 (MiB)

My Vapoursynth version is Vapoursynth Filter v1.4.5 # svp with Vapoursynth R61 API R4.0
If anybody could point me about what to do, I would be really glad.

Also I am adding here what was written in the command line:

&&&& RUNNING TensorRT.trtexec [TensorRT v8501] # C:/Program Files (x86)/SVP 4/rife\vsmlrt-cuda\trtexec --onnx=C:/Program Files (x86)/SVP 4/rife\models\rife\rife_v4.6.onnx --timingCacheFile=C:\Users\onurco\AppData\Roaming\SVP4\cache\Program Files (x86)/SVP 4/rife\models\rife\rife_v4.6.onnx.1920x832_fp16_trt-8502_cudnn_I-fp16_O-fp16_NVIDIA-GeForce-RTX-4090_3dcbe72f.engine.cache --device=0 --saveEngine=C:\Users\onurco\AppData\Roaming\SVP4\cache\Program Files (x86)/SVP 4/rife\models\rife\rife_v4.6.onnx.1920x832_fp16_trt-8502_cudnn_I-fp16_O-fp16_NVIDIA-GeForce-RTX-4090_3dcbe72f.engine --shapes=input:1x11x832x1920 --fp16 --tacticSources=-CUBLAS,-CUBLAS_LT --useCudaGraph --noDataTransfers --inputIOFormats=fp16:chw --outputIOFormats=fp16:chw
[01/19/2023-02:47:37] [i] === Model Options ===
[01/19/2023-02:47:37] [i] Format: ONNX
[01/19/2023-02:47:37] [i] Model: C:/Program Files (x86)/SVP 4/rife\models\rife\rife_v4.6.onnx
[01/19/2023-02:47:37] [i] Output:
[01/19/2023-02:47:37] [i] === Build Options ===
[01/19/2023-02:47:37] [i] Max batch: explicit batch
[01/19/2023-02:47:37] [i] Memory Pools: workspace: default, dlaSRAM: default, dlaLocalDRAM: default, dlaGlobalDRAM: default
[01/19/2023-02:47:37] [i] minTiming: 1
[01/19/2023-02:47:37] [i] avgTiming: 8
[01/19/2023-02:47:37] [i] Precision: FP32+FP16
[01/19/2023-02:47:37] [i] LayerPrecisions:
[01/19/2023-02:47:37] [i] Calibration:
[01/19/2023-02:47:37] [i] Refit: Disabled
[01/19/2023-02:47:37] [i] Sparsity: Disabled
[01/19/2023-02:47:37] [i] Safe mode: Disabled
[01/19/2023-02:47:37] [i] DirectIO mode: Disabled
[01/19/2023-02:47:37] [i] Restricted mode: Disabled
[01/19/2023-02:47:37] [i] Build only: Disabled
[01/19/2023-02:47:37] [i] Save engine: C:\Users\onurco\AppData\Roaming\SVP4\cache\Program Files (x86)/SVP 4/rife\models\rife\rife_v4.6.onnx.1920x832_fp16_trt-8502_cudnn_I-fp16_O-fp16_NVIDIA-GeForce-RTX-4090_3dcbe72f.engine
[01/19/2023-02:47:37] [i] Load engine:
[01/19/2023-02:47:37] [i] Profiling verbosity: 0
[01/19/2023-02:47:37] [i] Tactic sources: cublas [OFF], cublasLt [OFF],
[01/19/2023-02:47:37] [i] timingCacheMode: global
[01/19/2023-02:47:37] [i] timingCacheFile: C:\Users\onurco\AppData\Roaming\SVP4\cache\Program Files (x86)/SVP 4/rife\models\rife\rife_v4.6.onnx.1920x832_fp16_trt-8502_cudnn_I-fp16_O-fp16_NVIDIA-GeForce-RTX-4090_3dcbe72f.engine.cache
[01/19/2023-02:47:37] [i] Heuristic: Disabled
[01/19/2023-02:47:37] [i] Preview Features: Use default preview flags.
[01/19/2023-02:47:37] [i] Input(s): fp16:chw
[01/19/2023-02:47:37] [i] Output(s): fp16:chw
[01/19/2023-02:47:37] [i] Input build shape: input=1x11x832x1920+1x11x832x1920+1x11x832x1920
[01/19/2023-02:47:37] [i] Input calibration shapes: model
[01/19/2023-02:47:37] [i] === System Options ===
[01/19/2023-02:47:37] [i] Device: 0
[01/19/2023-02:47:37] [i] DLACore:
[01/19/2023-02:47:37] [i] Plugins:
[01/19/2023-02:47:37] [i] === Inference Options ===
[01/19/2023-02:47:37] [i] Batch: Explicit
[01/19/2023-02:47:37] [i] Input inference shape: input=1x11x832x1920
[01/19/2023-02:47:37] [i] Iterations: 10
[01/19/2023-02:47:37] [i] Duration: 3s (+ 200ms warm up)
[01/19/2023-02:47:37] [i] Sleep time: 0ms
[01/19/2023-02:47:37] [i] Idle time: 0ms
[01/19/2023-02:47:37] [i] Streams: 1
[01/19/2023-02:47:37] [i] ExposeDMA: Disabled
[01/19/2023-02:47:37] [i] Data transfers: Disabled
[01/19/2023-02:47:37] [i] Spin-wait: Disabled
[01/19/2023-02:47:37] [i] Multithreading: Disabled
[01/19/2023-02:47:37] [i] CUDA Graph: Enabled
[01/19/2023-02:47:37] [i] Separate profiling: Disabled
[01/19/2023-02:47:37] [i] Time Deserialize: Disabled
[01/19/2023-02:47:37] [i] Time Refit: Disabled
[01/19/2023-02:47:37] [i] NVTX verbosity: 0
[01/19/2023-02:47:37] [i] Persistent Cache Ratio: 0
[01/19/2023-02:47:37] [i] Inputs:
[01/19/2023-02:47:37] [i] === Reporting Options ===
[01/19/2023-02:47:37] [i] Verbose: Disabled
[01/19/2023-02:47:37] [i] Averages: 10 inferences
[01/19/2023-02:47:37] [i] Percentiles: 90,95,99
[01/19/2023-02:47:37] [i] Dump refittable layers:Disabled
[01/19/2023-02:47:37] [i] Dump output: Disabled
[01/19/2023-02:47:37] [i] Profile: Disabled
[01/19/2023-02:47:37] [i] Export timing to JSON file:
[01/19/2023-02:47:37] [i] Export output to JSON file:
[01/19/2023-02:47:37] [i] Export profile to JSON file:
[01/19/2023-02:47:37] [i]
[01/19/2023-02:47:37] [i] === Device Information ===
[01/19/2023-02:47:37] [i] Selected Device: NVIDIA GeForce RTX 4090
[01/19/2023-02:47:37] [i] Compute Capability: 8.9
[01/19/2023-02:47:37] [i] SMs: 128
[01/19/2023-02:47:37] [i] Compute Clock Rate: 2.58 GHz
[01/19/2023-02:47:37] [i] Device Global Memory: 24563 MiB
[01/19/2023-02:47:37] [i] Shared Memory per SM: 100 KiB
[01/19/2023-02:47:37] [i] Memory Bus Width: 384 bits (ECC disabled)
[01/19/2023-02:47:37] [i] Memory Clock Rate: 10.501 GHz
[01/19/2023-02:47:37] [i]
[01/19/2023-02:47:37] [i] TensorRT version: 8.5.1
[01/19/2023-02:47:38] [i] [TRT] [MemUsageChange] Init CUDA: CPU +448, GPU +0, now: CPU 13279, GPU 1771 (MiB)
[01/19/2023-02:47:39] [i] [TRT] [MemUsageChange] Init builder kernel library: CPU +430, GPU +116, now: CPU 14166, GPU 1887 (MiB)
[01/19/2023-02:47:39] [W] [TRT] CUDA lazy loading is not enabled. Enabling it can significantly reduce device memory usage. See `CUDA_MODULE_LOADING` in https://docs.nvidia.com/cuda/cuda-c-programming-guide/index.html#env-vars
[01/19/2023-02:47:39] [i] Start parsing network model
[01/19/2023-02:47:39] [i] [TRT] ----------------------------------------------------------------
[01/19/2023-02:47:39] [i] [TRT] Input filename:   C:/Program Files (x86)/SVP 4/rife\models\rife\rife_v4.6.onnx
[01/19/2023-02:47:39] [i] [TRT] ONNX IR version:  0.0.8
[01/19/2023-02:47:39] [i] [TRT] Opset version:    16
[01/19/2023-02:47:39] [i] [TRT] Producer name:    pytorch
[01/19/2023-02:47:39] [i] [TRT] Producer version: 1.12.0
[01/19/2023-02:47:39] [i] [TRT] Domain:
[01/19/2023-02:47:39] [i] [TRT] Model version:    0
[01/19/2023-02:47:39] [i] [TRT] Doc string:
[01/19/2023-02:47:39] [i] [TRT] ----------------------------------------------------------------
[01/19/2023-02:47:39] [W] [TRT] onnx2trt_utils.cpp:377: Your ONNX model has been generated with INT64 weights, while TensorRT does not natively support INT64. Attempting to cast down to INT32.
[01/19/2023-02:47:39] [i] Finish parsing network model
[01/19/2023-02:47:39] [W] Could not read timing cache from: C:\Users\onurco\AppData\Roaming\SVP4\cache\Program Files (x86)/SVP 4/rife\models\rife\rife_v4.6.onnx.1920x832_fp16_trt-8502_cudnn_I-fp16_O-fp16_NVIDIA-GeForce-RTX-4090_3dcbe72f.engine.cache. A new timing cache will be generated and written.
[01/19/2023-02:47:40] [i] [TRT] [MemUsageChange] Init cuDNN: CPU +1083, GPU +406, now: CPU 14928, GPU 2293 (MiB)
[01/19/2023-02:47:40] [i] [TRT] Global timing cache in use. Profiling results in this builder pass will be stored.
Post's attachments

Screenshot 2023-01-19 022812.jpg 199.17 kb, 77 downloads since 2023-01-18