dejavecue wrote:Nice. Finally can use SVP with mpv on Vulkan
SVP is actually providing mpv 0.28, which has vulkan.
Rev1 or Rev2? Because Rev1 throws errors for me, with a weird kind of triangle bug in the upper right corner.
You are not logged in. Please login or register.
SmoothVideo Project → Posts by dejavecue
dejavecue wrote:Nice. Finally can use SVP with mpv on Vulkan
SVP is actually providing mpv 0.28, which has vulkan.
Rev1 or Rev2? Because Rev1 throws errors for me, with a weird kind of triangle bug in the upper right corner.
Now that SVP has added Vulkun support.
??? I think you wanted to say that mpv has added vulkan support?
--gpu-api=vulkan is for command line use. You need to write gpu-api=vulkan (removing the leading dashes) in mpv.conf.
Try native 60fps 4K 10bit hdr first: http://4kmedia.org/samsung-travel-with- … d-4k-demo/
If it works, then go for svp.
If you want to use Vulkan, I would suggest the following additions to the mpv.conf:
profile=gpu-hq
gpu-api=vulkan
gpu-context=winvk
hwdec=no
vd-lavc-dr=yes
vd-lavc-threads=16 | Adapt this to the number of threads your CPU can handle simultaneously
where did u find so much hdr 2k+ content ?
4K blurays have recently been cracked (AACS2.0 I believe)
Nice. Finally can use SVP with mpv on Vulkan
mpv has absolutely no trouble playing UHD content @ 10 bit per channel (or higher). You simply have to use defaults (i.e. not use hardware decoding but let the CPU do it). It supports all the new(ish) content out of the box - and with the recent addition of a vulkan renderer, at even less performance cost.
Source: I have been watching 4k movies and series with mpv for months.
You can also use this media autobuild suite for compilation, although it relies on all the gits being compatible to one another (for now there is a bug in libass that stops the process) but if you want to control every aspect of compilation, this is a good tool.
1700 is overkill for 1080p. Its more than enough even for 4k
Only low bitrate 4k files work though. Again, CPU seems to be less important than GPU and my RX 480 cannot handle most 4k files with SVP4 decently.
Seems like everyone's suspicions that Ryzen's core count and love for high frequency memory would mean it performs well here. What I'm really wondering is if Threadripper with its 4 memory channels will do even better. Would love to see a comparison between a 1700 and 1900X.
I don't think you will see much difference. I am running a Ryzen 7 1700 @3.8 Ghz with 16GiB of RAM @ 2933 Mhz and with SVP4 pro (mpv) version, CPU usage never goes above 10% even. SVP seems to be mostly GPU intensive.
I'll do it for 1000€
This looks solid. Did this fix your problem?
Brilliant smooth motion, but this halo or shimmering whenever there's fast motion makes everything unwatchable - it's a terrible side-effect of what is a wonderful, liquid, almost 3D image.
I have SVP4 free. I tried SVP3 after reading that this effect it's not so bad... but typically (using SVP3) the ffdshow raw video filter doesn't appear in MPC 32bit while video is playing, in spite of it being added to external filters, yet it IS recognised in MPC 64bit only 64bit is not supported!
So I'm pretty disappointed - and annoyed - that such a potentially great addition, as SVP4 seems to be, is, in reality, totally useless. Unless you're myopic and don't notice it.
I get you are disappointed but for a free product, there is only so much you can expect.
Additionally, artifacts are simply mathematical reality that happens when you literally "invent" new frames for smoothness.
In SVP4 Pro you can have stronger artifact masking, so maybe instead of simply complaining, you should try and develop a better algorithm to either hide artifacts or find a different method of motion interpolation that does not produce artifacts (although I believe this is a physical and mathematical impossibility) - the SVP team would probably be very grateful for your input
Personally I just really want to avoid proprietary software just to watch my videos in a decent quality.
Use mpv, which is completely FOSS. If you really have trouble with SVP being closed source, you could always try to use mvtools for SVP-like frame interpolation. Or you could write your own software to do the exact same thing.
It's not like this is a software that is absolutely essential to everyday tasks.
dejavecue wrote:dlr5668 wrote:Check mine
input-ipc-server=mpvpipe vo=opengl-hq:backend=dxinterop:scale=ewa_lanczossharp:cscale=ewa_lanczossoft:interpolation:tscale=mitchell:tscale-clamp:temporal-dither hwdec=d3d11va-copy slang=enUS,en,eng,ptBR,pt alang=jp,jpn,enUS,en,eng,ptBR,pt save-position-on-quit=yes script-opts=autospeed-nircmd=true,autospeed-speed=false,autospeed-nircmdc="C:\Users\vadas\AppData\Roaming\mpv\nircmdc.exe1",autospeed-rates="50,60,71,72",autospeed-osd=true log-file="C:\tmp\mpv.log" video-sync=display-resample video-sync-max-video-change=10 hr-seek-framedrop=no
This will run smooth because the entire vo= line will be ignored, as for almost a year now the vo= settings are not separated by colons anymore.
Basically: vo=opengl-hq:backend=dxinterop:scale=ewa_lanczossharp:cscale=ewa_lanczossoft:interpolation:tscale=mitchell:tscale-clamp:temporal-dither
none of these are actually on.So that line only says that it will run in opengl? FWIW these are my settings. Did I mess up? https://pastebin.com/gRQbTVLr
Your config seems fine.
The other one with this line : vo=opengl-hq:backend=dxinterop:scale=ewa_lanczossharp:cscale=ewa_lanczossoft:interpolation:tscale=mitchell:tscale-clamp:temporal-dither
does not work.
The way it would work goes like this:
vo=opengl-hq
backend=dxinterop
scale=ewa_lanczossharp
cscale=ewa_lanczossoft
interpolation
tscale=mitchell
tscale-clamp
temporal-dither
Check mine
input-ipc-server=mpvpipe vo=opengl-hq:backend=dxinterop:scale=ewa_lanczossharp:cscale=ewa_lanczossoft:interpolation:tscale=mitchell:tscale-clamp:temporal-dither hwdec=d3d11va-copy slang=enUS,en,eng,ptBR,pt alang=jp,jpn,enUS,en,eng,ptBR,pt save-position-on-quit=yes script-opts=autospeed-nircmd=true,autospeed-speed=false,autospeed-nircmdc="C:\Users\vadas\AppData\Roaming\mpv\nircmdc.exe1",autospeed-rates="50,60,71,72",autospeed-osd=true log-file="C:\tmp\mpv.log" video-sync=display-resample video-sync-max-video-change=10 hr-seek-framedrop=no
This will run smooth because the entire vo= line will be ignored, as for almost a year now the vo= settings are not separated by colons anymore.
Basically: vo=opengl-hq:backend=dxinterop:scale=ewa_lanczossharp:cscale=ewa_lanczossoft:interpolation:tscale=mitchell:tscale-clamp:temporal-dither
none of these are actually on.
dejavecue wrote:cherokee wrote:Hi, I need this file. How do I get it?
Thanks!
Hi, dejavecue
mpv 0.26 is out today. Would you consider compile enable-vapoursynth version?
Thanks!
I would certainly, but 0.26 has just been updated in SVP itself. I'd recommend just downloading that one. When (if) there are interesting changes before a new version update, I will compile again.
dejavecue wrote:I instead recompiled the latest mpv from source with the --enable-vapoursynth flag and now it all works.
If wanted, I could provide this file for those who are interested.
Hi, I need this file. How do I get it?
Thanks!
wait for 0.26 release then
I instead recompiled the latest mpv from source with the --enable-vapoursynth flag and now it all works.
If wanted, I could provide this file for those who are interested.
mpv that comes with SVP is a last official release - 0.25 as of today
Which was compiled on April 24. Nearly three months ago and in the meantime there have been hundreds of commits.
To be more precise:
AXIS_UP seek 10
AXIS_DOWN seek -10
These commands seem to be completely ignored - they correspond to the mousewheel.
Sorry to necro this thread, but I have recently reinstalled Windows 10 and SVP4 Pro (after upgrading to a Ryzen 7 1700) and I used my old mpv.conf and input.conf files, but while the mpv.conf file has no trouble being read, the input.conf does not really read all my settings.
Is this because the mpv version that comes with SVP4 is rather old (lots of changes recently) or does it not read the entire input.conf?
I am having a similar error from time to time with youtube-dl. mpv even shows that audio bitrate suddenly drops to 1 kbps.
I think it has more to do with the way youtube streams audio than with the players themselves.
It usually goes away if I just quit mpv and play the video again
they'd better integrate mpv engine
This.
Browsers are for browsing text and images. Video support is pretty much abysmal. libmpv could simply be used in any browser.
In this light: You can use "open with" and point it to the mpv.exe that comes with SVP and then you can use SVP on any internet video
This is what "Artifact masking" is there for. But it is not perfect. I think only if you pre-encode files to higher framerates, these artifacts can be eliminated (not sure).
> I have been using SVP4 Pro for a while <...>
> However, as of recently <...>it used to work w/o crashes before, right?
when? what was changed?
I do not know. As mentioned, I mostly use it for fairly short files (TV shows) and have not been watching a lot of movies recently. The error only appears on longer files, so it might have to do with filesizes.
The most recent changes: Windows 10 Creator's Update, Frequent GPU driver updates (as they come out). SVP4 Pro is up to date as well.
Hi,
I have been using SVP4 Pro for a while and mostly for TV shows, where I have very little trouble (except with 4k releases, but that is to do with my CPU not being strong enough I guess).
However, as of recently, I have been getting the following error that makes mpv quit when watching longer files (i.e. movies):
Faulting application name: mpv.exe, version: 2.0.0.0, time stamp: 0x00000000
Faulting module name: ntdll.dll, version: 10.0.15063.0, time stamp: 0xb79b6ddb
Exception code: 0xc0000005
Fault offset: 0x000000000002f323
Faulting process ID: 0x2264
Faulting application start time: 0x01d2cc09dff66793
Faulting application path: C:\Program Files\SVP 4\mpv64\mpv.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report ID: 284f958a-acf4-4f89-b9bc-1e7ec7b0b220
Faulting package full name:
Faulting package-relative application ID:
It only happens with SVP4 manager running, if I watch the movie normally, no error appears.
I am running Windows 10 Pro x64 with 16GB of RAM on an i7-2600k and an RX480 8GB
Also, this is the mpv config that I use:
# Video settings
profile=opengl-hq
opengl-backend=angle
hwdec=auto-copy
hwdec-codecs=all
hr-seek-framedrop=no
scale=ewa_lanczossharp
scale-antiring=1
scaler-resizes-only
opengl-pbo
icc-cache-dir="~~/icc-cache"
icc-profile="~~/ULTRA HD.icm"
icc-3dlut-size=512x512x512
input-ipc-server=mpvpipe
force-window=immediate
# Audio settings
volume=66
alang=en,eng
# Subtitle settings
no-sub
slang=en,eng,ger
sub-font-size=40
sub-shadow-offset=0
sub-border-size=3.5
sub-color="#ffffffff"
sub-border-color="#ff000000"
sub-font="Source Sans Pro"
sub-ass-force-margins=yes
sub-use-margins=yes
# OSC settings
script-opts=osc-layout=bottombar,osc-seekbarstyle=bar,osc-hidetimeout=3000,osc-minmousemove=1,osc-fadeduration=0
# OSD settings
osd-font="Segoe UI"
osd-level=1
osd-scale-by-window=no
term-playing-msg='Resolution: ${width}x${height}, Framerate: ${fps}'
# Screenshot settings
screenshot-format=png
# Window settings
autofit-smaller=75%x75%
screen=1
autofit-larger=75%x75%
ytdl-format=(bestvideo[height<=?2160][fps<=?60]/bestvideo[height<=?2160]/bestvideo[height<=?2160])+(bestaudio[acodec=opus]/bestaudio)
#ytdl-format=(bestvideo[vcodec=vp9][height<=?2160][fps<=?60]/bestvideo[vcodec=vp9][height<=?2160]/bestvideo[height<=?2160])+(bestaudio[acodec=opus]/bestaudio)
save-position-on-quit
cache=yes
cache-file="K:\TEMP\mpvcache"
cache-initial=0
cache-secs=600
cache-pause=yes
[extension.webm]
input-ipc-server=no
save-position-on-quit=no
loop-file=inf
Does anyone have an idea, why mpv would crash with SVP4 running?
If he gonna play games then Radeon + Ryzen is not the best choice here. AMD GPUs always need faster processor for not being CPU limited than Nvidia.
Huh? That makes little sense. Benches clearly show that the upper CPU limit is never scratched with current games, whereas with Ryzens, you will have WAY higher minimum fps (1% and 0.1% especially).
Plus, if you go Ryzen + Radeon you save a lot of money and have comparable performance to i7 7700K + GTX1060.
So if someone want Ryzen but still going to play games then the best way to go is Nvidia + Ryzen. The only reason to wait for Vega here is to wait for price drop on Nvidia cards.
Nvidia drivers actually gimp Ryzen performance because Nvidia missed the train on actually building decent hardware that can compute asynchronously.
And while Vega will certainly lead to Nvidia price drops, but some leaks suggest that Vega cards are actually up to 15% beefier than a GTX 1080 Ti
I agree that it must be smoother, but interpolating to 300 fps from 50 fps also means that you add a lot of "fictional" frames and thus drastically lose information (relatively speaking), so that image quality would suffer.
SmoothVideo Project → Posts by dejavecue
Powered by PunBB, supported by Informer Technologies, Inc.