x265 neon patch for Apple Silicon #4

Closed
opened 2022-05-22 07:58:08 +00:00 by martinr92 · 7 comments
martinr92 commented 2022-05-22 07:58:08 +00:00 (Migrated from gitlab.com)

The latest x265 release does still not contain the neon patch provided by Apple.
But it has been added already 9 months ago to the x265 master branch:
https://bitbucket.org/multicoreware/x265_git/commits/4bf31dc15fb6d1f93d12ecf21fad5e695f0db5c0

The latest x265 release does still not contain the neon patch provided by Apple. But it has been added already 9 months ago to the x265 master branch: https://bitbucket.org/multicoreware/x265_git/commits/4bf31dc15fb6d1f93d12ecf21fad5e695f0db5c0
martinr92 commented 2022-05-22 07:58:08 +00:00 (Migrated from gitlab.com)

assigned to @martinr92

assigned to @martinr92
martinr92 commented 2022-05-22 07:59:51 +00:00 (Migrated from gitlab.com)

Since there is no timeline for a new release of x265, I validate a workaround for this:
https://bitbucket.org/multicoreware/x265_git/issues/563/patch-neon-arm64-improvements

Since there is no timeline for a new release of x265, I validate a workaround for this: https://bitbucket.org/multicoreware/x265_git/issues/563/patch-neon-arm64-improvements
martinr92 commented 2022-05-22 09:19:46 +00:00 (Migrated from gitlab.com)

This issue is based on a conversation of the FFmpeg mailing list:
https://ffmpeg.org/pipermail/ffmpeg-user/2022-May/054888.html

This issue is based on a conversation of the FFmpeg mailing list: https://ffmpeg.org/pipermail/ffmpeg-user/2022-May/054888.html
martinr92 commented 2022-05-25 17:46:36 +00:00 (Migrated from gitlab.com)

Version 3.5 does still not contain the neon patch for Apple Silicon

Version 3.5 does still not contain the neon patch for Apple Silicon
martinr92 commented 2022-05-25 17:51:12 +00:00 (Migrated from gitlab.com)

mentioned in commit 91c084751a

mentioned in commit 91c084751a5c0aa66d3bd11a246f3888078fdccd
martinr92 commented 2022-05-25 17:53:18 +00:00 (Migrated from gitlab.com)

As mentioned in 91c08475:
The temporary solution is to build the master branch instead of the release itself. As soon as the next release comes out we switch back to this release.

As mentioned in 91c08475: The temporary solution is to build the master branch instead of the release itself. As soon as the next release comes out we switch back to this release.
martinr92 commented 2022-05-26 18:35:02 +00:00 (Migrated from gitlab.com)

new builds are now available (snapshot and release):
https://ffmpeg.martin-riedl.de

new builds are now available (snapshot and release): https://ffmpeg.martin-riedl.de
martinr92 (Migrated from gitlab.com) closed this issue 2022-05-26 18:35:02 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
ffmpeg/build-script#4
No description provided.