formerly known as cmplayer
this fucking troll image gets me every time
I'm fucking hyped: gl_rework is almost at feature parity with master, the only thing that's missing is the OSD rendering, and a few non-standard upscalers (like bicubic_fast and sharpen*).
We can expect *significant* performance improvements to cscale, in the ballpark from 30%/40% (ewa_stuff) up to 200% or more (separable scalers) of the overall render time.
Smoothmotion has been reworked, it's now based on a frame queue (with some minor issues still left to resolve, like slightly better handling when pausing or framestepping, and also when to queue frames).
This also paves the way for stuff like custom, user-specified pixel shaders, and adds more configuration options for the color management code (including the ability to do gamut/gamma mapping without involving an icc-profile, like the old :srgb option but better).
Whoever made this image is blind
Also, the JND is generally considered to be around dE 2, usually below that level.
dE 4 should be clearly visible to most people.
Generic windows setup:#Video
MPC IDF spotted.
It is already technically superior to MPC:HC in many ways, and it is getting near feature parity with madvr. While using half the cpu/ram, and being fully open source and cross platform. It's still in development and will likely fully suprass mpc:hc soon. MPC is soon going to be fully phased out.
Emulators like retroarch, openemu, higan and others are already using them.
This would relieve the pressure on devs to include every single new hot upscaler/shader that comes out. They only now have to include the most basic and important. And you can imagine years from now, people are still making new upscaling algorythms, and even if the program is dead, users could still use them without updating the code of the program to include them.
User shaders also allow you to do ANYTHING including stupid or novel things for no reason. What does 2001 A Space Oddesy look like when used with a shader meant to replicate the look of a Gameboy screen?
What file format to support? There already exists .cg, .shader, Quark shader folders, etc.
There is admittedly less need for it in media players than in gaming. Retro games are these tiny 240p things, and you need to do SOMETHING when you upscale that to an hd screen. Media is different since it's already a high resolution.
Nothing has changed with respect to that. This is not really changing anything other than the rendering logic itself, so it's mostly just a drop-in replacement of the current code.
Timing will have to be revised separately, and will most likely be done after it lands in master.
This transition is a difference of approximately deltaE 2.2 on a calibrated sRGB monitor.
And finally, this simple geometric shape is drawn with two sRGB colors that are separated by a CIE deltaE 74 of approximately 1.1
If you can tell the shape, then congratulations, either your monitor calibration is shit or you have exceptionally good color perception.
>This would relieve the pressure on devs to include every single new hot upscaler/shader that comes out.
This is not the use case. These custom shaders wouldn't let you upscale things, just transform them.
Examples of a use case could be a barrel distortion filter for viewing things on the Oculus Rift (which is an actual feature request that we've received), or simply for blurring/sharpening stuff.
haha you actually believe the crap you shill, of course it uses half the cpu and ram, mpv can't into scaling algorithms the same way madrv does.
And no ones is gonna use this config pile of shit out of freedumbs zombies.
>And it takes half the ram and cpu all while using the same filters and algos?
Funny thing is, this is even the case before the performance improvements mentioned in >>46912127 have landed.
>Wintards this ass mad that Freetards make better programs than they can ever hope to.
The frontend is sufficient. What else do you want?
Well there's nothing wrong with that one? Or you could try this, it includes all the info
Nah brah it's okay I already placed my order. The thing that bothers me though is that pixel shader stuff >>46912440
My dad is into retro gaming (really likes the GameBoy stuff) and I was wondering if I should buy another mpv for him.
The reason it isn't exactly high on mpv's agenda is that in our renderer, we mostly care about reproducing the source as accurately as possible, whereas user shaders are pretty much only useful for distorting or “enhancing” the image (rather like video filters).
Granted, there are some legitimate use cases - such as the oculus rift thing; and another use case I can think of would be transforming to L*Ch for desaturation (as opposed to clipping in RGB space, which is what the code currently does for out-of-gamut colors*)
* Does not apply to the 3DLUT output, which is always desaturated colorimetrically.
Its already installed once you unzip it, just open a video in it you goddamn retard
>it's a command line program m8,
Whoever is doing the windows version >http://mpv.srsfckn.biz/
should freaking put a disclaimer/trigger warning on the freaking front page that running that program requires using cmd line !!!
but that would be inaccurate
while it's a command line program, you don't need to use cmd to use it, at all
if you accociate video files with mpv.exe (open with > mpv.exe), you can open video directly with mpv, and it will bring up a graphical window displaying the video
>KCP Haruhi is so much more superior to this for windows user that it's not even a contest.
List specific features. It already has most or all of madvr's features and development is improving them and adding more.
>it's sad that mpv doesn't even have anti-tearing feature like KCP
If it doesn't already, it may soon be added. Any features that you think are essential you should bring up on their github and they may add it.
>now millions of prospective users will consider that software amateur tier and broken
mpv is never aimed at those users. They want to keep it simple as possible. It's understood that mpv will be used as a backend in other projects, which will have a standard frontend with GUI that most users require.
There's already bomi, bakamplayer, and others on the way.
It typically uses half the ram/cpu as MPC making it ideal for lower end machines. It loads files incredibly fast on my low end laptop.
It's also a simpler more straight forward program with everything contained in one program. Open up MPC + KCP and a ton of little extra programs open up in your taskbar. Each with their own set of options. It's more complex and messy than it needs to be.
Then you have the menus. Menus piled upon menus and menus. The mpv OSD is so simple it includes all the things people actually need. Advanced options can be handled with the config. And configs are so much better than menus. Simple, easy to navigate, clean, and only containing the relevant information. People are simply scared of config files because they never used them before and don't want to learn, but they are superior.
This is the project to get behind. If it lacks features, then the devs will add to it.
>Why? What does it do better than mpv?
playing back 10 bit videos reliably without tearing
mpv can play up to 16 bit videos just fine; with higher quality than closed source russian botnet alternatives, too.
mpv lets you set a specific swap interval, and even if your implementation of OpenGL is broken, it supports various hacks like glfinish; and also includes support for some platform-specific extensions like for accurate video syncing, like GLX_SGI_video_sync.
tl;dr you are full of shit
>superior anti-tearing measures
>superior chroma upscaling
>superior gamma correction
>superior quality with no shortcuts
>superior features like NNEDI3
madvr blows it so much out of the water it's not even comparable.
This is arguably the case on Windows because of shitty OpenGL drivers, though most people will have no trouble.
>>superior features like NNEDI3
mpv can do NNEDI3 in software with VapourSynth, but it doesn't have a fast GPU implementation like madVR's.
The rest of your post is completely wrong. I'd like some citations, or at least anecdotal evidence for any of the other points. What's a "shortcut?" What's an "anti-tearing measure?" What led you to believe that madVR's "gamma correction" is better? It doesn't make any sense.
and don't forget this >>46922736
that feature only found in MPC with KCP allows it to be a superior player if you have large format external displays like a projector of that latest 70-80 inch flat panels in your living room.
>What led you to believe that madVR's "gamma correction" is better?
the fact that there's actually a control for it?
I prefer mpv. It's better for users who like command line programs and keyboard interfaces. It's lightweight, it starts faster and it seeks faster. It runs on platforms other than Windows.
It has some placebo video rendering features that aren't present in madVR like sigmoidal upscaling and a more correct Jinc filter, but madVR has some placebo features that aren't in mpv like NNEDI3 and error-diffusion dithering. Whether you use or care about any of these features will affect your decision.
Most people won't like it because it doesn't have a graphical user interface.
You're really misunderstanding mpv. mpv is not intended to become popular. It's not intended to "sell" or "go places." It already fits a specific niche (people who like high quality video and CLI software,) and that's where it's staying. Use it if you want.
You might think these threads are designed to advertise mpv, but they're not. They're just a place for mpv users to discuss the player among themselves.
enjoy watching crushed blacks and clipped or crushed whites with mpv
mpv keybinds work based on the character that's produced rather than the position on the keyboard, so if it was bound to [ ], you'd have to use whatever keys produced those characters or change the bindings. By default, I think volume is bound to 9 and 0, not [ and ], so you could try those instead.
What, does it cover your screen so hard it wraps around again?
>superior chroma upscaling
Are you talking about oil painting mode?
>superior anti-tearing measures
Vsync doesn't magically get better or worse. What the fuck do you think mpv's vsync does, only synchronize half the screen?
This is objectively false, madVR has subpar color management (no support for ICCv4 profiles, low quality gamut mapping, incorrect gamma correction/wrong colors)
>superior quality with no shortcuts
“quality” is a vague word used to no effect here. What “shortcuts” do you think mpv is making to sacrifice quality?
>superior features like NNEDI3
You already mentioned this. Twice.
>madvr blows it so much out of the water it's not even comparable.
Nothing's comparable if you're a retard who doesn't have a fucking clue what he's talking about.
>Can't read man pagesgamma=<0.1..2.0>
Set a gamma value (default: 1.0). If gamma is adjusted in other ways (like with the --gamma option or key bindings and the gamma property), the value is multiplied with the other gamma value.
Recommended values based on the environmental brightness:
Brightly illuminated (default)
Pitch black room
Automatically corrects the gamma value depending on ambient lighting conditions (adding a gamma boost for dark rooms).
With ambient illuminance of 64lux, mpv will pick the 1.0 gamma value (no boost), and slightly increase the boost up until 0.8 for 16lux.
NOTE: Only implemented on OS X.
Oh look, it even adjusts gamma automatically based on ambient room lighting.
>the fact that there's actually a control for it?
Have you considered the fact that mpv does the correct thing even without user intervention? Just because madshi is clueless about color management doesn't mean everybody developing high quality media player is.
for what purpose?
Enjoy your distortion of features and oil-painting-esque appearance.
If you want to distort the image this badly, why not just use WarpSharp or something?
>mpv can do NNEDI3 in software with VapourSynth, but it doesn't have a fast GPU implementation like madVR's.
madVR's “fast” GPU implementation also skips the prescreening check, so as a result it's like one or two orders of magnitude slower inherently.
It sort of balances itself out - doing it with the CPU filter isn't as slow as you might think. Also, there's an OpenCL-accelerated avisynth filter for it (with the same caveats), which is probably what madshi stole his code from.
You could try porting that to vapoursynth if you really want to, should be doable.
>not using -af=bs2b:profile=jmeier
Do you hate your ears?