I've - just given up on re-installing SVP. Just doesn't work on my machine. It worked last time though, and I think there might be something fishy going on in the code regarding VM-Detection. Or it's just the lack of a physical GPU that's bothering the SVP Manager at startup. Either way it would require me to take a way more complicated approach than I would get with FlowFrames at the moment. Still, it isn't ideal, updating as a non-paying user also takes about half an hour which isn't great either. So I'll leave it be for now.
As for 4.6, I've just tested it with some black and white scenes and though I didn't compare to 4.4, it looks a lot better than v4. B&w seems to be really difficult for interpolation as it doesn't know where that specific dark spot came from, from above or from the side etc., whereas before it could just tell them apart by color.

Back to the original question: Since I think the same AI fed with the same image sequence will always return the same output, maybe cut out that scene, use a different RIFE version und paste it back in? A little complicated, I know, or you could just concede and stick with v4.4 for the whole movie? To me it doesn't look like a technical issue with neither SVP nor RIFE AI, just that the training data is always a bit different and sometimes just gets worse with an update in some areas. And v4.4 isn't vaaastly inferior to v4.6 imo...

Also, I'm well aware this is not a FlowFrames troubleshooting forum, but I'd be happy to help there if needed :)

For me it was that every second frame was black, as in pitch-black, RGB #000000. I sadly don't have the video at hand anymore, wasn't worth the storage big_smile

This only happens with Gravity? You might want to try another RIFE-model, the most recent is v4.6 (afaik not in the current version of SVP), other good ones are plain v4 and v2.3. I'm not entirely sure if you have all these options, I'll probably have to spin up a VM and look which options are available.
Just for reference, you could also try Flowframes for once, the most recent precompiled version seems to already include RIFE AI v4. I'm not sure if 'recommending' competitors goes well here, so we'll see XD

Also I'm rate limited here, so I'm sorry my responses come in so slow... 2h/reply apparently

Also quick note since there is no button to close a topic, I successfully moved on to Flowframes. I know it's been more than a year now, but I just want to say that no further assistance is required (though there was none yet to speak of tbh).

Flowframes it is now. It's much easier to install, has to be compiled by Visual Studio once and then just works from this point on. SVP struggled a bit with everything, installing was complicated, on my native Windows it had issues running correctly, in a VM things were running a bit better but was a bit more difficult to install (I think at some point it wants to read the CPU core count and fails because it's virtual after all, and of course no useful error message), Linux didn't have the feature at the time and aaahh it was a tough time. I did get out a few videos with Vaporsynth which were quite good in the beginning, and as I said in the previous reply, I got RIFE to work eventually and it looked really good, so - yes. Things might be different now and I would still recommend SVP as an interpolation program for beginners, while FF is more for the tech-savvy.

Cheers!

A little update on my side: The only configuration that seems to work well is:
(AI Model: not tested, only used generic)
TTA: disabled
(Floating Point: no difference)
GPU Threads: 1 (2 caused issues, 4 and 6 failed directly after start)
GPU device: id0

Should I file a bug report for the configurations that are not working?

Cheers

Hi everyone!
I don't know where to start, so let me just start with the background.
I recently switched from using Linux to using Windows for SVP (Evaluation version). The reason I switched to Windows is pretty easily explained, RIFE needs version 210 which is not yet on Linux, and after I tried it on a Windows VM, it explained me it needed a GPU with Vulkan API which VMWare failed to provide. After spending hours gaining that knowledge, I installed Windows on a free partition and SVP installed without any issues. Also: The normal vapoursynth (non-RIFE) script never caused any issues, neither on Linux, nor on Windows VM nor on native Windows. It's the safe bet, but who's not willing to try something new?

-The Problem-

I configured the profile for higher quality (TTA on, FP32) and left everything as is, started the transcode and voila, it did actually start (the magic 1%)! Curious as I am, I opened the not-yet-finished file (read-only) in VLC, and I was surprised to see that it was flickering, and looking at it frame by frame told me every second frame was just black. Though the water mark was still there, to help troubleshooting smile . VLC told me the framerate is 24000 (sic!) with the original having 23.976024 fps. So I closed VLC, waited for it to be done transcoding, hoping that it would add these frames later on. But nothing changed. Despite the seemingly high framerate, the playback speed and seek bar times were correct, and I only had to go 48 frames forward to get to the next second. The log (attached) told me about some issues that I have no idea of. Task Manager told me 0~5% GPU load, 95~100% CPU load. Isn't that odd?

Also while writing this, I tried using the default settings and I think TTA causes this issue. Turning it off seems to get me a better video (I see interpolated frames, no flickering) and it takes a lot longer than before. If anyone needs snapshots in case they can't reproduce my error, I'll happily share some frames. Same goes for any logs/system information etc.

System Specs:
CPU: 3600
GPU: RX 570
M.2 SSD
RAM: 16GB DDR4
Windows 10, drivers and everything up to date
SVP 4 version 210

Thanks a lot big_smile
Super4Jet

Also since the attachements don't seem to work as far as I can see, here's the log on pastebin: https://pastebin.com/eTuX27Wz

I don't think so. You'd need to make it a video first and then let SVP do the hard work smile

Ah yes, didn't know mpv would be using more than 4.5Gigs. You're genius, thanks! It's working now smile

Okay so hi again, I now got another issue: 4k is not working. 1080p works and I'm very happy with it, it's really smooth! 1080p works with both encoders (264+265), but 2160p always fails:

21:35:55.499: ===== Starting mpv ======
21:35:55.499: Command line: /usr/local/bin/mpv /run/user/1000/gvfs/smb-share:server=192.168.178.10,share=nas/My Data/WhyNot1.mp4 --o=/run/user/1000/gvfs/smb-share:server=192.168.178.10,share=nas/My Data/WhyNot1.SVP.temporary.mkv --no-audio --no-sub --no-sub-auto --input-ipc-server=/tmp/mpvencodesocket --input-media-keys=no --no-msg-color --vf=vapoursynth:/home/ubuntu/.local/share/SVP4/scripts/ffff.py:4:6 --of=matroska --ovc=libx265 --ovcopts=crf=18,preset=slow,threads=6
21:35:55.561: (+) Video --vid=1 (*) (hevc 3840x2160 23.976fps)
21:35:55.561: Audio --aid=1 --alang=eng (*) (aac 2ch 44100Hz)
21:35:55.561: Audio --aid=2 --alang=eng (aac 2ch 44100Hz)
21:35:55.849: VO: [lavc] 3840x2160 yuv420p
21:35:55.849: [vo/lavc] Opening encoder: libx265 H.265 / HEVC [libx265]
21:35:55.850: x265 [info]: HEVC encoder version 3.2.1+1-b5c86a64bbbe
21:35:55.850: x265 [info]: build info [Linux][GCC 9.3.0][64 bit] 8bit+10bit+12bit
21:35:55.850: x265 [info]: using cpu capabilities: MMX2 SSE2Fast LZCNT SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
21:35:55.850: x265 [info]: Main profile, Level-6.1 (Main tier)
21:35:55.850: x265 [info]: Thread pool created using 6 threads
21:35:55.850: x265 [info]: Slices : 1
21:35:55.850: x265 [info]: frame threads / pool features : 6 / wpp(34 rows)
21:35:55.883: x265 [info]: Coding QT: max CU size, min CU size : 64 / 8
21:35:55.883: x265 [info]: Residual QT: max TU size, max depth : 32 / 1 inter / 1 intra
21:35:55.883: x265 [info]: ME / range / subpel / merge : star / 57 / 3 / 3
21:35:55.883: x265 [info]: Keyframe min / max / scenecut / bias: 25 / 250 / 40 / 5.00
21:35:55.883: x265 [info]: Lookahead / bframes / badapt : 25 / 4 / 2
21:35:55.883: x265 [info]: b-pyramid / weightp / weightb : 1 / 1 / 0
21:35:55.883: x265 [info]: References / ref-limit cu / depth : 4 / on / on
21:35:55.883: x265 [info]: AQ: mode / str / qg-size / cu-tree : 2 / 1.0 / 32 / 1
21:35:55.883: x265 [info]: Rate Control / qCompress : CRF-18.0 / 0.60
21:35:55.883: x265 [info]: tools: rect limit-modes rd=4 psy-rd=2.00 rdoq=2 psy-rdoq=1.00
21:35:55.883: x265 [info]: tools: rskip signhide tmvp strong-intra-smoothing lslices=4
21:35:55.883: x265 [info]: tools: deblock sao
21:35:55.883: [encode] Opening output file: /run/user/1000/gvfs/smb-share:server=192.168.178.10,share=nas/My Data/WhyNot1.SVP.temporary.mkv
21:35:55.902: [encode] Opening muxer: Matroska [matroska]
21:35:55.996: V: 00:00:00 / 00:03:46 (0%) {3.8min 0.0MB} Cache: 10s/9MB
21:36:05.282: (!!!) Intermediate file may be broken: /run/user/1000/gvfs/smb-share:server=192.168.178.10,share=nas/My Data/WhyNot1.SVP.temporary.mkv
21:36:05.282: ===== mpv exited with code 9 =====

No matter whether I take the h.264 or h.265 encoder, it would fire up, count up a few numbers, show 0.1fps and it fails directly after that. Does SVP then even support 4K? I tested the same file, encoded in HandBrake, same settings (RF same, not the bitrate, that'd pointless, and h.265), just downscaled for the 1080p version.

Ah no it's installed at /usr/local/bin/mpv
Install log for completeness: https://pastebin.com/irHfaQeb
Do I need to change that?

Reply limit:
Ah thanks, that did the trick! Now it's working. I'm super excited how this will turn out! smile
Feeling rather stupid now...

Thank you very much smile
So I rebuild it again and took a copy of the log. I don't want to cause too much trouble, but just in case there is something else I might have overlooked, I attached the whole log. But I believe only the last lines are interesting as in line 4468 and 4638 it says "compiling [...] vf_vapoursynth.c" - which leads me to believe that it did compile and, after ./install, install it. - ?

https://pastebin.com/xVNEEdgc

Reply limit...

Thanks Chainik,
so I did rebuild it (and sudo installed it), but SVPManager still tells me mpv didn't find vapoursynth. How do I make sure mpv correctly discovered and installed VS? I'm kind of lost here...

Hi everyone,
so, I have a problem: I have already installed Vapoursynth and Python and zimg and all that, but SVP tells me it doesn't work (see attached picture)
Now though it's not my first time using Linux, I can't get this to work, and the internet doesn't tell me anything. If that helps:  vspipe -v is (mostly) happy. But mpv doesn't even list VS in the vf=help section.
Log:

02:46:59.615: ===== Starting mpv ======
02:46:59.615: Command line: /usr/bin/mpv /home/ubuntu/Desktop/Butterfly.mp4 --o=/home/ubuntu/Desktop/Butterfly.SVP.temporary.mkv --no-audio --no-sub --no-sub-auto --input-ipc-server=/tmp/mpvencodesocket --input-media-keys=no --no-msg-color --vf=vapoursynth:/home/ubuntu/.local/share/SVP4/scripts/ffff.py:4:4 --of=matroska --ovc=libx265 --ovcopts=crf=18,preset=slow,threads=4
02:46:59.712: Option vf: vapoursynth doesn't exist.
02:46:59.712: Error parsing option vf (option parameter could not be parsed)
02:46:59.712: Setting commandline option --vf=vapoursynth:/home/ubuntu/.local/share/SVP4/scripts/ffff.py:4:4 failed.
02:46:59.712: Exiting... (Fatal error)
02:46:59.714: (!!!) Intermediate file may be broken: /home/ubuntu/Desktop/Butterfly.SVP.temporary.mkv
02:46:59.714: ===== mpv exited with code 1 =====

If you need any more information, feel free to ask me, I'd be glad about any help.
Super4Jet

I can't reply?
So here is a reply as an edit:
Thanks Chainik,
so I did rebuild it (and sudo installed it), but SVPManager still tells me mpv didn't find vapoursynth. How do I make sure mpv correctly discovered and installed VS? I'm kind of lost here...