#smoothie vs. smoothie-rs

50 messages · Page 1 of 1 (latest)

open ore
#

I'd be very appreciative if those who have smoothie-rs could try to match their recipe.ini with the old smoothie (installable with scoop)'s recipe.yaml and see how much faster smoothie-rs is at frame blending,

Thank you!

exotic wind
#

ok

#

ill use default

#

i cant install either of them

#

error

granite mantle
#

Smoothie: 60.6s
Smoothie-RS: 60.07s

#

Using a 720p960fps clip from #1090708601070424258

#

Not sure if H264 NVENC ffmpeg args are the same though

heady patio
sage coyote
#

mb

candid kestrel
#

when i get home ill run a 15s, 30s, and 60s clip through smoothie-py and -rs at faster, weak, 13 👍

open ore
#

the only important metric is frame blending

candid kestrel
wise adder
solar notch
#

sm-rs ~19 seconds, smoothie ~20 seconds. (360fps blended to 60fps at 1.0 equal)

sage coyote
# 
  enabled: yes
  fps: 60
  intensity: 1.5
  weighting: equal```
180fps
open ore
#

so it seems just as fast for y’all mmhtent

inland snow
#

im gonna download smoothie py later and test

inland snow
#

less of a difference than i thought but there still is one on my machine

#

py

# This is the recipe (config) for making a delicious smoothie ;p
# Learn how it can be fine-tuned @ https://github.com/couleur-tweak-tips/Smoothie/wiki

interpolation:
  enabled: no
  fps: 480
  mask: weak
  speed: medium
  tuning: weak
  algorithm: 13
  gpu: true

frame blending:
  enabled: yes
  fps: 60
  intensity: 1
  weighting: equal

flowblur:
  enabled: no
  amount: 100
  mask:

encoding:
  process: ffmpeg
  args: H264 CPU

misc:
  mpv bin: mpv
  stay on top: true
  verbose: false
  ding after: 1
  folder: 
  container: .MKV
  flavors: fruits
  dedupthreshold: 0

timescale:
  in: 1.0
  out: 1.0

rs

[interpolation]
enabled: no
fps: 960
speed: medium
tuning: weak
algorithm: 23
use gpu: yes

[frame blending]
enabled: yes
fps: 60
intensity: 1
weighting: equal
bright blend: no

[flowblur]
enabled: no
amount: 100
mask:

[output]
process: ffmpeg
enc args: H264 CPU
file format: %FILENAME% ~ %FRUIT%
container: .MP4

[preview window]
enabled: no
process: ffplay
output args: -s 1280x720 -f yuv4mpegpipe -

[miscellaneous]
play ding: no
always verbose: no
dedup threshold: 0.0
global output folder:
source indexing: no
ffmpeg options: -loglevel error -i - -hide_banner -stats -stats_period 0.15
ffplay options: -loglevel quiet -i - -autoexit -window_title smoothie.preview

[console]
stay on top: no
borderless: yes
position: top left
width: 900
height: 350

[timescale]
in: 1.0
out: 1.0

[pre-interp]
enabled: no
factor: 2x
model: rife-v4.4
inland snow
granite mantle
#

CPU args are different

#

-c:v libx264 -preset slow -aq-mode 3 -crf 16 use this on smoothie py

#

its what smoothie-rs uses for H264 CPU

inland snow
#

running that right now

#

after that im sleeping because its 1am for me

#

its at 4 fps right now which is slower than it was during the first test

granite mantle
#

wtf

inland snow
#

232.75 seconds

#

¯_(ツ)_/¯

granite mantle
#

inconsistant variables?

#

other shit running the the background?

inland snow
#

idk i had krita open but i wasnt doing anything

#

but that was for all of them

#

i had to fuck with it a little to get it to run

#

liek get rid of all the spinner and prog stuff

#

also make it split the string at the ffprobe thing in the exec.py

#

becausef ro some reason it doesnt like linux

#

im going to bed now because i cant type

#

and itss 1am

jolly fractal
#

how to fix this

image.png
long cedar
#

it Told you

dreamy musk
#

#🟩｜ffmpeg