mpv: latest release with native GUI and gpu-next

[barracuda156]

Native cocoa GUI, app bundle, full screen, gpu-next vo (libplacebo with GL2), ffmpeg 8, altivec support in dav1d and libvpx

 

[barracuda156]

Installable as mpv-devel: https://github.com/macos-powerpc/powerpc-ports/commit/7538cfa55ad478b37cd7ae7f9040c2916ba07ceb

Needs updated libass and libplacebo (already in PPCPorts).

 

[f54da]

neat, i knew it could be done! Pretty minimal set of patches, all things considered https://github.com/barracuda156/mpv/commits/cocoa/)

 

[Andrew-R]

Spoiler: libvpx-vp9_error

It works with fullscreen mode now on 10.6.8 but libvpx-vp9 decoding suffer from errors.

mpv file -vd=libvpx-vp9 should switch decoder to libvpx-vp9 from ffvp9.

 

[barracuda156]

Spoiler: libvpx-vp9_error

View attachment 2647570

It works with fullscreen mode now on 10.6.8 but libvpx-vp9 decoding suffer from errors.

mpv file -vd=libvpx-vp9 should switch decoder to libvpx-vp9 from ffvp9.

1. `libvpx-vp9` is an opt-in, not default; does default playback work as expected?

2. To debug libvpx-vp9 specifically I need debug log and to know if errors are video-specific or not.

 

[Andrew-R]

1. `libvpx-vp9` is an opt-in, not default; does default playback work as expected?

2. To debug libvpx-vp9 specifically I need debug log and to know if errors are video-specific or not.

Yes, default works (but for 1080p30 drops frames).

I tried two videos (yt-dlp downloaded webm), both show this error.

I think you have enough AMVs to produce debug logs yourself ....

 

[barracuda156]

Yes, default works (but for 1080p30 drops frames).

I am not sure we should expect literally perfect playback with 0 frames dropping, but there is a room for improvement, and current ffmpeg does not yet have altivec in its VP9.

I tried two videos (yt-dlp downloaded webm), both show this error.
I think you have enough AMVs to produce debug logs yourself ....

Thanks. Well, I will test with several videos both in mpv and ffmpeg to see if I get any failures, but I will move the topic elsewhere, since it is unrelated to mpv (I mentioned it along just because it is something new, but libvpx is an external library, mpv just uses it when forced to).

 

[barracuda156]

@Andrew-R Ok, it is interesting. I do indeed get same error messages with webm, but not mp4 (both are vp9 and use libvpx). However despite errors playback of webm works, and apparently better than ffmpeg native vp9: with this sample 29 frames dropped with libvpx-vp9 vs 62 frames with default vp9 decoder.

Same mpv, same libvpx, same arguments, just different files:

I did not try webm, so did not notice these. Will try addressing the issue soon.

@Andrew-R Could you confirm no frame decoding errors with mp4? For example https://samplelib.com/mp4/sample-10s-vp9.mp4

 

[barracuda156]

@Andrew-R Ok, decisive now: bug is real, but totally unrelated to either our mpv or altivec. Reproduceable with pure-C build of libvpx and ffplay.

P. S. Activate non-altivec libvpx (or rebuild with `libvpx -altivec), run `ffplay -loglevel verbose -vcodec libvpx-vp9 somefile.webp`, should throw out identical messages.

 

[Andrew-R]

@Andrew-R Ok, decisive now: bug is real, but totally unrelated to either our mpv or altivec. Reproduceable with pure-C build of libvpx and ffplay.

P. S. Activate non-altivec libvpx (or rebuild with `libvpx -altivec), run `ffplay -loglevel verbose -vcodec libvpx-vp9 somefile.webp`, should throw out identical messages.

Thanks for debugging. I spend my time hacking a bit mplayer's configure so it enables libvpx-vp9 specifically when build with internal ffmpeg.

It also shows this error msg at webm decoding.

Image is not corrupt, just it feels like only keyframes show up ...