Exoplayer VS FFmpeg

I tried using the Fire TV but it has huge problems with some 4K HDR video formats that goes black screen. It is an issue reported by multiple users for Plex but it's the same for all applications on FireTV. This is the issue on github for Exoplayer: https://github.com/google/ExoPlayer/issues/11096

Media3 is the new home for APIs that enable you to create rich audio and video experiences. If you’ve used libraries like ExoPlayer, MediaCompat, or Media2, you’ll find Media3 to be familiar. However, instead of using these separate libraries, Media3 provides a unified API for playback use-cases and also expands to cover new use-cases like video editing and transcoding. The APIs are simple to use yet powerful, customizable to meet your needs, and reliable and optimized so you can build for the diverse Android device ecosystem. (https://android-developers.googleblog.com/2023/03/media3-is-ready-to-play.html)

Haven't done video work in years, but checkout the DefaultTrackSelector and start following around in the source code. Android Studio should allow you to do this all in the IDE. It's really the only way to learn/understand this stuff.

Also in regards to having to tell PC rtspt:// and Quest rtsp:// and waiting for ExoPlayer to fail over to TCP (8 seconds delay) https://github.com/google/ExoPlayer/issues/11069

I wonder if it's an ExoPlayer bug?

See the full changelog of ExoPlayer 2.18.2. Some notable changes are:

This started happening on Android when they enabled DRM on the streams. Assuming you use a device with Android 12 or later, you can just use Race Control TV to fix the issue. With Android 11 or earlier, Race Control TV also stutters due to this issue, which can be fixed by a custom build of the the app and force-enabling the fix mentioned in the issue.

If one day https://github.com/google/ExoPlayer/issues/3438 is done then yes. Until then no I can't.

GPL2

Since FFmpeg is GPL2, doesn’t that require CompressX to disclose its source code?

IANAL, apologies if I miss understand license requirements.

https://github.com/FFmpeg/FFmpeg?tab=License-1-ov-file

This turns out to be a lot of assembly macros to help write one x86 assembly. https://github.com/FFmpeg/FFmpeg/blob/master/libavutil/x86/x...

The sibling comment recommending compiler intrinsics is probably the best way to go for writing SIMD code. A mixture of `` style types and intrinsics to specify instructions is a solid 90% solution compared to assembly.

If you want that last 10%, I think macros are putting the emphasis in the wrong place. They're a somewhat easy way to build up a language abstraction which will work if held carefully, but I'm confident the dev experience using this abstraction when you write invalid code will be deeply confusing.

I would suggest to write a parser instead of the macros. That'll tell you clearly when the syntax is invalid (though possibly not with much precision) and it'll give you a place to put semantic analysis for where valid syntax encodes nonsense. Do the equivalent of the macro expansions on the parsed tree instead of on the text. Emit asm as the "back end".

You might have heard of FFMPEG or ImageMagick for image and video edition in a programmatic way. MoviePy is a Python module for video editing (Python wrapper for FFMPEG and ImageMagick). It provides functions for cutting, concatenations, title insertions, video compositing, video processing, and the creation of custom effects. It can read and write common video and audio formats and be run on any platform with Python 2.7 or 3+.

There are many cloud-based tools and websites that can convert your images, but the problem with these tools is that you usually have to upload the files for them to be processed, and some of their services are not free. In this article, I'd like to introduce a piece of software called FFmpeg, which allows you convert the images locally with one simple command.

To run the demo locally, be sure to have Python 3.11 and FFmpeg installed.