mirror of https://github.com/n00mkrad/flowframes
updated changelog
This commit is contained in:
parent
19618f9cc6
commit
ccd46eef28
|
@ -1,3 +1,11 @@
|
|||
Flowframes 1.38.2 Changelog:
|
||||
- FPS limiting (downsampling) now works with RIFE-NCNN-VS
|
||||
- RIFE-NCNN-VS will no longer overwrite existing output files
|
||||
- Fixed issue where RIFE-NCNN-VS would try to use too many GPU threads
|
||||
- Fixed issue where a warning would pop up every time Flowframes is started without Pytorch
|
||||
- Replaced the default Message Box with a custom window, fixes some UI weirdness
|
||||
|
||||
|
||||
Flowframes 1.38.1 Changelog:
|
||||
- RIFE-NCNN-VS will now use the GPU ID set in the settings (multi-GPU not possible for now)
|
||||
- Trimming the input video now works with RIFE-NCNN-VS
|
||||
|
|
|
@ -1,3 +1,11 @@
|
|||
Flowframes 1.38.2 Changelog:
|
||||
- FPS limiting (downsampling) now works with RIFE-NCNN-VS
|
||||
- RIFE-NCNN-VS will no longer overwrite existing output files
|
||||
- Fixed issue where RIFE-NCNN-VS would try to use too many GPU threads
|
||||
- Fixed issue where a warning would pop up every time Flowframes is started without Pytorch
|
||||
- Replaced the default Message Box with a custom window, fixes some UI weirdness
|
||||
|
||||
|
||||
Flowframes 1.38.1 Changelog:
|
||||
- RIFE-NCNN-VS will now use the GPU ID set in the settings (multi-GPU not possible for now)
|
||||
- Trimming the input video now works with RIFE-NCNN-VS
|
||||
|
@ -13,10 +21,6 @@ Flowframes 1.38.0 Changelog:
|
|||
- Possibly fixed bug where RIFE-CUDA would run instead of the selected implementation
|
||||
- Improved AV1 encoding quality by changing bad default parameters
|
||||
|
||||
KNOWN ISSUES:
|
||||
- Frame counting sometimes fails and returns 0. Restart Flowframes if this happens.
|
||||
- Certain export features (image sequences, FPS limiting, ...) don't work with RIFE-NCNN-VS
|
||||
|
||||
|
||||
Flowframes 1.37.2 Changelog:
|
||||
- Added RIFE 4.1 model (RIFE-CUDA)
|
||||
|
|
Loading…
Reference in New Issue