Native Instruments Pro-53 is back as an open-source project (Cmajor port)

VST, AU, AAX, CLAP, etc. Plugin Virtual Instruments Discussion
Post Reply New Topic
RELATED
PRODUCTS
Pro-53

Post

nix808 wrote: Sat Mar 16, 2024 11:48 pm Can I make a free version of Pro-53 with these graphics?
If you mean Pro54, then you can do whatever you like with it *so long* as you make your updates available for others. Basically the source is open source, so you have an obligation to make the source you use to build whatever you make from it open source as well.

Post

GaryG wrote: Sat Mar 16, 2024 11:08 pm
osiris wrote: Sat Mar 16, 2024 9:33 pm That's easy. What it would look like if NI updated it. Just ask A.I. (If only this were around when I was doing SE stuff)
play some pretty exotic scales on that there keyboard
It's from the future, we'll all be using exotic scales whilst flying around on our jetpacks.

Post

For clarification:
The 'CmajPlugin' is a VST3 plugin and gets installed to the standard/default VST3 install location for VST3 plugins - which is 'Program Files\Common Files\VST3' - when you use the binary installer 'cmajor_win_x64.exe' from 'https://github.com/cmajor-lang/cmajor/releases'.
There is no VST2 plugin and 'CmajPerformer.dll' thus also isn't the name of any VST2 plugin, but instead a redistributable binary required by both the VST3 plugin as well as by the command line tool called 'cmaj.exe', which gets installed to 'Program Files\Cmajor\Cmajor'. For the command line tool this 'CmajPerformer.dll' is only required for certain operation(s).
It has to be said though, that in it's current state the plugin is not much of practical use, since it doesn't remember the last loaded cmajor patch - left alone any sound settings from that patch.
Which means, when you reload a project with that cmajor plugin, then tracks using it will not produce any sound, because you first have to again drag'n'drop the patch onto its GUI. At least this is how it behaved for me in EXT64.
- The above quoted block is out-dated! See Edit 2!

Edit:
When it comes to Linux:
Cesare F. from cmajor confirmed, that the Linux binaries (as of version 1.0.2386) currently do not contain that plugin due to a bug in the build/deliver chain.

Edit 2:
As of version 1.0.2397 - pre-release, available since 17.03.2024 ~midday, the CMaj VST3 plugin saves and restores its state correctly. Apparently also state saving/restoring of Pro-54 got a fix.
See here: https://github.com/cmajor-lang/cmajor/releases
This means that it is now really cool to use Pro-54 in a DAW project.
I tested it shortly and main functionality all worked well!
@cmajor: Thanks for the quick fix! :tu:
Last edited by ZonderP on Sun Mar 17, 2024 4:53 pm, edited 4 times in total.

Post

cesare wrote: Sun Mar 17, 2024 8:50 am
nix808 wrote: Sat Mar 16, 2024 11:48 pm Can I make a free version of Pro-53 with these graphics?
If you mean Pro54, then you can do whatever you like with it *so long* as you make your updates available for others. Basically the source is open source, so you have an obligation to make the source you use to build whatever you make from it open source as well.
Is anything built with CMajor the language required to be open source, or just the specific Pro 54 code?

Post

briefcasemanx wrote: Sun Mar 17, 2024 10:38 am
cesare wrote: Sun Mar 17, 2024 8:50 am
nix808 wrote: Sat Mar 16, 2024 11:48 pm Can I make a free version of Pro-53 with these graphics?
If you mean Pro54, then you can do whatever you like with it *so long* as you make your updates available for others. Basically the source is open source, so you have an obligation to make the source you use to build whatever you make from it open source as well.
Is anything built with CMajor the language required to be open source, or just the specific Pro 54 code?
If you seriously think about doing something with cmajor, I recommend reading the license section on their site https://cmajor.dev/docs/Licence

Post

nix808 wrote: Sat Mar 16, 2024 11:48 pm Can I make a free version of Pro-53 with these graphics?
Absolutely. I didn't even post the first stuff it generated. Gorgeous but even more out there.

Post

ZonderP wrote: Sun Mar 17, 2024 10:41 am
briefcasemanx wrote: Sun Mar 17, 2024 10:38 am
cesare wrote: Sun Mar 17, 2024 8:50 am
nix808 wrote: Sat Mar 16, 2024 11:48 pm Can I make a free version of Pro-53 with these graphics?
If you mean Pro54, then you can do whatever you like with it *so long* as you make your updates available for others. Basically the source is open source, so you have an obligation to make the source you use to build whatever you make from it open source as well.
Is anything built with CMajor the language required to be open source, or just the specific Pro 54 code?
If you seriously think about doing something with cmajor, I recommend reading the license section on their site https://cmajor.dev/docs/Licence
Yes, read the above link.

The software is dual licensed, like JUCE and other audio frameworks. Under the GPL licence you can develop and deploy whatever you like so long as you keep what you build open source.

If you want to develop a commercial plugin (closed source) with this, you will need a commercial licence. We've not got this in place yet, simply because we haven't got the infrastructure in place to manage licensees (and meeting GPDR requirements etc). However, the broad plan will be to have a free tier for indie developers below a certain turnover, then monthly fees for small companies, then a bespoke agreement for larger businesses which will include support, that sort of thing.

So, for now, GPL only, but we're getting the sign up process in place which will cover indie developers. I'd expect it to be up and running within the next few weeks, but things have a habit of slipping and i'm rubbish at estimating :)

Post

cesare wrote: Sun Mar 17, 2024 8:52 am
GaryG wrote: Sat Mar 16, 2024 11:08 pm
osiris wrote: Sat Mar 16, 2024 9:33 pm That's easy. What it would look like if NI updated it. Just ask A.I. (If only this were around when I was doing SE stuff)
play some pretty exotic scales on that there keyboard
It's from the future, we'll all be using exotic scales whilst flying around on our jetpacks.
One would hope that the pool of pilots will be far superior to what we have on the ground presently, here in the 50 states. :scared:

Post

ZonderP wrote: Sun Mar 17, 2024 10:22 am As of version 1.0.2397 - pre-release, available since 17.03.2024 ~midday, the CMaj VST3 plugin saves and restores its state correctly.
Confirmed on REAPER/Win11. :tu:

Download:
https://github.com/cmajor-lang/cmajor/r ... g/1.0.2397

Post

Chris-S wrote: Mon Mar 18, 2024 2:00 pm
ZonderP wrote: Sun Mar 17, 2024 10:22 am As of version 1.0.2397 - pre-release, available since 17.03.2024 ~midday, the CMaj VST3 plugin saves and restores its state correctly.
Confirmed on REAPER/Win11. :tu:

Download:
https://github.com/cmajor-lang/cmajor/r ... g/1.0.2397
Awesome, thanks for the confirmation! I'll make this the official release

Post

FREQ dial on Oscillator A doesn't work for me. Anyone else has this problem?

Edit: oh, I got it: when SYNC is on it will not pitch, but only change the timbre!

Post

So I installed this x64 VST plugin: https://github.com/cmajor-lang/cmajor/r ... g/1.0.2724

Sucked https://github.com/cmajor-lang/cmajor/t ... ches/Pro54 using https://downgit.github.io/#/home

I drag'n drop "Pro54.cmajorpatch" onto it in latest REAPER on W11 but no GUI showing up, what gives please?

Post

kujoi wrote: Mon Mar 17, 2025 5:43 pm So I installed this x64 VST plugin: https://github.com/cmajor-lang/cmajor/r ... g/1.0.2724

Sucked https://github.com/cmajor-lang/cmajor/t ... ches/Pro54 using https://downgit.github.io/#/home

I drag'n drop "Pro54.cmajorpatch" onto it in latest REAPER on W11 but no GUI showing up, what gives please?
Better use EXT64 on Windows 7 - where it works nicely! :hihi:

Post

Anyone tried building Pro-54 this on the Mac? I got the standalone, AUv3, and VST3 to work, but the AU shows up as a blank window. On the Mac, I used Visual Studio Code with Cmajor, output JUCE code, CMake'd it, then built (when did we stop saying compiled?) using a couple different versions of Xcode.

I'm so far out of touch with programming and modern tools (though studying the code brought me back, and I was surprised that I could actually make sense of most of it) that I'm not actually sure where the issue may lie. I may switch to Linux and try again, but if anyone got the component to compile correctly, please let me know how you went about it.

Post

Note that other examples compile to AU fine.

Post Reply

Return to “Instruments”