Self-compiled FFMPEG binary or updated bundled default native binary?? about a-shell HOT 5 OPEN

I can confirm that you cannot add binaries compiled on a Mac to a-Shell: iOS will only load binaries that are signed with the developer certificate and placed inside the $APPDIR/Frameworks directory. Since the $APPDIR/Frameworks directory can only be accessed during app install time, there is no way for a user to add their own binaries.

I don't fully understand the rest of your question: the bundled ffmpeg version is not that old (2022), and anyway it links with the system VideoToolbox framework dynamically, so it is already having access to all the hardware abilities of your iPad. For licensing reasons, ffmpeg is compiled without the non-free codecs and without the GPL codecs; these maybe the features you are missing, but updating the ffmpeg version will not improve your experience here.

I'm going to update ffmpeg anyway, but I do not expect it will improve your experience.

from a-shell.

Hi,
The TestFlight version of a-Shell mini: https://testflight.apple.com/join/REdHww5C contains a big update: ffmpeg v7.0. Like the previous version, it has been compiled with --enable-videotoolbox --disable-audiotoolbox --disable-gpl --disable-nonfree --enable-libmp3lame --disable-asm, so it has hardware acceleration for h264 and hevc codecs (videotoolbox), no GPL codecs, no non-free codecs. No assembly code and no hardware acceleration for audio codecs (audiotoolbox) because these do not compile. It uses parallelism a lot more than version 5.0, so you should see a difference on your M series iPad Pro.

ffmpeg contains lots of options and use cases, so I'm planning to let people test this version for at least two weeks until I make an AppStore release.

from a-shell.

from a-shell.

There are two types of codecs that I am not allowed to distribute with a compiled app on the App Store:

• the "non-free" codecs, that require paying a fee to the developer for each binary install (but not, crucially, for source code compiled by the user).
• the GPL codecs, since the FSF has decided that the GPL is incompatible with a distribution on the AppStore.

x264 and x265 are the latter. I'll look into libaom. Build 400 (on TestFlight) has been compiled with libaom, and thus has the option to encode to AV1: -c:v libaom-av1.

As for "the neon-optimizations and asm-code that Apple provided", they just cause compilation errors on iOS.

from a-shell.

I cannot find any option to compile the "sv-av1" codec. I assume you meant "SVT-AV1". Is there any advantage in having two different AV1 encoders, AOM-AV1 and SVT-AV1?

from a-shell.