You are not logged in. Please login or register.
SmoothVideo Project → Posts by Chainik
well, Ryzen 7 can play 4K with mpv smoothly
not with highest settings as with MPC-HC though...
ok, I've updated mpv's wiki page with the link to shinchiro's builds
it's not a renderer issue because mpv shows abnormally high CPU usage on 4K even with null renderer
> Or alternatively would you provide weekly updates from mpv git master?
No, only the releases.
svpcode and svpcast extensions was added just now
and they both use mpv for encoding
> что-то очень много файл потом весит
Так битрейт крутить можно...
Ну, вот если очередная "черная пятница", то все сидят и ждут эту "пятницу"... Это хорошо для тех, кто всякое китайское говно продает (см. "М-видео"). А для SVP выгода сомнительна...
This's great, but SVP now needs more built-in encoders for transcoding and streaming - x265, QuickSync, AMD AMF.
> I'm surprised that SVP4 can't show the same good results for this goal.
Why? Only because it can't set "2 threads"? ![]()
All settings -> set "frc.threads" = 2
I'm more surprised with the fact 2 threads can handle 1080p...
Which CPU do you have? Kabylake @5GHz ?
> how do you think this pipeline can be improved?
Probably by using mpv.
====
Just a little technical comment: number of threads is NOT a problem. The real problem is in ffdshow buffers size (open ffdshow properties, Avisynth tab, see "buffer back/ahead" values). In general, more threads need larger buffers -> gives higher latency, BUT you can adjust buffers size with frc.prefetch.ff_mul and frc.prefetch.ff_add values - <buffer size> = ff_mul * <threads> + ff_add. When the buffer will be too small for the given number of threads you'll see it ![]()
====
You can now set 2 threads in SVP 4 but you can't lower ffdshow buffer size below 7. Damn...
это только в м-видео (и пр.) халява предсказуема и по календарю ![]()
That's right
you can add whatever you want via All settings - cast.encode.opts.h264_amf
Nope
try SW decoder on the mobile
try this
This was copied from Videostream ffmpeg args... I have no idea if we really need it
probably not...
right
now remove params one by one
ah! the only difference I can see is different default encoder params:
svpcode: "code.simple.opts.h264_amf" = "b=$B,quality=quality,profile=high,rc=vbr_peak"
svpcast: "cast.encode.opts.h264_amf" = "b=$B,quality=quality,profile=high,rc=cbr"
in fact you can try to put all the svpcast's params into svpcode's encoding profile (under "advanced" button):
b=4700000,quality=quality,profile=high,rc=cbr,g=60,keyint_min=60,refs=1,sc_threshold=0
Prerequisites
Windows® 7 (SP1 with the Platform Update), Windows® 8.1, or Windows® 10
Version 1.4.6: AMD Radeon Software Crimson Edition 17.12.1 (17.50.02) or newer
Try the new .130 build.
- should be a little bit less CPU demanding
- added AMD AMF option (*)
(*) I can't check how good or bad it works, so please leave your comments ![]()
See the encoder options in "All settings": cast.encode.opts.h264_amf and cast.encode.opts.hevc_amf
намекает что не каждый может себе позволить SVP вместе с svpcode
Videostream encodes video for streaming with 5M bitrate.
> Nvenc doesn't matter as my gpu isn't being used when streaming anyways, mostly just the cpu.
You didn't read what I wrote
Interpolation uses "mostly the cpu" and NVENC works just fine.
...and stream 720p only...
===
I'm wrong, it can do "native resolution", at least for 1080p...
but no NVENC ![]()
and 5M bitrate at maximum
nope, it'd be too predictable ![]()
SmoothVideo Project → Posts by Chainik
Powered by PunBB, supported by Informer Technologies, Inc.