Desktop: Add dav1d library for AV1 software decoding #99
Conversation
| In practice, H.264 is a good choice for physical Android tablets / smartphones | ||
| as most devices (including old and cheap ones) have hardware decoding support. | ||
| Remember to dispose a VideoPlayer before loading a new one, as some devices | ||
| fail to load the next video otherwise. |
There was a problem hiding this comment.
I agree with this. The same holds true for web - I use H.264 there because older/low-spec hardware lacks hardware-based VP9 decoding and it has only recently been supported by Safari. Not that gdx-video works well on iOS (15) - it ends up opening the raw video full screen - but at least it's better than nothing.
It's a little annoying to ship VP9 for desktop and H.264 for GWT, since the GWT backend doesn't support multiple assets directories, but you can tell Gradle to exclude the web version from the desktop build.
|
Is there a reason why you created a separate Gradle subproject ffmpeg? |
Just to split the FFmpeg build and the build of our own code (Java/JNI) into separate files. I did not get that to work a different way. |
|
I guess I just trust you there and merge it :) |
This PR updates the desktop build files to add AV1 decoding.
For this, the dav1d library is built for each platform and linked into the native shared library.
Tested on MacOS (ARM64), Linux (x86_64), Windows (x86_64)
fixes #83