You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 16, 2023. It is now read-only.
I have added the relevant Registry edits, yet it seems to still be broken. I am using i7-7700k and RTX 2080 Super running 436.30. On the previous post with this error, you said I need to be running 416 or earlier, but there seemed to be quite a bit of conversation after that saying the problem was solved. Here are my screenshots of error message and registry.
The text was updated successfully, but these errors were encountered:
Are you running the latest version? If you check the release page for 0.2.4.alpha2, you will see that several builds were added to the assets. What you'll want to download is butterflow-0.2.4a4-win64.zip.
For what it is worth, if you are running under Windows (as your screen shots suggest) I have made a GUI for butterflow called butterflow-ui that comes pre-packaged with 0.2.4a4.
I think you also have to put one in the WOW6432NODE thingy key also (since you only supplied one screen shot of the reg key).
I also tested the ui version and it seems to be working, except it doesn't seem to be working too.
I can get a processed output file, but it doesn't seem to be smooth 60 fps video like I expected to get with -vf "minterpolate=fps=60". It just looks like a 60 fps video made on -r 60 or -vf minterpolate=fps=60:mi_mode=dup. which 10x faster than processing it through butterflow, but I'll do some tests first.
(I also hope that the console windows can be resized)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have added the relevant Registry edits, yet it seems to still be broken. I am using i7-7700k and RTX 2080 Super running 436.30. On the previous post with this error, you said I need to be running 416 or earlier, but there seemed to be quite a bit of conversation after that saying the problem was solved. Here are my screenshots of error message and registry.
The text was updated successfully, but these errors were encountered: