@FriendofBernie in any case, this is not the place for such discussions. open a ticket and we can talk there
@FriendofBernie @unfa you know it is in the archlinux repos already, right?
if you plan to build it yourself, better to try to understand the process a bit first. trying to build without "make" is just.. well you wont be able to build much at all of anything.
I dont use arch, I cant help there, you are on your own when building software. IMO users should not be doing that really. if you are not a developer in any way, trying to build things results in a bad time as you dont know how to fix it
@guenther ok, so just rumors as usual. would be great to not spread them around as if they were fact though. it has never been officially confirmed as far as I know
@guenther do you have a source on this?
I'll be streaming an announcement about Cardinal very soon. This is a new exciting open-source modular audio plug-in created by @falktx based on VCV Rack!
https://www.youtube.com/watch?v=HapldC7rROc
#unfa #Cardinal #LinuxAudio #LibreAudio #Audio #Eurorack #Modular
@gcrkrause @unfa it is nothing new exactly. and they always had this stance anyway.
even their GPLv3 license is unclear if is even valid. they require extra work which is unenforceable by GPL rules. when asked for comment they say nothing back.. :/
I went to ask JUCE devs since Steinberg is just quiet about it. https://github.com/juce-framework/JUCE/issues/1027
@colinsmatt11 right yes, which is kinda what rust developers are doing. A lot of C++ concepts do not apply to rust, so a pure conversion is not ideal.
I did something similar myself for DPF where I went with a custom API-incompatible implementation.
On both cases the final binary is ABI-compatible with regular VST3. As far as users are concerned, all approaches result in valid VST3 plugins
@colinsmatt11 a pure reimplementation that would just convert the existing C++ code into something else would for sure be problematic, but Steinberg doesn't even want clean-from-scratch implementations.
As far as I am aware, but obviously not a lawyer and all that, implementing something from scratch that targets an existing API is quite okay. No copyrighted code ends up being used.
@colinsmatt11 APIs are not copyrightable, that is enough to handle this whole thing. They still act like they are though.
falkTX has just made the initial release of Cardinal!
The Cardinal plug-in is - to put it shortly - VCV Rack in a bottle. You have a static (and huge) collection of Rack modules to use, specials for communicating with the DAW, ability to receive MIDI CCs and have them act as CV sources inside etc...
https://kx.studio/News/?action=view&url=cardinal-2202-is-now-released
This is what I needed to be able to really use Rack in my projects - while being able to keep them contained in a DAW project.
Thank you, @falktx !
And here we go, tagged Cardinal 22.02, the first official stable release.
Checkout https://kx.studio/News/?action=view&url=cardinal-2202-is-now-released for the announcement and small details about the project.
Have fun!
Now on the blog: a January Activity & Contract Report, with some more details about the newly-available GIMP and Inkscape. https://www.haiku-os.org/blog/waddlesplash/2022-02-05_haiku_activity_contract_report_january_2022/
Virtual Playing Orchestra is using sources under mixed licenses - some require you to credit the authors in your music or use a specific license for it.
VPO author suggests that your can use the instruments without attribution. You can't. That'd be in violation of the sample author's copyright.
Instead, use VSCO - these are clearly CC0 licensed instruments that are legally safe to use without violating anybody's rights.
More info here:
https://hilbricht.net/foss-sampled-instruments.html
@trummerschlunk @goaty except it not just a synth (generating sound) it can also be used for FX or sequencing
@klaatu @sprkwd@mas.to Would "Eurorack-style modular synthesizer toolkit" work too, or best to forget about the eurorack label?
I need opinions/suggested for Cardinal's short description.
Something like...
"A Eurorack-style virtual modular synthesis toolkit" or "modular synthesizer audio plugin"
don't like either of them tbh.
it's hard to make a nice and short description that describes it well enough.
Let me know if you got any suggestions you think are good.
Thanks!
@unfa why is "nothing will happen" not an option here? this is all bluffing IMO, pleasing dear investors. aka "it is not our fault that we are losing money, it is those damn europeans and their regulations!"