new kino https://github.com/mpv-player/mpv/pull/17395#discussion_r2790985801

https://mpv.rocks/

i see no reason to update to the latest release

>>108165637
sloppa

File: 540928.jpg (92 KB, 600x600)

92 KB JPG

ikachan status?
ikadev knows about reverse engineer windows dlls?

File: 68427a3ef6226f5494db28e2f(...).jpg (432 KB, 1136x2000)

432 KB JPG

>>108166476
just released a new version which fixes gelbooru image loading
currently working on custom booru support

zewia aka sizumam aka linearschizo

>>108167888
kill yourself zewia

>>108165654
nobody cares wm4 you are irrelevant now.

Still broken for pornhub

File: 1759984097168449.png (180 KB, 1891x1496)

180 KB PNG

>>108169891
your ip range must be blocked or something

the performance issue I had with commit 8407df979f6d8bb29e15b9412e769639bc3763c0 was fixed when Arch updated libplacebo and ffmpeg
somehow it's averaging triple the FPS of the previous "good" mpv version that I was benchmarking against
either something was seriously wrong with Arch packaging or mpv/libplacebo devs outdid themselves with 0.41/7.360.0

File: Screenshot 2026-02-17 at (...).png (185 KB, 1176x577)

185 KB PNG

>>108170022

>>108169891
update your yt-dlp

>>108165511
>small

>>108170332
use commad.. yt-dlp --update-to master
that should work..

>>108170107
>either something was seriously wrong with Arch packaging
Arch has been packaging libplacebo wrong for as long as they've been packaging it. Use Tumbleweed, haasn is the maintainer for that one himself.

>>108170401
>yt-dlp --update-to master
That doesn't seem to work if you install it via brew
I will just wait for the brew repo to be updated

Why did yt-dlp stop seeing 1440p for live streams and only download 1080p?

The processed video shows it correctly. I wish I'd noticed this earlier so I could check the formats.

Is anyone else seeing something similar?

>>108170493
It's been a while but last I knew 4K worked fine with live-from-start.

>>108165482
Anyone know a Debian repo to obtain the latest version of mpv?

>>108170520
testing

>>108170332
i'm not familiar with brew but it could be something wrong with their build, it's strange you've been getting that error for so long

>>108170535
Link?

>>108170578
https://packages.debian.org/search?keywords=mpv&searchon=names&exact=1&suite=all&section=all

>>108170107
You likely were using 16hf buffers with linear transfer which were killing your gpu throughput.

File: Screenshot_2026-02-17.png (5 KB, 400x110)

5 KB PNG

>>108170587
Any thoughts on how to resolve this issue?
>dpkg -i --ignore-depends
?

>>108171320
Don't ignore the dependencies, retard. You're probably better off upgrading your entire system to testing.

You'd need to upgrade all of the dependencies of Mpv to the version in testing if you want to use this deb on stable.

Alternatively, you could use some Distrobox container or something.

File: chair-fold.jpg (71 KB, 597x448)

71 KB JPG

>>108171508
Dude, the version in the apt repository is from 2023. ANCIENT! It's four versions behind.
It seems a major effort is required to manually install each dependency just to use v0.41.0. There's no binaries to be found elsewhere?

>>108171758
Build from source:
https://github.com/mpv-player/mpv-build

Or find an AppImage from some random malware repository.

>>108171758
You are using Debian.

>>108170475
what's wrong with Arch's packaging of it?

>>108171214
that was it, previously I think it defaulted to rgba16hf

profile=high-quality

Rate my config.

>>108171320
use deb-multimedia repos for non amerimutt-cucked builds.
if the versions are not new enough for you, build stuff yourself, or even better, move to Arch.
don't listen to the retard suggesting moving to "testing". that debian release branch is the worst of all worlds. you get neither distro stability nor upstream stability.

>>108172886
>don't listen to the retard suggesting moving to "testing". that debian release branch is the worst of all worlds. you get neither distro stability nor upstream stability.
If he wanted stability he'd be using the Mpv from 2023 like everyone else on Debian.

File: 1421198278663.jpg (47 KB, 376x375)

47 KB JPG

tring to set up a way to sort my active playlist; ideally it would load the sort order from the directory in dolphin, but just a keybind is fine. i'm using playlistmanager.lua, but the sort command doesnt seem to take any options, even though it has various ways to sort the initial playlist ie. name-asc, size-desc

k script-message playlistmanager sort name-asc
shift+k script-message playlistmanager sort name-desc

for example just does the default sort operation on either key. wat do? am i an retard?

https://github.com/mpv-player/mpv/pull/17416#issuecomment-3918208726
>blurs your image when displayed 1: not scaled
literally blurpv

Wayland sisters, our response? https://github.com/mpv-player/mpv/pull/17416#issuecomment-3918208726

>>108170022
what is the legitimate point of watching streamed content through mpv like this if you have to use the website to find videos anyways

>>108176769
This is Wayland's fault. The same thing used to happen in macOS until they worked around it. Fake fractional scaling is worse than no fractional scaling.

>>108176823
I use it for better speed control and scaling quality.

mpv Q.
I want to advance time by 10 seconds using the mouse scroll wheel. How do?

>>108177011
No, blurry but readable is better than tiny but completely unreadable.
The issue here is that Mpv wants to do its own scaling and different compositors are going to handle that differently unfortunately.

The real issue is (You) the meme fag consumer that bought a monitor that requires scaling though. I only have one such monitor I use scaling on (a portable monitor where 150% scaling is just better here). The rest are all set to 100% scaling.

>>108178893
4k monitors pretty much always require scaling, unless you're buying something TV-sized to use as a monitor, but that's niche.

>>108179184
I have a 32" 4K monitor and it's okay at 100% scaling. Not sure if that qualifies as "TV-sized" or not though, it's definitely larger than some but still not as huge as a TV.

>>108179216
I have a 32" 4k monitor too and it's unusable at 100% scaling unless I'm uncomfortably close to it. I leave it at 150%.

>>108179216
>>108179276
how come this is a problem in whyland, but not in X, no matter what DPI is set?

>>108178893
>The real issue is (You) the meme fag consumer that bought a monitor that requires scaling
I have 27" 4K monitors at 200% scaling. That wouldn't cause a problem even with the bad methods of scaling since it's an integer.

>>108169891
stop. watching. porn.

>>108170493
try
--live-from-start --extractor-args 'youtube:player-client=web_embedded'

>>108165482
what exactly does mpv over over libplacebo, or even just ffmpeg? it's like the most barebones possible wrapper over god knows what at this point.

File: 1764924984657207.jpg (285 KB, 1642x1871)

285 KB JPG

>>108165482
I haven't updated mpv in four years.

What has changed since then?

>>108180230
vulkan, wayland, videophile shit, trannies.

>>108180517
Is everyone using ekisu's webm even after 4chan added support for mp4?

>>108179456
X doesn't do fractional scaling without Xrandr hacks (which are also blurry)

>>108181368
you missed the point retard. i explicitly mentioned dpi, because you can simply set Xft.dpi and let GUI toolkits scale accordingly, without fucking with the desktop itself.
where this doesn't work, find a specific toolkit option (e.g. QT_SCALE_FACTOR, sun.java2d.uiScale, ...etc).
if you're not satisfied with the results, adjust application level option(s) (e.g. firefox's layout.css.devPixelsPerPx).
if none of those work, then whatever you're using is not worth using, and you still can hack a "magnifying" solution for that specific window...without fucking the whole desktop.
using xrandr scaling is the same retardation as what whyland is doing, except the latter crowd don't view it as retardation. irony no. #116 from those retards and whoever donkey who didn't cop their retardation yet.

>>108181862
You can do the same integer scaling in Wayland too and it's not blurry as >>108179553 attests. The blurry issue only happens with fractional scales.
If you just set DPI then that does nothing except change fonts. Most UIs don't scale with font DPI

sometimes when I cut and encode a video progress bar gets buggy or it start laggy on as webm on here. why is that and how can I mitigate that? I think -dn might be helping.

>>108181994
probably needs more keyframes, I set the max distance to every 5 seconds
the distance number depends on framerate, -g 150 for 30fps and so on

>>108181977
>Most UIs don't scale with font DPI
what is "most UIs", retard?
the "auto" value of the likes of "layout.css.devPixelsPerPx" is literally derived from dpi. and that is the correct and expected behavior.

File: Screenshot_20260218_162220.png (305 KB, 2582x2045)

305 KB PNG

>>108165482
https://github.com/orlfman/FFmpeg-Converter

my amazing, terrible ffmpeg frontend in qt6. now with x264 support. brought it back.

File: Screenshot_20260218_163351.png (306 KB, 2512x1988)

306 KB PNG

>>108183970

when hdr anime

What's the meta for sharpening and upscaling non anime stuff?

>>108183970
your program is pretty nice, I recommended it to a friend of mine that hates cli and he loves it
just out of curiousity, do you use libplacebo for scaling and HDRtoSDR or some other method?

>>108179931
window controls, GUI, stats panel. You know... the features of mpv.

>>108184775
wow, thank you! means a lot.

scaling is done via whatever the user picks in the scale filter combobox + using zscale (zimg) over regular scale for ffmpeg

current filters for scaling are:
>lanczos - default
>point
>billinear
>bicubic
>spline16
>spline36

hdr to sdr is done via:
>if (toneMapCheck->isChecked()) { videoFilters << "zscale=t=linear:npl=100,format=gbrpf32le,zscale=p=bt709,tonemap=tonemap=hable:desat=0,zscale=t=bt709:m=bt709:r=tv"; }

it pretty much converts the color / tone down to sdr levels. works with both 8 and 10 bit.

File: Screenshot_20260218_205234.jpg (1.58 MB, 7680x2160)

1.58 MB JPG

>>108185103
just pushed a newer build that expands the hdr -> sdr option. now there is a new option called "custom" that allows you to control the desaturation level.

>>108183487
Everything that's not your web browser. Your browser may derive UI scaling from fonts (especially, if the page is using nice relative units instead of hardcoding dimensions everywhere) but nearly everything else doesn't.

File: Screenshot_20260218_232738.jpg (1.23 MB, 7680x2160)

1.23 MB JPG

>>108183004
that's a great idea. i totally copied that and made it functional in my program. thanks for the great idea.

>>108185979
are you just making shit up as you go?

File: b2144e1b29aa94389b9960d30(...).jpg (963 KB, 2894x4093)

963 KB JPG

>>108185979
some desktop environments set ui scale based on font dpi

>>108187493
Just speaking from experience when I had to deal with shitty laptops in the past. Also, if you have multiple displays then it's even worse because Xft DPI is a single global value which makes no sense when you have two or three monitors so you have to find some shitty midpoint or are back to the Xrandr hacks.

>>108187687
>Xft DPI is a single global value which makes no sense when you have two or three monitors so you have to find some shitty midpoint or are back to the Xrandr hacks
qt can dynamically change scale to monitor dpi the window is on on x11

>>108187711
But only if you set some hardcoded environment variable and if you ever hotplug a display (granted nobody does that) then good fucking luck.

>>108187723
the original point was that the whyland crowd were retarded for going with scaling the whole desktop instead of letting GUIs scale based on DPI, so we don't have the likes of MPV worry about this whole retardation.
whyland is not bounded by any "old" limitations. let the DPI be defined in a new way and per display. that would be an improvement. yet they ironically manage to end up in a worse situation with every other design choice they make, and they seem to effortlessly introduce such retardations consistently.

>>108187893
It is defined per-display. They just didn't restrict it to whole integer values so if you want to make your display a blurry mess you can. If you're not a retard you'll use nice whole values instead.

>>108187916
gui toolkits on win32 and x11 can scale their own ui to any fractional scale with no problem because the system doesn't scale the window
only wayland does this shit and blurs your window

>>108188068
macOS scales windows and Windows scales windows unless explicitly told not to in the manifest or during handle creation.

>>108188101
> Windows scales windows unless explicitly told not to in the manifest or during handle creation
all modern windows programs do

whyland tards should just implement lanczos or smth for "scaling", if they insist on being retards lol
or maybe they won't because they don't want to lose their precious "scan out" optimization, an argument i've seen them make before regarding other matters (like the reluctance to implement support for custom shaders).

>>108188101
have you thought about maybe not scaling shit?

just get glasses if you can't see. holy shit.

>>108188101
>but that's a path (some) wintards take
well, that settles it then

>>108189050
That's a terrible idea. Anything that rings will look extremely bad for text.

>>108191018
they can peak/steal the anti-ringing code from bugplacebo.
they want to scale and not see blur, so let's be constructive (lol) and help whyland tards out. other suggestions are welcome.

File: Screenshot_20260219_165112.png (345 KB, 2823x2017)

345 KB PNG

>>108186160
Added a 2 second option to the automatic keyframe calculation and added drag and drop support into the select file input box.

>>108192107
uses fprobe to source the frame rate of the video (or uses the frame rate thats manually set in the frame rate box), then calculates the GOP size based off the seconds * frame rate.

>>108191905
You don't need to "scale" text, tardmongler, it's made of vectors.

File: time.png (56 KB, 2186x369)

56 KB PNG

>>108193175
wow. your ability to follow a thread is quite special. i wonder where you are from.

File: Screenshot_20260219_210938.png (449 KB, 2712x1776)

449 KB PNG

>>108192107
>>108183970
new version has a new button.. color correction.
>brightness
>contrast
>saturation
>gamma
>hue
so now you can mess around with brightness, contrast, etc