Hi Aleksid, Any new news re: ffmpeg on Apple Silicon?
For everyone else, does ffmpeg en/decode performance generally scale with CPU cores, GPU cores, both or neither? Or does it use the “media engine” block(s)? Is there any way to tell which parts of the chip are being used? Or is this all hidden/obfuscated by the video_toolbox API? I’m very curious to see how the M1 Max would run certain types of tasks. > On Aug 7, 2020, at 1:02 PM, Aleksid <beautyofno...@gmail.com> wrote: > > Hi, > > Just for information. Today I successfully compiled FFmpeg 4.3.1 for Apple > Silicon (macOS 11 Beta Big Sur) on Apple Developer Transition Kit. > > Also I was able to include FFmpeg shared libraries for my test app. > > I used basic configure options to make sure that FFmpeg works on arm64: > > ./configure --prefix=/usr/local/Cellar/ffmpeg/4.3.1 --enable-shared > --extra-cflags="-fno-stack-check" --enable-gpl --enable-version3 > --enable-hardcoded-tables --enable-pthreads --enable-nonfree > > I discovered only one issue (probably my mistake). dylibs work only when I > put them to /usr/local/Cellar/ffmpeg/4.3.1/lib folder > If I put dylibs into my APP bundle /Contents/Frameworks these dylibs fail > to load, despite the fact that I load dylib using absolute file path from > my folder. > _______________________________________________ > ffmpeg-user mailing list > ffmpeg-user@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-user > > To unsubscribe, visit link above, or email > ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe". _______________________________________________ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
