-
Notifications
You must be signed in to change notification settings - Fork 64
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
Almost to the end #32
Comments
Hi @arildnor, Sounds like you were really close indeed!
Hmm, it seems like it's not picking up that a new target was added to the build configuration. Can you double check that you copied One trick for debugging CMake stuff, is that you can add print statements using 'message', and make sure that they show up when you execute the build. For example you can add this to
Let me know how it goes! |
Hi Thanks. Surprised by the fast response.
The line was put in the CMakeLists.txt.
mod-openvino folder copied as described
I will redo the complete chain just to make sure I did not miss out
anything..
The only modification I did was adding
linuxmint:21.1
[ "$os" == "linuxmint21.1" ] ||
to the install_openvino_dependencies.sh
The plugin you are working with is a great tool. As I said I have the text
and stem set up in Python. And also getting chords using autochord. The
chords are really useful. Audacity can then be used as a free Transcribe
program.
My setup is really for processing complete music collections, taking all
albums and tracks and making aup3 files for each "song" for musicians to
investigate their own or others' work. I run it on a 128 GB RAM 16 GB GPU
machine and it takes a bit of time.
For stem separation I use htdemucs_6s. And whisper on the vocal stem.
Chords on all stems without drums, and also individual vocal, bass,
guitar, piano, guitar and other.
You see the offsets and can get more ideas for getting notes out.
I use the whisper large model with nospeechTreshold 0.1 as my default.
Using higher may give text where there is no vocals (using only vocals
stem). I found that in a Beatles song.
I am glad I am retired from work and have time to play with this.
Audacity is great.
Keep up the good work.
regards
Arild Eldøy
…On Sun, Jan 21, 2024 at 4:09 PM Ryan Metcalfe ***@***.***> wrote:
Hi @arildnor <https://github.com/arildnor>,
Sounds like you were really close indeed!
cmake --build . --config Release --target mod-openvino failed.
gmake: *** No rule to make target 'mod-openvino'. Stop.
Hmm, it seems like it's not picking up that a new target was added to the
build configuration. Can you double check that you copied mod-openvino
folder to audacity/modules folder, and that you also added edited
audacity/modules/CMakeLists.txt to add the line
add_subdirectory(mod-openvino)? These steps are described here
<https://github.com/intel/openvino-plugins-ai-audacity/blob/main/doc/build_doc/linux/README.md#audacity-openvino-module-build>
.
One trick for debugging CMake stuff, is that you can add print statements
using 'message', and make sure that they show up when you execute the
build. For example you can add this to audacity/modules/CMakeLists.txt:
message("ADDING OPENVINO MODULE TO THE BUILD!!!!!")
add_subdirectory(mod-openvino)
Let me know how it goes!
Ryan
—
Reply to this email directly, view it on GitHub
<#32 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACPMYFOK3LQA6IC6L2437B3YPUVUDAVCNFSM6AAAAABCD2ZNAWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBSGY3DMMJVG4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
"But the last command : I have the same error. |
Hmm, weird. Another option, after adding
|
Thanks, but after running the above command(with the adjusted directory), I am gettung that: "CMake Error at modules/mod-openvino/CMakeLists.txt:6 (find_package): Could not find a package configuration file provided by "OpenVINO" with any
Add the installation prefix of "OpenVINO" to CMAKE_PREFIX_PATH or set -- Configuring incomplete, errors occurred!" |
Hi @sandoxy, It seems like it is having trouble finding OpenVINO. In the same terminal as you are running Edit: In general, the environment setup in the terminal that you are building from should looks like this:
|
I did every step of the instructions, but in the meantime my terminal was closed. I repeted the last stets, but there is still an error. I will go all all the steps again, including your suggestion. |
After a you try i am still getting this error: gmake: *** No rule to make target 'mod-openvino'. Stop." I used also your suggestions. |
@sandoxy, can you give full log of cmake commands? Thanks! |
Of course. Where do i find that log? Or do you mean just a list of commands i used? |
Hi @sandoxy, sorry, I should have been more specific. When you execute:
Or, if you're following my suggestion where you just build audacity again:
In either case, there is probably a bunch of stuff that is printed to the terminal after entering the commands. Can you just copy and paste this into a text file and share it, just so that I can take a look to see what the issue may be? Thanks! |
Thanks @sandoxy, Did you clone this repo, and copy the I didn't see these steps in the log that you sent, but maybe you did it outside of this terminal? Can you just confirm by sending printed output of these commands:
|
I did it outsider of the terminal
|
Hmm, okay those look correct. Can you try running Audacity cmake / make step again from your terminal, and send me the output? (from inside your existing
|
do i have to replace ../audacity with the actual audacity folder? |
Oh, yes, sorry. You can run the same cmake command that I see in your log:
|
Of cource:
|
Hi @sandoxy, Looks like the CMake command worked (I see the printouts confirming LIBTORCH, whisper, etc.). I think you can just build it now:
And after that completes, if all goes well, you should see |
Hi RyanMetcalfeln8: I don't know why, bug it seems to have worked this time. Now it looks like that; Thanks a lot! |
That's great @sandoxy -- glad to hear it's working. I think I'll update the Linux instructions to explicitly run cmake step again after putting the mod-openvino in place. Anyway, you certainly didn't do anything wrong -- I think I just messed up the explanation of the routine -- but this was very useful. Thanks again! |
Great, I hope this will help other linux-users to install this plugin!:) |
Hi @arildnor, I've updated the Linux instructions (https://github.com/intel/openvino-plugins-ai-audacity/blob/main/doc/build_doc/linux/README.md#audacity-openvino-module-build) to reflect the method that worked smoothly for @sandoxy. If you're still interested in trying this, could you let me know if it works for you? Otherwise, I can close this issue as completed. Thanks! |
Hi. I nearly managed to get it installed on my Linux Mint system. Since my mint is based on Ubuntu 22.04 I added linuxmint21.1 to the setup file where needed. But the last command :
cmake --build . --config Release --target mod-openvino failed.
gmake: *** No rule to make target 'mod-openvino'. Stop.
Probably something I forgot or did wrong
But I just take a break and redo all later.
The good thing is I got a build of the latest version of Audacity and ran it.
I have been working another route to do what the plugin do. I run Demucs, whisper and finding chords in python scripts. Then I import tracks, chords and lyrics from wav and label files generated directly from Python script. With the latest version of Audacity I can use the pipe and get Audacity populated from python direct. I am not able to run demucs and whisper / chord in the same Python run. A lot of issues pop up, not least GPU memory. So it is 3 separate runs with shared variables.
I have for the last year struggled with the Python package nightmare. Using miniconda I manage to get things running, but it takes a lot of different conda environments, and disk space.
The text was updated successfully, but these errors were encountered: