/mpv/ - mpv general:

Last thread Install mpv:
mpv.io/installation/

Wiki:
github.com/mpv-player/mpv/wiki

Manual:
mpv.io/manual/stable/

User Scripts(including opengl shaders):
github.com/mpv-player/mpv/wiki/User-Scripts

input.conf:
github.com/mpv-player/mpv/blob/master/etc/input.conf

Other urls found in this thread:

github.com/atomnuker/mpv/
gist.github.com/haasn/7919afd765e308fa91cbe19a64631d0f
github.com/haasn/gentoo-conf/blob/xor/home/nand/.mpv/input-image.conf
pastebin.com/raw/bCspQGWm
pastebin.com/raw/Cm04TCVj
mpv.io/manual/master/#options-hwdec
spit.mixtape.moe/view/fa5765f8
github.com/mpv-player/mpv/wiki/User-Scripts
gist.github.com/Zehkul/25ea7ae77b30af959be0
github.com/occivink/mpv-scripts
spit.mixtape.moe/view/9ca24217
pastebin.com/yux1YLWn
twitter.com/AnonBabble

hwdec yes or no?

vulkan
github.com/atomnuker/mpv/

what cpu?

Who else here uses mpv as their imageviewer?
The only problem I have with it is that it's a bit slow when zooming bigger images.

i5 7600k

hwdec=no

>gist.github.com/haasn/7919afd765e308fa91cbe19a64631d0f
>github.com/haasn/gentoo-conf/blob/xor/home/nand/.mpv/input-image.conf
Do you use this?

hwdec=no is default.

Yes but modified. I am a fan of nand since the times he was programming in C#.

Im getting "Too many hooks! Limit is 16." Wat do? Does this shit limit me somehow? I only have 4 shaiders in my chain.

I know

So xrandr.lua+72hz overclocked monitor would be the best solution for a judder free playback?

I only use two shaders but get "TOO MANY HOOKS" error. What the fuck. Please help me!

There's a way to increase the hooks but I don't remember how, some user talked about it like 3 threads ago , go to the archive and search the last 3 threads.

Could someone with intel or amd test? Or someone with a more modern card than a gtx 780something?

vd-lavc-threads=32

linux only?

>vd-lavc-threads
That's for cpu threads

And what do you think the threads are being used by?

Opengl shaders are processed by the gpu not cpu.
The cpu is used to decode the video and process the frames.

Yes.

man mpv
--vd-lavc-threads=: Number of threads to use for decoding.

when yo gon fix resizing fagget

and force-window segfaults

>Resizing still freezes my computer.
> pastebin.com/raw/bCspQGWm

>Force window causes segfault.
> pastebin.com/raw/Cm04TCVj

Literally why would you ever put hwdec=no if it's supported on your CPU? Just use hwdec=vaapi for Intel. If you use software decoding it wastes 10-20% of CPU usage, and can stutter if you have a shitty CPU. Is there any downside to using hardware decoding?

# Video
profile=opengl-hq
opengl-backend=dxinterop

# Interpolation
interpolation=yes
tscale=oversample
video-sync=display-resample

# Misc. video
deband-grain=0
deband-iterations=2
deband-range=12
deband-threshold=48

# Window
fullscreen=yes
autofit=80%

# Scaling
scale=ewa_lanczossharp
cscale=ewa_lanczossharp

# Audio
audio-spdif=dts-hd,ac3

# Font
sub-ass-style-override=force
sub-auto=fuzzy
sub-use-margins=no
sub-scale=0.85
sub-color="#afa32b"
osd-shadow-color=000000
sub-shadow-color=000000
sub-font="Source Sans Pro"

i5-4210u+geforce 820m
what do you think?

Who else plays movies from the framebuffer with vo=drm ? It's the comfiest way to use mpv.

>they perform conversions (badly, of course) and mpv can't perform proper color management. In cases they align croma and luma planes (e.g. to convert to RGB) and do this using bad algorithms (usually bilinear or bicubic) and mpv can't use your cscale. Stuff like that can but doesn't have to happen. Some also shit themselves with certain formats.

>There's also no benefit using them, really. The one major benefit is potentially lower energy usage on mobile hardware. However, with CPUs being good and software more optimized than ever, h264 decodes in software nearly as efficient as in hardware. So there's really no point, especially not when you are on a desktop. So why risk the problems mentioned above?

>There's one exception though and that's when your software decoder is not fast enough. This is the case for h265 where software just isn't nearly as optimized as with h264. Trying to decode h265 4K 60FPS in software is probably impossible for most systems, here you need hwdec.

It fucks up the color space most of the time

No.

Of course. They are applied in their respective order.

"Wastes" usage? Hwdec pushes this load to the GPU, in the end the energy consumption is pretty identical.

Thanks but im still getting "TOO MANY HOOKS MAX 16".
That user said to ask devs to make the number more.

Its not an ERROR its a WARNING.

One shader can have many hooks. IIRC the adaptive sharpen shader had a ridiculously high number of hooks.

How do I know if xrandr.lua is working?

What's a good range for frame timings?

mpv.io/manual/master/#options-hwdec

No. Its error. "[e]".
I see, thank you.

>asked for non-ancient cards
>posts that

When either your fucking beloved nvidia fixes the drivers, or you stop using crappy 30 year old technology and switch to perfectly working and much faster wayland or someone runs a validation layer on their nvidia system very probably confirming its the drivers, not mpv. And the last thing isn't happening because good goys wouldn't blame someone after they gave them money for junk.

Below 16ms

Fooozer post youre mpv config!

Depends on FPS of the video. For 60FPS its 16ms, for 24FPS 41.

Thanks.

Interpolation is garbage, but the conf looks okay.

I mean you need some headroom. For example 11ms for 16ms (60FPS) or 30ms for 41ms (24FPS).

Its oversample interpolation. It doesnt add blur or anything.

What shaders would one want for basic media playing?

None.

None of them.
profile=opengl-hq
scale=ewa_lanczossharp
cscale=ewa_lanczossoft
video-sync=display-resample

This is the bare minimum you should use. Also might want to throw in:
interpolation=yes
tscale=oversample

>oversample
>A version of nearest neighbour that (naively) oversamples pixels, so that pixels overlapping edges get linearly interpolated instead of rounded. This essentially removes the small imperfections and judder artifacts caused by nearest-neighbour interpolation, in exchange for adding some blur.

is this good enough for Youtube, TV shows and movies?

I need mpv to display the timecode in mm:ss.miliseconds so I can see when I want to cut scenes with ffmpeg.

How do I see the precise timecode? hh:mm:ss is not granular enough.


Thanks.

Yup. If youre on win add "log-file=log.txt". It will create a log in your mpv folder. Open it after playback and search for "DUMB" anything. If there is nothing like that in the txt then youre fine.

osd-fractions=yes
script-opts=osc-timems=yes

thx senpai

and what do you recommend for anime.

I primarily download 720p and 1080p and upscale to my 4K TV. what's the best for upscaling like that?

click the left stamp on the on screen controler

why don't you use a script so you can cut clips in mpv

I'm just a scrub with a 770 but vo=vulkan segfaults even with no-config
spit.mixtape.moe/view/fa5765f8

Does anybody else have problems with video-sync=display-* causing mistimed/delayed frames on 10-bit video? Even if I used --no-config I'd occasionally get a mistimed frame on 720p 10-bit even though I can otherwise handle intensive filters just fine.

ooooooh... nice! thank you so much user. I always wanted ms but never asked.

>click the left stamp on the on screen controler
wow! thanks. works great too.

I personally use scale=haasnsoft for upscaling anime to 4k.

>why don't you use a script so you can cut clips in mpv
dang. had no idea there was a script for that.

Is it any of these?

github.com/mpv-player/mpv/wiki/User-Scripts

I see mpv_slicing.... that it or is there something else?

that one

I use this
gist.github.com/Zehkul/25ea7ae77b30af959be0
You can convert to other file formats as well.

and I use this to crop
github.com/occivink/mpv-scripts

thx anons. gonna install this stuff right away. I always wanted to cut out clips but it was always a pain with ffmpeg

Will it work on win with Shinshiro's build?

Taken out of context. wm4 was referring specifically to the situation on feature level 10_0 GPUs like the 9600 GT, since ANGLE does not support high-bit depth FBOs on these platforms, even though raw Direct3D does. This means you can't use fruit dithering with ANGLE on these cards, but it probably still works with dxinterop (since that card supports OpenGL 3.3.) If you have a feature level 10_1 card or greater or you use dxinterop, you don't need to worry. In general, mpv and ANGLE are worse on old hardware in Windows than mpv on Linux, but it makes no difference with new hardware.

I ran it in valgrind in case it helps.
spit.mixtape.moe/view/9ca24217

So "ANGLE" with a RX 480 is fine?
I think the RX 480 supports level 12_1

Yep, should be.

>Run in the main mpv repo directory (with ./build/mpv since it looks for shaders in ./wip_shaders).
>If it crashes, try --vulkan-direct=no. If it still crashes provide a log with -v.

So what you're saying is that mpv is still the best player on Windows for me since I have a 7700K and a 1080 Ti?

1080 ti supports 12_1 so it should be good with ANGLE backend

Yes

I've been using dxinterop all the time since Angle was shit back when it first came out.

Is it better now?

Same result. Is there more documentation anywhere? I didn't see that in the README or man pages.

ANGLE works better with my RX 480.
My average frame timings while upscaling a High 4:4:4 Predictive@L5 720P with ANGLE are 11ms and with dxinterop are 17ms.

Ok, where is the Vulkan? The manual doesn't have any mention of it.

Cool shit. But you have AMD and I have Nvidia so it's probably different for us.

It's still in alpha

Is this true? In my experience hardware is preferable because it reduces heat and stops my laptop fans from spinning up as well as saving battery, but I'd stop using it if it was messing up the colours.

hwdec if you have shit computer

no hwdec if you have good computer

How can I try it out? I build mpv everyday and it seems vo=vulkan isn't recognized. Do I have to pull from another branch?

...

Take in count it only works for Linux for now

See pic related

Alright. I did grab that fork, but I'm not running wayland. I run into a segmentation fault right away, that sucks.

did you Also don't resize the window.

You can use x11 too.

It doesn't open at all. Give me some time, I'll give it another go soon.
Alright. I did just go with vo=vulkan on the mpv.conf and nothing else. I'll try what was already mentioned.

bump

I tried with the post you mentioned and had no luck with it.
Here's what I get normally:
$ ./mpv ~/Videos/Backlog/\[HorribleSubs\]\ Shingeki\ no\ Kyojin\ S2\ -\ 37\ \[1080p\].mkv --vulkan-direct=no
Playing: /home/user/Videos/Backlog/[HorribleSubs] Shingeki no Kyojin S2 - 37 [1080p].mkv
(+) Video --vid=1 (*) (h264 1920x1080 23.810fps)
(+) Audio --aid=1 --alang=jpn (*) (aac 2ch 44100Hz)
(+) Subs --sid=1 --slang=eng (*) (ass)
[vo/vulkan/wayland] failed to connect to a wayland server: check if a wayland compositor is running
[vo/vulkan] Requesting extensions:
[vo/vulkan] VK_KHR_surface
[vo/vulkan] VK_KHR_xlib_surface
[vo/vulkan] GPU listing:
[vo/vulkan] 0: GTX 970 (discrete)
[vo/vulkan] Using device: GTX 970
[vo/vulkan] Alignments:
[vo/vulkan] optimalBufferCopyOffsetAlignment: 1
[vo/vulkan] optimalBufferCopyRowPitchAlignment: 1
[vo/vulkan] minMemoryMapAlignment: 64
[vo/vulkan] Best device memory (heap 1, size 6044550144 bytes) flags:
[vo/vulkan] VK_MEMORY_PROPERTY_HOST_VISIBLE_BIT
[vo/vulkan] VK_MEMORY_PROPERTY_HOST_CACHED_BIT
[vo/vulkan] VK_MEMORY_PROPERTY_HOST_COHERENT_BIT
[vo/vulkan] Best queue family (0) flags:
[vo/vulkan] VK_QUEUE_GRAPHICS_BIT
[vo/vulkan] VK_QUEUE_COMPUTE_BIT
[vo/vulkan] VK_QUEUE_TRANSFER_BIT
[vo/vulkan] VK_QUEUE_SPARSE_BINDING_BIT
[vo/vulkan] Requesting device extensions:
[vo/vulkan] VK_KHR_swapchain
[vo/vulkan] Using the Xlib backend
[vo/vulkan] Supported present modes:
[vo/vulkan] VK_PRESENT_MODE_FIFO_KHR
[vo/vulkan] VK_PRESENT_MODE_FIFO_RELAXED_KHR
[vo/vulkan] VK_PRESENT_MODE_IMMEDIATE_KHR
[vo/vulkan] Using mode: VK_PRESENT_MODE_FIFO_KHR
AO: [alsa] 44100Hz stereo 2ch float
VO: [vulkan] 1920x1080 yuv420p
[vo/vulkan] Starting a reconfiguration!
Segmentation fault

>inb4 smug remarks about shitty anime or cuck card
Also, the full log: pastebin.com/yux1YLWn

./build/mpv

what's the best config for an i7-7700 laptop? Not sure if I should be using hwdec or not, some people in this thread make it seem bad. Right now I'm using
vo=opengl
profile=opengl-hq
hwdec=vaapi, and nothing else. Ideally I want settings that won't make my laptop heat up or waste battery.

# Video settings
vo=opengl
opengl-backend=dxinterop
hwdec=no
video-sync=display-resample

profile=opengl-hq
scale=ewa_hanning
cscale=ewa_lanczos
scale-radius=3.2383154841662362
scale-blur=1.12
cscale-radius=3.2383154841662362
cscale-blur=1.025
sigmoid-slope=10.0

deband-grain=0
deband-iterations=2
deband-range=12
deband-threshold=48

You're running linux I suppose, use vaapi-copy, that way it won't fuck up the color space.

I tried running it from the repo root with ./build/mpv and got the same crash as him (I'm ).

Yes I'm on linux. How does vaapi-copy differ from normal vaapi?

Why the fuck these scalers?

memes