What's your opinion about it?
Is it the ultimate solution for 60hz only monitors?
>>53236184
svp is shit, looks cool but practical can't be used on any average cpu with out boosting to 100%
>>53236216
Maybe with cpu only but what about with gpu?
>>53236184
>Is it the ultimate solution for 60hz only monitors?
Adds a shittons of artifacts, so no
>>53236184
why would you use svp shit when you can have:
https://github.com/mpv-player/mpv/wiki/Display-synchronization
>>53236641
How is that article relevant to the discussion?
>>53236819
mpv's display-resample is far superior to svp for 24p on 60Hz.
>>53236856
Do you have any fucking clue what you're talking about or are you just spouting random garbage?
>>53236916
retard pls.
enjoy your soap opera effect from svp.
>>53237070
Well I guess that confirms it, you're just spouting random garbage.
>>53237196
>arguments: zero
>confirmed troll
>>53237279
>arguments: zero
A claim with no proof requires no proof to dismiss.
>>53237070
enjoy your judder m8
>>53237565
not relevant because there was a whole wiki article and nothing from you
>>53237760
mpv's display-resample doesn't have any judder
>>53237996
>not relevant because there was a whole wiki article and nothing from you
I wrote that wiki article
>>53237996
>mpv's display-resample doesn't have any judder
If you watch a 24 Hz video on a 60 Hz screen, yes it will
wheres the download link senpai
Dude, SVP4 is the fucking best. Works on my machine. i5 3570K at stock speeds.
>>53238019
>didn't read the wiki
>>53239256
>Apart from that, there is also the (somewhat separate) issue of clock mismatch. For example, suppose your audio hardware can only do 44.1 kHz, but your audio is still 48 kHz - or suppose your video is 24 Hz, but your display only runs at 60 Hz. For audio, the solution (resampling) is uncontroversial and well-known, but for video the situation is more complicated. For that, we have an entirely separate article.
https://github.com/mpv-player/mpv/wiki/Interpolation
When is this shit coming out?
where can i find svp 4 full torrent for wangblows
Why each time I get excited about a thing on mpv, there is a thread on 4chan that destroy it?
I think mpv have no future since wm4 gets paid for its development to be include in plex.
And everybody knows that this kind of software is not for watching family videos.
However it seems that physical formats will be dead this year in profit of netflix like shits.
Furthermore netflix like shits needs subscription.
There is unique hidden watermark in streams with auto banning system.
>>53236184
Use CRU to set your monitor refresh rate to 72hz (or another multiple of 24hz) Then use Reclock or MPDN integrated tool to sync perfectly your monitor with the movie fps.
Wouldn't you just interpolate to 30hz for reduced artefacts and to avoid the soap opera effect?
I was always told that there are two types of video:
Film-like: 25fps, 24fps, 30fps
and
Video-like: 50fps, 60fps
You should only interpolate within the two categories.
MPV generally seems to be a waste of time for normal people.
It seems they ripped out useful shit like MEncoder from mplayer and then went about turning it in to the perfect player for people watching 240p jap kiddy porn on 1080p+ displays.
It's borderline useless for anything else and performance is horrible.
>>53242609
>Wouldn't you just interpolate to 30hz for reduced artefacts
Interpolating to 30 Hz and interpolating to 60 Hz is going to give you the same amount of artifacts.
The artifacts come from the bad detection of motion vectors on the source. The target framerate has little effect on it.
>and to avoid the soap opera effect?
I don't see why you would want to _avoid_ this effect. The “soap opera” effect means it's working as intended.
If you're trying to eliminate it, you might as well not use motion interpolation.
>I was always told that there are two types of video:
Bullshit. Framerates are just framerates. Above the point where motion is fluid, there's no extra phase transition.
>>53242943
>It seems they ripped out useful shit like MEncoder
What can mencoder do that ffmpeg can't?
>>53243072
>Framerates are just framerates
'Film rates' are typically done as a stylistic thing.
>If you're trying to eliminate it, you might as well not use motion interpolation.
Motion interpolation is used to avoid judder in the display of video.
Ever wondered why an extremely expensive motion interpolator is used to convert between 50 and 60 for broadcast?
>The target framerate has little effect on it.
The target framerate does have an effect when it is significantly higher than the input.
24 > 60 is more than double.
>>53243171
Have shitty code
Oh wait, ffmpeg does that too. Never mind.
- mpv devs are against motion interpolation
- mpv devs are against complex enhancement shaders
- mpv devs are against 3d
- mpv devs are against doom9
- mpv devs copy/paste ideas from madvr
- mpv devs copy/paste ideas from mpdn
Why should I like something created by hermit devs?
Is vapoursynth a good alternative for people with big cpu with igpu?
I saw there are nice scalers too, which ones is the best for realtime?
>>53236184
>60hz only monitors
every one i've used can be run at 72Hz (3*24Hz), so i do that instead
perfect timing, all-original frames
>>53244030
Damn right.
>>53244030
How do you run them at 72Hz? I have a Dell U2410 and an LG 31MU97-b and they both just support 60 Hz modes.
Even if I manually force something else I just get a black screen.
>>53244196
i've written modelines for various common rates
most tools make 72Hz modes that use too high a pixel clock for "60Hz" monitors
here's mine;
/etc/X11/xorg.conf.d/10-monitor.confSection "Monitor"
Identifier "HDMI-0"
Modeline "1920x1080" 106.82 1920 1928 1952 1960 1080 1083 1087 1090 -HSync +VSync # 50Hz
Modeline "1920x1080" 132.48 1920 1928 2016 2024 1080 1083 1089 1092 -Hsync +Vsync # 60/1.001Hz
Modeline "1920x1080" 130.80 1920 1928 1992 2000 1080 1083 1086 1090 -Hsync +Vsync # 60Hz
Modeline "1920x1080" 164.16 1920 1928 1968 1976 1080 1083 1152 1155 -HSync +VSync # 72/1.001Hz
Modeline "1920x1080" 156.96 1920 1928 1992 2000 1080 1083 1087 1090 -HSync +VSync # 72Hz
Option "PreferredMode" "1920x1080"
EndSection
if you're using something like the windows radeon driver to add custom modes, you might have to enter values like "front porch" and "sync width", they can be derived from these like so;
156.96 1920 1928 1992 2000 1080 1083 1087 1090 -HSync +VSync
this is;
156.96 = pixel clock in MHz
1920 = H display size
1928 = H sync start (H front porch is the above minus this)
1992 = H sync end (this minus the above is H sync width)
2000 = H total
1080 = V display size
1083 = V sync start (see above)
1087 = V sync end (see above)
1090 = V total
-HSync = negative H polarity
+VSync = positive V polarity (not related to what you're thinking of)
>>53244247
>(H front porch is the above minus this)
(H front porch is this minus the above)*
>>53244247
I'm using the proprietary nvidia drivers on Linux.
I've tried out those modeline tools you read about on every wiki page (e.g. cvt), but the numbers they spit out give me black screens.
How do you determine what modelines work and what don't? Is there any automated testing tool that tries them all or something?
Alternatively, what tools are non-shit when it comes to this stuff?
>>53244257
i ended up getting a radeon card because i couldn't get custom modelines to work with the nvidia driver, so good luck with that
you can use them with nouveau, but then your card will likely only run fast enough for video playback...
in my case, i made those knowing my monitor had a pixel clock limit of 165MHz
i also found that generally, i just needed 8 pixels either side of the hsync period, and 3 pixels either side of the vsync period, which you'll notice most of those follow this trend
i determined the pixel clock and total values using this calculator;
http://www.monitortests.com/pixelclock.php
(if someone can get a local copy of this that'd be awesome, it's the only tool i've found that does exactly what i want, and it could disappear at any time)
>>53244306
>i ended up getting a radeon card because i couldn't get custom modelines to work with the nvidia driver, so good luck with that
But radeon card's can't even vsync properly on Linux, I specifically got an nvidia card _because_ the radeon drivers were so shitty.
>you can use them with nouveau, but then your card will likely only run fast enough for video playback...
And probably support none of the OpenGL features past basic triangles. Yeah, I'm not too keen on nouveau either.
>in my case, i made those knowing my monitor had a pixel clock limit of 165MHz
I'm not too sure how far I can push it, given that I'm already driving at 4096x2160 10-bit depth. (Though I can realistically turn that to 8-bit. If doing so would allow me to use 72 Hz instead of 60 Hz, that would be a clear and obvious net gain)
>http://www.monitortests.com/pixelclock.php
that's a pretty handy tool, I'll play around with it a bit later. Thanks for sharing
>>53244306
oh yea, i tested them simply by adding and switching to them using xrandr, keep "xrandr --output HDMI-0 --auto" handy so you can switch back if it fails
with modern lcd's you don't need to worry about damages, they just refuse anything they can't handle
>But radeon card's can't even vsync properly on Linux, I specifically got an nvidia card _because_ the radeon drivers were so shitty.
heh, yea, i use the free radeon driver, it can into vsync just fine, and it's fast enough for my purposes
>And probably support none of the OpenGL features past basic triangles. Yeah, I'm not too keen on nouveau either.
mesa's progressed a lot recently, it can into up to opengl 4.1 nowadays
>>53244357
>heh, yea, i use the free radeon driver, it can into vsync just fine, and it's fast enough for my purposes
Unfortunately, I'm already pushing my GTX 970 to its utmost limits when it comes to upscaling, so it's hard to compromise on anything less - especially considering my AMD cards are already less powerful than the 970 (I have a HD 7950, that's it).
>mesa's progressed a lot recently, it can into up to opengl 4.1 nowadays
(As you say this I'm working on shaders that require 4.3 or higher)
>>53244336
give this a shot;Modeline "4096x2160" 668.16 4096 4104 4152 4160 2160 2163 2230 2233 -HSync +VSync # 72/1.001Hz
>>53244373
>(As you say this I'm working on shaders that require 4.3 or higher)
so you're the guy the other day i tried to help out but couldn't because i couldn't into GL4.3, eh?
at least i can help you with this
>>53244196
Even my shitty HP elitesomething monitor at work supports 72Hz.
>>53244402
Where do I add this modeline? My xorg.conf only has a Monitor section for my secondary monitor (the U2410), which looks like this:Section "Monitor"
# HorizSync source: edid, VertRefresh source: edid
Identifier "Monitor0"
VendorName "Unknown"
ModelName "DELL U2410"
HorizSync 30.0 - 81.0
VertRefresh 56.0 - 76.0
Option "DPMS" "off"
EndSection
I tried adding my own for the primary:Section "Monitor"
Identifier "Monitor1"
ModelName "LG 31MU97"
Modeline "4096x2160_72" 668.16 4096 4104 4152 4160 2160 2163 2230 2233 -HSync +VSync # 72/1.001Hz
EndSection
But starting with this config doesn't seem to have affected anything (i.e. I don't actually see any new modes in `xrandr`'s output)
>>53244499
i'm not really that proficient with xorg configuration syntax, it looks ok to me
i used an example from somewhere and it worked, so i left it
did you completely stop and start X?
for the meantime, you can add new modelines while X is running using xrandr (good for testing)xrandr --newmode "test1" 668.16 4096 4104 4152 4160 2160 2163 2230 2233 -HSync +VSync
xrandr --addmode HDMI-0 "test1"
xrandr --output HDMI-0 --mode "test1"
where HDMI-0 is the appropriate output
also, you don't need to add _72 to the name, using just the resolution will add them as another refresh rate option, see pic
>>53244554
>i'm not really that proficient with xorg configuration syntax, it looks ok to me
It doesn't really look okay to me, to be honest. How would xorg know what the fuck I mean by ‘Monitor1’? I'm basically making up identifiers here, including the “ModelName”. Seems to me like it would need _some_ way of knowing which monitor is which, no?
>did you completely stop and start X?
I started a new X server on :1 using a different FB. That should pretty much be the same thing.
>for the meantime, you can add new modelines while X is running using xrandr (good for testing)
That's what I tried first but the --addmode step fails:X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed request: 139 (RANDR)
Minor opcode of failed request: 18 (RRAddOutputMode)
Serial number of failed request: 41
Current serial number in output stream: 42
I _assume_ this is because the monitor only claims to support 60 Hz, so xrandr is refusing to add a 72 Hz mode to it.
I know that some of my peers get around this problem by spoofing/faking the EDID information, but I'm too dumb to do that.
Doesn't xrandr have some sort of “force” flag to get around this?
>>53244594
>How would xorg know what the fuck I mean by ‘Monitor1’?
no idea, never looked into it
>including the “ModelName”
i haven't set the modelname option anywhere in mine, doesn't really concern me if nothing can tell me what model it is
>I started a new X server on :1 using a different FB. That should pretty much be the same thing.
yea, i did that to start with as well
>That's what I tried first but the --addmode step fails:
i got similar errors with the nvidia driver, i tried lots of things but like i said, i couldn't get the nvidia driver to play nice
using modified EDID information should work, but i didn't end up trying that
>>53244402
Also how did you generate this mode line?
Can you generate one for the 1920x1200 72 Hz monitor too? What about 4096x2160 48 Hz (that one might work better than 72 Hz)?
I pretty much have no idea how to calculate any of this. It's black magic to me
Everything is over complicated on linux, that's a shame.
I would like to switch to ubuntu today and with this thread I felt discouraged.
Hey /g/, do you advice me to just use kodi on ubuntu for perfect playback.
It has checkbox to switch display framerate automatically and sync the audio if needed.
>>53244642
And you can use config file to enable them if you you are not against xml.
>>53244623
>>53244639
Oh, I just found this line.
it was actually in my xorg.conf from earlier tests, just commented out:Option "ModeValidation" "AllowNonEdidModes,NoEdidMaxPClkCheck,NoMaxPClkCheck,NoVertRefreshCheck,NoHorizSyncCheck"
I set it and now I could add your suggested modeline with `xrandr` just fine.
What happens is something like this:
1. Monitor goes blank
2. Monitor flashes a single frame of something. Like a few horizontal lines
3. Monitor goes blank again
4. Monitor flashes again
5. Monitor goes blank for a longer time
6. Repeats forever
>>53244639
i used the page i linked to before, and the "rules" i mentioned here >>53244306
>Can you generate one for the 1920x1200 72 Hz monitor too?
sure
Modeline "1920x1200" 181.44 1920 1928 1952 1960 1200 1203 1284 1287 -HSync +VSync # 72/1.001Hz
(this, like the other, is 72/1.001Hz, which i presume is what you want, since most "24fps" media is really "23.976" (24/1.001))
48Hz isn't as well supported in my experience, unless you're targeting a crt television (i actually do sometimes run a crt tele at 48Hz as a second monitor)
>>53244642
kodi will switch display refresh rate automatically /if they're available/, we've been talking about making them available
kodi can't switch to say, 72Hz if it's not there
>>53244698
nice, might have to increase the H/V porch value, the values i use have only been tried on 1920x1080 displays
see if you can find out what the monitors' max pixel clock is, too, should be in the specsheet
>>53244763
>see if you can find out what the monitors' max pixel clock is, too, should be in the specsheet
The “spec sheet” is a nonexistant piece of shit, basically what you see here:
http://www.lg.com/us/monitors/lg-31MU97-B-4k-ips-led-monitor
(For the record: LG are absolutely garbage at making their own displays, and I'm never buying from them again. They should stick to panel hardware)
>>53244763
>Modeline "1920x1200" 181.44 1920 1928 1952 1960 1200 1203 1284 1287 -HSync +VSync # 72/1.001Hz
I tried this one on the U2410 and it started displaying a dialog box:
>The current input timings are not supported by the display. Please set the display mode to 1920x1200@60Hz.
>>53244763
>>53244825
I did a quick google search on this one as the monitor is more widely known:
http://www.overclock.net/t/1380527/official-dell-u2713hm-2560x1440-semi-glossy-ips-club/2560
>I own a U2410 which is 60Hz locked, hope its not the case with this one.
>My old U2410 also does 24Hz but it does it with internal 3:2 pulldown, so it brings it back to 60Hz internally.
I'm pretty sure my 31MU97 also does internal 3:2 pulldown, since I “can” technically force it into 24 Hz mode but only over HDMI (yeah, let that sink in) - but it just does internal pulldown which sort of defeats the point completely.
Why is it that in 2016 you basically have the choice between a monitor with non-shit color reproduction and a monitor with non-shit framerates?
I'm seriously considering selling both and getting one of Dell's new 5000€ OLED displays that runs at 120 Hz, simply so I can have the best of both worlds.
>>53244844
give this a shot on the 4K one;
668.16 4096 4104 4152 4160 2160 2168 2225 2233
(+-8px for vsync instead of 3px)
playing with the values except for the pixel clock, display size, and total sizes won't affect the end result
>I own a U2410 which is 60Hz locked, hope its not the case with this one.
>My old U2410 also does 24Hz but it does it with internal 3:2 pulldown, so it brings it back to 60Hz internally.
wow, so they're deliberately refusing rates higher than 60 just because "fuck you"?
all my monitors are cheap shit, i would have imagined these would be the least likely to get higher rates working on
>>53244881
No dice. I strongly doubt you're going to get anything other than 60 Hz to work on the 4K display, to be honest. This thing has such shitty programming in general, and even the fact that they _use_ a 3:2 pulldown layer internally shows to me that they pretty much internally drive the panel at 60 Hz.
At best I would expect some kind of botched conversion from 72 Hz down to 60 Hz, i.e. stuttering everywhere.
iirc that's what I got when I forced it into 48 Hz, too.
So yeah, not getting my hopes up high.
>>53244913
monitors are getting too "smart" for their own good
i miss crts that took what they were given, even if that meant they'd squeel and display rolling garbage
>>53244924
-- not to mention how fast crts could switch modes, you'd get a slight flicker and bam, new mode
none of this blacking out for 5 fucking seconds shit
>>53244940
>tfw no 32" 4K 120 Hz CRT tho
>>53244979
>>53244991
It's okay, OLEDs are coming. Best of all worlds.
Low input lag, zero blacks, high resolutions, high refresh rates, wide gamut by default, perfect color accuracy, perfect viewing angles
Only current problems are the cost and lifetime, and both are improving drastically
>>53245007
when i watch something in bed i forego my laptop and use my phone just because it has an OLED screen which just looks so much nicer
maybe when i'm 50 i'll be able to afford a desktop OLED monitor
The silver lining about 4K monitors and only running at 60 Hz is that 4K content (UltraHD) is actually expected to be 60 Hz.
