Home Artists Posts Import Register

Downloads

Content

So here it is, the first Flowframes version with VapourSynth-based RIFE, eliminating the need to store all the frames on disk.

Do keep in mind that some things don't work with the new implementation yet, like FPS limiting/downsampling.

Full changelog on Discord and in Flowframes.

Comments

HakuryuuFilms

sadly this version is not woking for me at all. fail to load any type of video file it always gives an error and thats it.

Anonymous

Would there be a way of making VaporSynth use less VRAM? I'm in the process of interpolating my 5898x5898px stereoscopic 360 degree-videos from 30 to 60 fps. My RTX 3060 TI has 8 GB of VRAM. The input video format is H264 with around 1500 mbps. Using RIFE - CUDA doesn't work because there's not enough VRAM. Using Half-Precision mode uses only around 6 GB of VRAM but the resulting video flickers. NCNN/VS also tries to occupy more than 8 GB of VRAM and crashes. RIFE - NCNN works without half-precision mode though and only uses 6 GB of VRAM, works really well. But VS would be so much better speedwise and to not loose any detail in JPG compression. PNG-files would take up about 1 TB for each video...

Anonymous

When FlowFrames is reading the metadata, it reads the whole file, which in case of a 200 GB file takes a while. Would there be a way of reducing that?

n00mkrad

No, frame count is needed and there's no way to get it without reading the entire file once

Anonymous

Hi, is it possible to add support for spherical 360 video so that after recoding it also remains spherical and does not become ordinary flat?

Anonymous

I have already converted a lot of 3D-360-degree-videos in the top/bottom format and it worked flawlessly. Doesn't have to be explicitly supported I believe.

Anonymous

I discovered several bugs in this version: - When trying to start the interpolation while it is still reading the meta data, it of course doesn't start, but after that it continues to load the whole input file endlessly and has to be stopped in task manager. - When doing other things while the AI is running and the VRAM fills up, it continues the job, even continues to create all the interpolated pictures, it even continues encoding, but from that point on the video ouput file doesn't grow anymore, so from that point on the work is lost. - Doing a step-by-step interpolation, when the extraction of images has finished, it's not possible to close flowframes, load the same video and continue with the 2nd part, the interpolation. - Also when cutting the frames folder, pasting it outside the temp folder and loading that instead of the input video, there is an error message almost instantly that no frames could be extracted, and there are already extracted frames. Even after manually running the last step (reset and clear cache). - VaporSynth doesn't seem to run on Intel UHD graphics (i9, 11th generation), even though it has 32 GB of shared VRAM left. Error message: "thread count has to be between" I believe 1 and -1, can't look it up right now. NCNN-Vulkan runs on it though.

Anonymous

The problem is that it makes the video flat and after that it has to be recoded again to 360 degree format via Adobe Premier, which takes extra time and resources. There is also an unpleasant docking line that is visible at high speed, for example, when the video is shot on the roof of a car.

Anonymous

A question, when using dedepulication it always says; "Error: Index was outside the bounds of the array." Is that a concern at all?

Anonymous

I believe that's just the 360 degree tags missing in the file. If you open both files in Windows Media Player which doesn't support 360-degree vids and they look exactly the same, that's the case.

Anonymous

The solution is: use the spatial media metadata injector YouTube provides. It just takes a few seconds and the tags are back.

Anonymous

Perhaps for such heavy videos you should buy an RTX 3090 video card with 24 GB of video memory and a powerful GPU

Anonymous

Thought about that but it turned out it would only have around 30% more performance than my overclocked 3060 TI (connected via USB-C in an eGPU-case). However, it would be really awesome if I could use the integrated NVIDIA T600 (4 GB VRAM) for nvEnc-encoding while using the 3060 TI for the AI. That would speed it up a lot. Usually with the AI working 1,6 GB VRAM are free. When it is encoding though, free VRAM shrinks to around 100 MB, so I can't do a lot while it is encoding. Would there be a way to configure that somewhere?

Andy Zou

What an improvement. Thanks! It's come a long way since the first version! Love not needing to reserve space for PNGs...

Kezo

This is brilliant, no more bloat during processing! You do exemplary work!

Anonymous

is there a version of this with the embedded python? Or do you have a link to an idiots guide to installing the relevant things under windows? I'm new to python and not having much luck getting anything to work :(

n00mkrad

1) Fill fix soon 2) That happens when your GPU runs out of memory. 3) You can resume by dragging the temp folder into Flowframes, no the video 4) Will look into this 5) Probably related to GPU ID, working on a fix

n00mkrad

I still don't know what it happens, but it should not be a problem.

n00mkrad

In the installer, select "Vulkan + CUDA" on the framework selection screen

Anonymous

Thanks, and lastly if you have the time, is NCNN/VS higher quality than CUDA?

Anonymous

Hello, when trimming start / end times, it just keeps going. E.G. start of 00:20:00 and end of 00:21:00 just for a small sample clip. But it keeps on encoding far past the number of frames that should be expected.

n00mkrad

Trimming won't work for RIFE-NCNN-VS if that's what you tried. Should be implemented in the next update.

Anonymous

There are a few problems I found. 1. I saw a message saying "Set multi gpu threads to 1 or 2" when using multiple gpu. I am using amd and nvdia graphics card together, but amd must be deactivated before it works. 2. When running a specific video codec in ncnn/vs (the video was recording with obs amd-h.264), the whole process was skipped and it was completed in 2 seconds.

Anonymous

Correct, I was trying to trim. Thanks! Looking forward to future updates.

Indulge Me

Time to get an update I guess. Thanks.