26 Reply by myfakeacc

(4 replies, posted in Using SVP)

Wait, no, stop.
opengl-early-flush=no is what should fix your issue (it's also mentioned on the wiki page).
video-sync=display-resample is a no-op when SVP interpolates to your display's refresh rate. I would definitely not enable it to prevent side issues due to display-resample machanics in mpv. After all, in this case there are 2 different programs trying to interpolate your video independently.

Go to forum: Using SVP

27 Reply by myfakeacc

(2 replies, posted in Using SVP)

Could be a video with wrong fps value tagged, I've had this before. Not the fault of your hw or svp. You can counter it by changing the target fps options.
edit: best option is to remux the video with a correct fps value. It only takes like 5 seconds.

Go to forum: Using SVP

28 Reply by myfakeacc

(20 replies, posted in Using SVP)

ricouzuki wrote:

Videos that my machine cannot handle have massive frame skipping in mpv whereas VLC keeps playing but just looses audio sync. So I guess this shows what each player's priority is when the system cannot handle the load. I just thought that was interesting.

In this case the video should be slower. The more framedrops the slower the video. Frame dropping is specifically used to avoid this. You can configure mpv to behave the same as VLC does (A/V desync): https://mpv.io/manual/master/#options-framedrop

Go to forum: Using SVP

29 Reply by myfakeacc

(20 replies, posted in Using SVP)

You can try --opengl-early-flush=no with mpv, that might help in your case. When you can get VLC to run fluent then mpv should as well.

Regarding hwdec, only *-copy modes are compatible with vapoursynth filters.

Go to forum: Using SVP

30 Reply by myfakeacc

(111 replies, posted in Using SVP)

I'm using it on a hackintosh with ATI 6870 where it's working pretty good. Works on my 13" rMBP with integrated haswell graphics as well, but only when I disable the retina scaling factor. The integrated graphics aren't that bad, but interpolation on pictures of size 3300x2100 (size of the surface when using a 1680x1050 "retina" resolution) is just too much for it.

Something else: after a change in mpv (kind of recent, I think) I have to use --opengl-early-flush=no to prevent a huge amount of framedrops. There was a change that tried to fix a bug in OSX 10.11 but every fix (including this one) doesn't work for everyone and has side effects. I hope they will continue searching for better solutions but in the meantime I'll add that to my config.
Just a heads-up in case OSX users complain about dropped frames.

Go to forum: Using SVP

31 Reply by myfakeacc

(111 replies, posted in Using SVP)

Oh, for some reason I thought using x2.5 would also end up with a wrong result but this was a mistake on my part, works great. Thanks!

Go to forum: Using SVP

32 Reply by myfakeacc

(111 replies, posted in Using SVP)

Right now I have a video with an incorrectly tagged FPS value. Mediainfo says:

Frame rate                               : 23.810 FPS
Original frame rate                      : 23.976 (23976/1000) FPS

The 23.810 is obviously wrong. mpv of course reports the same value (23.810) but ignores it (mpv usually doesn't care about the container fps value).
Since the actual FPS is 23.976 the speedup calculated by SVP is incorrect and the result is >60fps on a 60Hz display.
2 solutions: remux the video and correct the container FPS value or use mpv with --fps=24000/1001 flag. Unfortunately, since SVP uses media-info's value it doesn't help.

My question: is there a place in SVP where I can overwrite the detected FPS or tell SVP to use the FPS reported by mpv (which I can overwrite using --fps)? Or should I remux?

Go to forum: Using SVP

33 Reply by myfakeacc

(111 replies, posted in Using SVP)

That's possible given that the used APIs are available on the target system.
You usually have a "deployment target (SDK)" option which you can set to 10.9. However, I'm not sure if this would require you to have the 10.9 SDK (which you can have on a 10.10 machine).

Go to forum: Using SVP

34 Reply by myfakeacc

(138 replies, posted in Using SVP)

Chainik wrote:

> mpc-qt

check this out: link big_smile
(a mingw-64 build with Qt 5.5 + mpv-1.dll with vapoursynth + "input-ipc-server=mpvpipe" option hardcoded into mpc-qt sources)

Oh, you are way ahead of me big_smile

Go to forum: Using SVP

35 Reply by myfakeacc

(138 replies, posted in Using SVP)

Just saw this: https://github.com/cmdrkotori/mpc-qt
I think it's kind of new but claims:

A clone of Media Player Classic reimplimented in Qt. (screenshot)

Media Player Classic Home Cinema is considered by many to be the quintessential media player for the Windows desktop. Media Player Classic Qute Theater (mpc-qt) aims to reproduce most of the interface and functionality of mpc-hc while using libmpv to play video instead of DirectShow.
[...]
Features

Nearly everything that mpc-hc does. For the most part, unwritten portions relate to setting options, streaming from devices, and storing favorites.

and apparently some features not available in mpc-hc.
However, the probably most interesting part might be:

Mpc-Qt can be compiled with a libmpv linked to MSYS2's ffmpeg libraries, or by using the prebuilt library from mpv.srsfckn.biz.

implying you can use libraries build by other ppl?

Not sure if actually interesting but wanted to let you know.

Go to forum: Using SVP

36 Reply by myfakeacc

(138 replies, posted in Using SVP)

Ah okay, I didn't know that about Baka MPlayer. That's unfortunate.

Go to forum: Using SVP

37 Reply by myfakeacc

(138 replies, posted in Using SVP)

SMPlayer is not exactly liked by mpv devs because it uses mpv in a deprecated way and SMPlayer users are frequently opening issues at mpv's tracker because of problems caused by options SMplayer is adding.
Personally I don't know the program so I don't want to judge it.

However, I know of one (new) front end that is developed specifically for mpv: http://bakamplayer.u8sand.net/
I'm not using this one either so I can't really tell much about it. Going by the screenshot however, there's a "Settings" menu.

Go to forum: Using SVP

38 Reply by myfakeacc

(138 replies, posted in Using SVP)

mashingan wrote:

mpv is gpu intensive sad
the only way I can watch with mpv is to lower the setting of my svpflow options.

Post your VO config. You can make it everything from incredibly heavy to absolutely negligible.

Go to forum: Using SVP

39 Reply by myfakeacc

(111 replies, posted in Using SVP)

Yes, thanks!
Seems like the fallback works fine:

Media: codec type is H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 [lavc:h264], yuv420p
Media: video 1280x720 [PAR 1.000] at 23.976 fps [constant] (via mpv)
Media: codec type is unknown
Media: MediaInfo failed to extract useful information

Now the only "issue" left for me is mpv crashing when I close it. Since it only happens when closing anyway it's merely a cosmetic thing of course...

Go to forum: Using SVP

40 Reply by myfakeacc

(111 replies, posted in Using SVP)

Thanks!
I'm wondering, why doesn't it use mpv's information in the first place? I'd assume they are most correct because playback should go wrong when mpv has wrong information anyway.

Go to forum: Using SVP

41 Reply by myfakeacc

(111 replies, posted in Using SVP)

Is there any more information you need? I can upload a whole episode if you tell me where

Go to forum: Using SVP

42 Reply by myfakeacc

(111 replies, posted in Using SVP)

It doesn't for my mediainfo:

→ mediainfo S05E01.mp4
General
Complete name                            : S05E01.mp4
Format                                   : MPEG-4
Format profile                           : Base Media / Version 2
Codec ID                                 : mp42
File size                                : 425 MiB
Duration                                 : 43mn 7s
Overall bit rate mode                    : Variable
Overall bit rate                         : 1 377 Kbps
Movie name                               : Stargate Atlantis S05E01 (Search and Rescue) - Sci Fi HD @ - PGor -
Encoded date                             : UTC 2013-11-11 23:02:38
Tagged date                              : UTC 2013-11-11 23:26:16
Writing application                      : HandBrake 0.9.9 2013052900

Video
ID                                       : 1
Format                                   : AVC
Format/Info                              : Advanced Video Codec
Format profile                           : High@L4
Format settings, CABAC                   : Yes
Format settings, ReFrames                : 6 frames
Codec ID                                 : avc1
Codec ID/Info                            : Advanced Video Coding
Duration                                 : 43mn 7s
Bit rate                                 : 924 Kbps
Width                                    : 1 280 pixels
Height                                   : 720 pixels
Display aspect ratio                     : 16:9
Frame rate mode                          : Variable
Frame rate                               : 23.976 fps
Minimum frame rate                       : 23.974 fps
Maximum frame rate                       : 23.981 fps
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 8 bits
Scan type                                : Progressive
Bits/(Pixel*Frame)                       : 0.042
Stream size                              : 285 MiB (67%)
Writing library                          : x264 core 130 r2273 b3065e6
Encoding settings                        : cabac=1 / ref=6 / deblock=1:0:0 / analyse=0x3:0x113 / me=hex / subme=7 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=1 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=-2 / threads=12 / lookahead_threads=2 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=0 / constrained_intra=0 / bframes=6 / b_pyramid=2 / b_adapt=1 / b_bias=0 / direct=1 / weightb=1 / open_gop=0 / weightp=2 / keyint=240 / keyint_min=24 / scenecut=40 / intra_refresh=0 / rc_lookahead=40 / rc=2pass / mbtree=1 / bitrate=924 / ratetol=1.0 / qcomp=0.60 / qpmin=0 / qpmax=69 / qpstep=4 / cplxblur=20.0 / qblur=0.5 / ip_ratio=1.40 / aq=1:1.00
Encoded date                             : UTC 2013-11-11 23:02:42
Tagged date                              : UTC 2013-11-11 23:26:16
Color range                              : Limited
Color primaries                          : BT.709
Transfer characteristics                 : BT.709
Matrix coefficients                      : BT.709

Audio
ID                                       : 2
Format                                   : AAC
Format/Info                              : Advanced Audio Codec
Format profile                           : LC
Codec ID                                 : 40
Duration                                 : 43mn 7s
Bit rate mode                            : Variable
Bit rate                                 : 448 Kbps
Maximum bit rate                         : 533 Kbps
Channel(s)                               : 6 channels
Channel positions                        : Front: L C R, Side: L R, LFE
Sampling rate                            : 48.0 KHz
Compression mode                         : Lossy
Stream size                              : 138 MiB (33%)
Title                                    : Stereo
Language                                 : English
Encoded date                             : UTC 2013-11-11 23:02:42
Tagged date                              : UTC 2013-11-11 23:26:15
→ mediainfo --version
MediaInfo Command line,
MediaInfoLib - v0.7.76

Go to forum: Using SVP

43 Reply by myfakeacc

(111 replies, posted in Using SVP)

Ah sorry... I didn't know one existed...
It fails to extract video information. Once I start a video:

22:56:40.288 [i]: VideoPlayer: mpv connected, waiting for the video info...
22:56:40.543 [i]: VideoPlayer: mpv git-717380a
22:56:40.657 [i]: Media: MediaInfo failed to extract useful information
22:56:40.657 [i]: Media: codec type is unknown
22:56:40.657 [E]: VideoPlayer: unable to extract video information
22:56:40.883 [i]: Media: MediaInfo failed to extract useful information
22:56:40.883 [i]: Media: codec type is unknown
22:56:40.883 [E]: VideoPlayer: unable to extract video information
22:56:41.407 [i]: Media: MediaInfo failed to extract useful information
22:56:41.407 [i]: Media: codec type is unknown
22:56:41.407 [E]: VideoPlayer: unable to extract video information
22:56:41.933 [i]: Media: MediaInfo failed to extract useful information
22:56:41.933 [i]: Media: codec type is unknown
22:56:41.933 [E]: VideoPlayer: unable to extract video information
22:56:42.459 [i]: Media: MediaInfo failed to extract useful information
22:56:42.459 [i]: Media: codec type is unknown
22:56:42.459 [E]: VideoPlayer: unable to extract video information
22:56:42.980 [i]: Media: MediaInfo failed to extract useful information
22:56:42.980 [i]: Media: codec type is unknown
22:56:42.981 [E]: VideoPlayer: unable to extract video information
22:56:43.481 [i]: Media: MediaInfo failed to extract useful information
22:56:43.481 [i]: Media: codec type is unknown
22:56:43.481 [E]: VideoPlayer: unable to extract video information
22:56:43.978 [i]: Media: MediaInfo failed to extract useful information
22:56:43.978 [i]: Media: codec type is unknown
22:56:43.978 [E]: VideoPlayer: unable to extract video information
22:56:44.480 [i]: Media: MediaInfo failed to extract useful information
22:56:44.481 [i]: Media: codec type is unknown
22:56:44.481 [E]: VideoPlayer: unable to extract video information
22:56:44.984 [i]: Media: MediaInfo failed to extract useful information
22:56:44.984 [i]: Media: codec type is unknown
22:56:44.984 [E]: VideoPlayer: unable to extract video information
22:56:45.480 [i]: Media: MediaInfo failed to extract useful information
22:56:45.480 [i]: Media: codec type is unknown
22:56:45.480 [E]: VideoPlayer: unable to extract video information
22:56:45.984 [i]: Media: MediaInfo failed to extract useful information
22:56:45.984 [i]: Media: codec type is unknown
22:56:45.984 [E]: VideoPlayer: unable to extract video information
22:56:46.481 [i]: Media: MediaInfo failed to extract useful information
22:56:46.481 [i]: Media: codec type is unknown
22:56:46.481 [E]: VideoPlayer: unable to extract video information
22:56:46.980 [i]: Media: MediaInfo failed to extract useful information
22:56:46.980 [i]: Media: codec type is unknown
22:56:46.980 [E]: VideoPlayer: unable to extract video information
22:56:47.515 [i]: Media: MediaInfo failed to extract useful information
22:56:47.515 [i]: Media: codec type is unknown
22:56:47.515 [E]: VideoPlayer: unable to extract video information
22:56:47.541 [W]: PlaybackObjectsCollection: id not exist

As you probably know the "middle" part about being unable to extract information loops until I close mpv which then causes the last line to appear.
And I just noticed it only affects a few files, all of them being local mp4 (h264) files and all of them work with my local copy of mediainfo. I tried to cut you a small sample of such a video but this sample then suddenly works... (tried to produce sample with: "ffmpeg -ss 0 -i in.mp4 -t 1 -c copy out.mp4" so no reencoding).
Any other information I can deliver?

Go to forum: Using SVP

44 Reply by myfakeacc

(111 replies, posted in Using SVP)

The latest preview (just updated) completely fails detecting for me. Even using "open with SVP..." doesn't work anymore.

Go to forum: Using SVP

45 Reply by myfakeacc

(111 replies, posted in Using SVP)

Chainik wrote:

> Why does SVP need to downscale in the first place?

it doesn't "need" but "can"
to reduce CPU load at the first place

so, the question is simple:
1. when we watch 3840x2160 video on 3840x2160 screen it renders pixel-per-pixel, obviously
2. what about watching 3840x2160 video on 1920x1080 "Retina" screen? will it be rendered pixel-per-pixel OR it will be scaled down to 1920x1080 by mpv and then processed by some magical internal OS X scaler?

When the selected (logical) resolution is 1920x1080 then the physical resolution is 3840x2400 (because 16:10) and mpv would not (and could not) create a window larger than that. It would then scale the video source to this window if necessary (which it isn't, in this case). I'm... 99% confident.
This must be tested on a 15" machine, mine is 13" though. Do you have me a 2560x1440/1600 video, then I can test this with a 1280x800/2560x1600 logical/physical resolution.
However, I assume it is the same for images and for an image of size 2560x1440 on a screen set to 1280x800/2560x1600 logical/physical it works the way I just outlined:

→ mpv IMG_7499.jpg -v --fs | egrep '\d+x\d+'
[...]
        vd: Decoder format: 2560x1440 yuv440p bt.601/full CL=mpeg1/jpeg
        vf:   [in] 2560x1440 yuv440p bt.601/full CL=mpeg1/jpeg
        vf:   [out] 2560x1440 yuv440p bt.601/full CL=mpeg1/jpeg
   cplayer: VO: [opengl-hq] 2560x1440 yuv440p
vo/opengl-hq: Resize: 2560x1600
vo/opengl-hq: Window size: 2560x1600
vo/opengl-hq: Video source: 2560x1440 (72:72)
vo/opengl-hq: Video display: (0, 0) 2560x1440 -> (0, 80) 2560x1440
vo/opengl-hq: Testing user-set FBO format (0x805b)
vo/opengl-hq: Create FBO: 16x16 -> 16x16
vo/opengl-hq: Texture for plane 0: 2560x1440
vo/opengl-hq: Texture for plane 1: 2560x720
vo/opengl-hq: Texture for plane 2: 2560x720
vo/opengl-hq: Resize: 2560x1600
vo/opengl-hq: Window size: 2560x1600
vo/opengl-hq: Video source: 2560x1440 (72:72)
vo/opengl-hq: Video display: (0, 0) 2560x1440 -> (0, 80) 2560x1440
[...]

Please note that this is only the case because the width is with 2560 already the maximum size for a window at this resolution (as in your case it would be with 3840). If possible, mpv would create a window of size 5120x2880 for an image of size 2560x1440 since the backing scale factor is 2 (in all current retina macs). This follows Apple's recommendations for developers -- at least that's what I was told, I'm not an OSX developer.

The magical internal scaler is the window server btw. This is also the reason why I can "set" my display to a resolution of 3360x2100 which is physically not possible with my display. It is scaled down by the window server before sent to the display.

Go to forum: Using SVP

46 Reply by myfakeacc

(111 replies, posted in Using SVP)

> Note that mpv's window opens in 1920x1080 logical pixels = 3840x2160 physical pixels so I've no idea HOW it renders the video in this case.
It does this because that's actually the "official" and recommended way Apple wants you to handle high dpi.

Why does SVP need to downscale in the first place? Is it not possible to let mpv do this and take advantage of it's scaling algorithms?

Go to forum: Using SVP

47 Reply by myfakeacc

(111 replies, posted in Using SVP)

Sent one (yesterday). Let me know if you want more/different resolutions!

I've once reported that mpv crashes when closing the player when the SVP VS filter was added once (even when it got removed by the time mpv is closed). Want to add: mpv also crashes when SVP is closed while it is running (probably an obscure case... wanted to let you know nonetheless).

Go to forum: Using SVP

48 Reply by myfakeacc

(111 replies, posted in Using SVP)

Well, what to say except it works just fine, thanks!
I have used (try to use) MVTools before but it was just way too slow for my laptop, with SVP I get fluent results even with an iGPU* (no 1080p ofc big_smile). I can't wait to test it on my hackintosh at home with a more juicy GPU and CPU.

Can we also ask questions here?
Does the "Optimize for" setting change the used shader? As in: is the sharp one used when one selects "Animation"?


* I should maybe add that I'm disabling retina scaling while doing it otherwise the additional scaling done by the window manager would hurt performance

Go to forum: Using SVP