-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bundle macOS App and upload it as artifact #13529
Conversation
Download the artifacts for this pull request: |
079325f
to
65922db
Compare
Really nice to see this. Would it be possible to create a macOS arm64 binary also? |
yes definitely possible, that was my plan. i have everything 'planned' out, just need to test a few more things in the workers, test that everything works properly and then will add arm builds too. there will be some limitations though, eg the bundles will only work on systems of the same version, eg the min macOS version is set to the one where it was built on. because of that i want 4 runners+builds. newest macOS version and the one 2 versions prior, for arm and intel. though there are only arm runners for macOS 13+14 atm. |
ba91447
to
6c8b6d4
Compare
rpaths can be relative to the current object folder path. resolve those paths.
e179478
to
fa113e7
Compare
The latest arm64 artifact works well on my MacBook with m2 processor. 🎉 Though I had to run I have only found one small issue. If I play a hevc mp4 file from the terminal or drop it on the mpv.app bundle the video plays correctly. But if I start the app and then drop the same file on the window that says "Drop files or URLs to play here", the file starts playing (I get sound) but the window only shows flashing colors. This was using config: If I use the default config instead the window is only black (sound playing). |
that's normal, the app is signed with a pseudo identity. you can also just hold the
this issue has already been reported #13505, though the title is still a bit misleading. seems to be introduced with a newer moltenvk version. you can work around that by toggling the video, shortcut is _ (underscore) |
before errors and outputs where ignored from the subscript and the main script didn't fail nor did it output anything. with this change the script properly outputs everything to stdout and stderr. in the case the dylib script fails the whole script fails now. the main function in dylib_unhell was kept since it can still be used individually without the oscbundle script. the script had to be renamed with an underscore to make it importable.
2bfc9da
to
4585819
Compare
for now we only have 2 intel builds for macOS 12 and 13, and 1 arm build for macOS 14, because there are only runners for those macOS versions and architectures. if we want more/need more combinations, we probably need to cross compile. though that is out of scope of this PR. i tested the comment changes on my fork here Akemi#13 |
Just curious, is hw acceleration with videotoolbox enabled in this build? If I play a hevc file with verbose log I got:
Is that expected? |
also add architecture to artifact name
also explicitly enable those and remaining macOS features.
it uses the standard ffmpeg from homebrew, how exactly it is configured i don't know. but yes hardware decoding is working with those builds. but like your log says here a log with
|
I see. Thanks for the tip. With hwdec=auto I also get:
|
No description provided.