One of the Flucoma people here, @Sam_Pluta pinged me about this thread (thanks!):
@igormpc just to signal that if there’s anything I can do to help diagnosing the cause of the plugins killing the server for you, please shout
@madskjeldgaard You’re so fast! The graph_loop_grain Ugens only appeared yesterday Just a warning: they are in support of a upcoming paper led by @groma, and should probably be regarded as research code (although lots of fun). I’d be wary about relying on them in a production environment just yet*! In the near future, we’d hope to integrate them into the main package.
Thanks!! This is Arch Land so we love bleeding edge software so no worries there. That said, graph_loop_grain seems to work nicely!
I need to update the prebuilt flucoma package soon as well, I haven’t updated it with the beta 1.0 stuff yet so that might fix some of @igormpc’s issues
Installing plugins on Raspberry Pi and other single board computers
If you want to install plugins on a Pi or similar SBC running manjaro arm or arch arm, use the plugin packages ending in git. They have been modified to be compatible with those platforms (and in some cases, including Flucoma and MI UGens) build and install a smaller number of plugins (excluding those that are exclusive to x86 architectures).
For example to install a bunch of plugins on a Pi, run:
yay -S supercollder-mkplugins-git supercollider-flucoma-git supercollider-mi-ugens-git supercollider-sonoro1234-ugens-git supercollider-vbugens-git supercollider-maths-git
Thanks to the developers of those for helping make the plugins compatible.
Word of warning
Installing these packages can take a long time since they will compile the plugins from source which is heavy duty work for the processors in single board computers.
Hi @madskjeldgaard ! Did you manage to successful compile and run this autotune UGen ? I compiled it with no big warnings. But it is not allowing the server to boot showing this message:
> *** ERROR: dlopen '/home/myusername/.local/share/SuperCollider/Extensions/AutoTune/AutoTune.so' err '/home/myusername/.local/share/SuperCollider/Extensions/AutoTune/AutoTune.so: undefined symbol: mayer_realfft'
> Server 'localhost' exited with exit code 0.
Yes, but I still have the same problem… There is a brief instruction on the .sc file about how to use, but I saw people creating issues on github about usage and bugs (also about the impossibility to compile on windows… )
The arch package will bill and install it automatically (I’m guessing you’re not on an arch based system since you are compiling yourself) but here are the basic commands I used (see full details in the PKGBUILD file PKGBUILD - aur.git - AUR Package Repositories) :
Yeah arch based systems are basically the best supported linux distributions right now. You can basically install everything now with very little effort.
If you want to try out archb ut not spend a ton of time setting up, you could check out Garuda https://garudalinux.org/
I would say that setting up a running Arch system (even for audio production) looks more daunting from a distance then it really is. The Wiki is so good and it doesn’t take a huge amount of time to follow all the installation instructions etc. (Given some basic computer system knowledge, I guess.) The bonus is having inside knowledge and control over one’s own system… And once it’s up and running the amount of packages and ease of their installation/updating is bliss.
Very much agreed! I’d also add that one of the benefits of using mainline Arch vs an Arch-based distro is that the Arch forums and IRC channels tend to be pretty strict about not supporting Arch derivatives, so imo the time to consider an Arch-based distro is AFTER you already know your way around Arch and its packaging tools, not before.
That’s a good point. I learned it this way. It was brutal but I am happy that I did it.
Regarding the forums - I see your point but IMO the forums are pretty useless anyway. I’ve only had really rude and wrong responses from people there unfortunately (which thankfully doesn’t reflect the wider arch community which I find helpful and generally nice).
Just a warning: they are in support of a upcoming paper led by @groma, and should probably be regarded as research code (although lots of fun). I’d be wary about relying on them in a production environment just yet*! In the near future, we’d hope to integrate them into the main package.