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
Official Linux build for ARM architectures #419
Comments
Very cool indeed. Travis CI supports arm64, so it's really a matter of whether AppImage does it or not. We are currently using linuxdeploy for the actual packaging process and as far as I can tell there's no trace of ARM builds in there... |
Well, musescore has an ARM AppImage, so it's doable. :) LEt's dig into the details when I confirm Giada is actually working fine on my Odroid. |
I just built it on Odroid! Yass! Didn't test it thoroughly yet, I've got to drag along my sample library first. But it runs and I didn't see anything suspicious yet. I ran tests and I don't know what to make out of it, no experience with those. I'm guessing it won't work with actual samples and sounds, huh?
EDIT: Today I played with Giada for a bit more and everything seems to work very well... The memory footprint was in order of 30MB, the CPU utilization around 15% on one of six available cores. Actually it took much more processing power to display a stream of debug messages in a terminal window. :) |
Nice! Did you also try with Jack as the underlying sound system? Wrt the tests: they must be run outside the |
I just tried Jack and yup, it does work just fine. :) I haven't tried MIDI yet, as I sold all my mini/micro controllers recently, and lost an auction of a Launchpad S that I wanted to get instead 😿 The tests also run smoothly when I followed your advice.
So, yay! All that needs to be done is to figure out how to make an ARM AppImage. Maybe the musescore guys would share their insight? ;) |
Wow I'm very impressed, especially for the CPU utilization around 15%. Did you also try to load multiple channels and fiddle around with them - removing, changing properties, ...? I'm asking this because there are some default/unoptimized atomic instructions in the code that might be very slow on ARM architectures (#348 will help a lot on that point). |
Well, the test was very basic to be honest, just two samples lopping :D |
One more thing worth noting, Raspberry Pi OS is currently available 32-bit only. As RPi holds major share of the SBC market, I'm guessing that armv7 or armv8 build should be available too. |
Stuff to keep in mind: https://gist.github.com/fm4dd/c663217935dc17f0fc73c9c81b0aa845 |
It's not true. There is a 64-bit version. They just tuck it away. I have been running it for over 6 month. |
No official release though, and well hidden from general public. My point was that 32-bit release should be available as well. |
Any news on this? or are there any special build instructions for this architecture? I'd really love to have an official armv8 build. Giada will be a strong competitor in the low spec music making market. I'm currently running a rpi4 and was looking at begineer friendly music tools. Giada is the best fit so far except for this little detail :( |
Just follow the build instructions and all should be well. I dont remember taking any extra steps. I haven't tried building with vst support though. |
Im trying to compile it on pi 3 32bit . Just for fun and to see if I can contribute in the future, since there is a Giada version on my apt . The only strange thing I noticed is a weird error with ssh and github , I had to -> echo -e "Host github.com\n\tStrictHostKeyChecking no\n" >> ~/.ssh/config otherwise , it wont let me update recursively the repo |
Alternatively , I changed the url in the git config file and it works normally now . Line 15 in 4e6bcf5
Instead of git@github.com:monocasual/geompp.git https://github.com/monocasual/geompp.git , etc with the others |
That's definitely not an ARM-related problem. |
Sorry about that , here I have one . Without VST support it does build , even tho the version through apt seems more stable and efficient for some reason and it has vst support that runs well on my rpi 3. When trying vst3 support I get the following : Any leads would be appreciated, would like to keep up to date |
Just successfully built in my rpi4b (armv7l) with and without VST3 support (however I couldn't find a suitable arm-compiled vst to test this yet). For VST3 support, I had to install these additional dependencies:
And had to add a line in CMakeLists.txt after L505 (as I faced the same errors as @CarloCattano) :
|
Perfect , thanks @Xpktro !! I did build successfully VST3 and VST2 at the same time . I got most of them from the Zynthian repo https://github.com/zynthian/zynthian-plugins VST3 works with @Xpktro instructions . Vst2 requires a few extra steps : I got the vst2sdk from archive.org:
still relevant until vst3 greatness manifests on arm widely , or till giada merges lv2 and then wont be needed for linux at last , since many plugins have already their lv2 available |
Can confirm the full VST2+3 build is working in my setup thanks to the instructions given by @CarloCattano, thanks! Note: The copy command for the vst2 SDK just need a |
Right ,
exactly , forgot that it asks for the files under vst2.x |
Since some people reported that Giada builds even on ARM machines such as Raspberry Pi, it seems like a quite low-effort improvement.
The selection of music production software is limited for this platform (unless you know how to compile stuff), and it might be a good idea to provide an ARM-compatible AppImage for those who wish to try out Giada on their tiny machines. I believe there is not a lot of "competition" on this "market".
Personally I switched to Odroid ARM computer as my daily desktop, due to negligible power consumption and decent performance for light tasks. I will continue my programming efforts on it unless I find something that prevents me from doing so.
I wanted to spark a discussion around the demand for such a feature - do people actually want it, can we deliver it etc.
I can test it, that's for sure :D
The question remains however, does AppImage actually support ARM? Hmm..
The text was updated successfully, but these errors were encountered: