-
Notifications
You must be signed in to change notification settings - Fork 68
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
Release for Mac? #28
Comments
Hi @rtrahan504,
Nope, not that I can think of. Building for Mac would probably be more similar to building for Linux, which I have instructions posted here: https://github.com/intel/openvino-plugins-ai-audacity/blob/main/doc/build_doc/linux/README.md But I haven't tried, as I don't have a Mac either :) Happy to review any changes needed to support Mac if someone from the community wants to take a shot. Thanks, |
Thanks @RyanMetcalfeInt8. Everything seems like standard C++. I've honestly never used a Mac, so I don't know where to start. The linux build seems standard too except for a lot of manual building of packages. Maybe just leave this issue up and a Mac user might chime in? |
Yeah, a couple packages need to be built manually -- they're not too bad though.
Sure, let me tag with 'Good first issue' -- maybe someone will volunteer. Cheers! |
I'm not a developer per say but quite surprised no one has jumped on this yet. |
I wasn't going to respond until I'd finished this, but since you asked... I don't recall ever building anything on MacOS before, so this is a bit of an adventure, but I've been working on it and am making some progress. There are some tricks and tips that I've worked through and will try to document properly, but this is roughly where I've got to: Dependencies I think you can then skip everything (although uncertain if libtorch still needs its path exporting) until: Whisper.cpp OpenVINO Stable-Diffusion CPP Audacity initial (vanilla) build
That then builds a broken app, which is probably to be expected given the hamfisted approach I've been taking, but it's getting late... |
Hey Roland - What generation mac are you using? |
MacOS 12.7 Monterey on a 2016 MacBook Pro with Intel. |
I've poked around a bit more but am a bit stuck at this point, and unsure what direction to take next. The Mac build instructions for Audacity are a bit sparse. The main instructions describe using the XCode IDE, which might work - I don't actually know it, but I can't imagine it's insurmountable. Would the next Linux step (the OpenVINO module) work if you built it through the IDE? I'd test it, but XCode requires a more recent version of MacOS. The signing instructions refer to a file called cmake_build.txt, but that was deleted three years ago and doesn't appear to be fully current / relevant. |
Yes, it should. You should be able to drop the
So Mac requires you to sign the binary to use them or something? |
I've been looking into this too as I'd love to have this working on the Mac, but haven't been able to get further than the discussion here and no luck building audacity via the IDE> Anyone else made progress? |
I was able to build vanilla Audacity, and then with the
the main things I did differently than the instructions y'all mentioned were using the homebrew-installed libtorch
and I got an error about an ambiguous usage in
|
hmm, I wonder if it is having trouble resolving some other .so's? I'm not a Mac developer so maybe this tip wouldn't apply, but from the terminal that you run Audacity from, could you do something like |
Google led me to
|
@cshaver It looks like you were almost getting a working build. It can work on Apple M1. To resolve references issues and make models available:
|
This would be so cool to use on a Mac with M1 chip. Has anyone built a working plugin for that yet? |
Yes, the plug-in works for me on Apple M1. I am preparing a build on GitHub. |
That would be great @eukarpov for the likes of me who're not good with Terminal... |
@eukarpov will the build work for user that don’t have M1? |
The build will work for Apple M generation devices as it is based on Arm64. For x64 devices it should be another build. |
Has anyone posted an installer yet? |
@eukarpov |
@shock There was progress on obtaining build artifacts; however, it still lacks some dependencies for the installation to be completed. This weekend could be a date estimation for when the artifacts might be deployed correctly. Please join review Thanks! |
@eukarpov: Great! Sometime today, I'll fork your fork, and have a look at your GitHub build work. I'll message you in your repo... |
Any information or status "HOw to install openvino plugin aduacity on Mac OS Intel"? |
I will allocate some time next week to investigate possibility of an x64 build on macOS. |
I’m looking forward to it. |
@eukarpov how's your investigation going? Will that be possible or not? Thanks for the answer! |
@danruzicka Sorry, I was busy with other things these days. I will try to compile it next week. |
@eukarpov, Thank you so much for your efforts in working on the build for a Mac. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Is there anything inherently in the source code or dependencies that is incompatible to Mac? I don't see anything with a quick spot check. I'm also not a Mac owner or user so I can't even attempt. A friend is hoping for a MacOS release.
The text was updated successfully, but these errors were encountered: