Native Instruments Supersaw synth

[machinesworking]

You clearly don't understand what happened with this instrument, what Reaktor is and what this instrument does. And that's ok. Ask Chat what a "Reaktor ensemble" is and how one is made.

Sure I do, and you clearly are misrepresenting what I said

All I am doing is quoting what Matthew from NI said himself on the official NI forum

"In fact, Super*Saw is the first product built with a new platform update to Reaktor, that will eventually open to all builders. It empowers Reaktor builders to create discrete, standalone plug-ins running the Reaktor engine under the hood, with high resolution user interfaces, dedicated authorization, distribution and installation mechanisms. A.G. Cook and friends were creating and using the patches that became this product long before they became this product."

https://community.native-instruments.co ... ent_265884

So taking official communication from NI at their word, A.G. Cook had developed some patches/presets in Reaktor a long time ago.

I still wonder what you think the issue with that is supposed to be.

I don't take any issue with it, my only issue is that $99 is to much for this plugin. Other than that I have never expressed any issues with this plugin, but once again you are misrepresenting what I said

My point is that NI is going to open the floodgates to make Reaktor a haven for Vibe Coding Plugins. You can draw your own conclusions as to if that is good or bad

Where are you getting the "Vibe Coding" part? You might be assuming that since they mention

Super*Saw is the first product built with a new platform update to Reaktor, that will eventually open to all builders. It empowers Reaktor builders to create discrete, standalone plug-ins running the Reaktor engine under the hood, with high resolution user interfaces, dedicated authorization, distribution and installation mechanisms.

That is means Vibe Coding? because I'm not finding it in your link. Evil Dragon here mentioned that the "Komplete GUI" platform was a set of tools that would be used in the future to fix Reaktors Windows 95 GUI issues at least front facing, I think that's what Matt is talking about here.

[IvyBirds]

You clearly don't understand what happened with this instrument, what Reaktor is and what this instrument does. And that's ok. Ask Chat what a "Reaktor ensemble" is and how one is made.

Sure I do, and you clearly are misrepresenting what I said

All I am doing is quoting what Matthew from NI said himself on the official NI forum

"In fact, Super*Saw is the first product built with a new platform update to Reaktor, that will eventually open to all builders. It empowers Reaktor builders to create discrete, standalone plug-ins running the Reaktor engine under the hood, with high resolution user interfaces, dedicated authorization, distribution and installation mechanisms. A.G. Cook and friends were creating and using the patches that became this product long before they became this product."

https://community.native-instruments.co ... ent_265884

So taking official communication from NI at their word, A.G. Cook had developed some patches/presets in Reaktor a long time ago.

I still wonder what you think the issue with that is supposed to be.

I don't take any issue with it, my only issue is that $99 is to much for this plugin. Other than that I have never expressed any issues with this plugin, but once again you are misrepresenting what I said

My point is that NI is going to open the floodgates to make Reaktor a haven for Vibe Coding Plugins. You can draw your own conclusions as to if that is good or bad

Where are you getting the "Vibe Coding" part? You might be assuming that since they mention

Super*Saw is the first product built with a new platform update to Reaktor, that will eventually open to all builders. It empowers Reaktor builders to create discrete, standalone plug-ins running the Reaktor engine under the hood, with high resolution user interfaces, dedicated authorization, distribution and installation mechanisms.

That is means Vibe Coding? because I'm not finding it in your link. Evil Dragon here mentioned that the "Komplete GUI" platform was a set of tools that would be used in the future to fix Reaktors Windows 95 GUI issues at least front facing, I think that's what Matt is talking about here.

I thought I explained it before, but let me do so again in an expanded way

I never said that Super*Saw was Vibe Coded. All I did was make an observation regarding Super*Saw and how it fits into the new Native Instruments ecosystem and where that is heading moving forward

Based on the communication of NI on the NI Forum, soon users will be able to turn patches, and Ensembles made with Reaktor into stand alone plugin virtual instruments that will be for sale. Super*Saw is the first example of EXACTLY that.

So in the future you and I and anyone can also make a patch/ensemble in Reaktor and turn that into a stand alone plugin. My guess is NI will sell them in some kind of marketplace and take a significant cut because the whole thing is sitting on their code

It's a rather ingenious way to make revenue for inMusic. You let other people design and build your plugins and then you sell them and make money

Anyway the question then becomes how are these going to be made? Currently you can build your own Patches in Reaktor all by hand if you choose, and then in the future you could sell them as part of the new Reaktor platform.

However currently you can also use various AI tools to Vibe your own patches and Ensembles in Reaktor and in the future you can then sell them as stand alone instruments. You can use Gemini or Claude and it will give you instructions on exactly how to build what you are trying to build in Reaktor.

You can give an AI explanation of what you want the instrument to do and will give you a step by step guide on how to build it in Reaktor including going deep into Reaktor core with all of the needed math and instructions

And then you can also use AI to design the GUI for you

My observation after reading the NI forum post was that this is really going to become a haven for people that want to Vibe Code plugins, as in lots of ways it will be easier than using other tools currently to Vibe Code plugins

Again you can take that as a good thing or a bad thing, it's up to you and I am not arguing either way

I also wonder if you own Reaktor if you will be able to make your own plugins for your own personal use, with or without the assistance of AI. I currently enjoy making my own instruments for my own purposes with my own GUI with and without the assistance of AI and it's something I look forward to messing around on Reaktor

[motomotomoto]

This thread is weird

AG Cook is an absolute titan in terms of pop music influence and sound design

If you think you can recreate the sounds in this synth, and the ease with which they can be musically modified yourself using your plugin chain, great, but I’d guess it would take you so long you would be working for $1 an hour

And finally, the fact that this contains the ACTUAL reaktor patches that were used in so many legendary productions is epic.

Unlike so many plugins which attempt to reengineer or model a famous effect pedal chain or synth this is the actual thing, exactly like it’s heard on so many hit records

If you aren’t into it, fine, but don’t act like this is somehow less valuable than 99 for another stupid modeled compressor, clipper, or guitar pedal emulation

[Vortifex]

Can I get an example of one of these legendary productions so I can get a handle on the typical use of this synth?

[enCiphered]

The funniest part of these threads is how confidently development effort gets reverse-engineered from a product announcement. Apparently, if something looks simple from the outside, it must have taken an afternoon to build. That's a remarkable level of certainty for people who have never seen a single line of the code, the DSP, the testing pipeline or the productization work.
Love how software engineering becomes wonderfully simple the moment someone else is doing it.

[Tiles]

Yup, have to agree here. The hardest part in development is to make a piece of software look and act simple. This usually means the designer and developer did an excellent job. I definitely like the simplified UI. Everything is pretty self explaining.

[nordickvr]

Native Access still requires Rosetta?

In fact like I wrote it’s NTKDaemon that asking for Rosetta.

Recently about half the installers I used asked for Rosetta.
Here’s an excerpt of the explanation offered by a developer who fixed it:
“The plugin binaries inside the [plugin installed] installer are fully universal (they run natively on Apple Silicon, no Rosetta involved). What was missing was a small declaration on the installer package itself telling macOS that the package supports Apple Silicon. Without it, the Installer app plays it safe and asks for Rosetta before it even opens - misleading, but harmless.”

Apple Silicon chip is there since many years now and Rosetta is about to disappear in a month or so…
Time to do the homework?

[ere2learn]

Can I get an example of one of these legendary productions so I can get a handle on the typical use of this synth?

[Lbdunequest]

Am i blind or there there is no demo for real?

[chk071]

Am i blind or there there is no demo for real?

The latter.

[mcbpete]

Was trying to think of what that reminded me of and then it came to me:

[motomotomoto]

Can I get an example of one of these legendary productions so I can get a handle on the typical use of this synth?

Brat album by Charli xcx

[IvyBirds]

The funniest part of these threads is how confidently development effort gets reverse-engineered from a product announcement. Apparently, if something looks simple from the outside, it must have taken an afternoon to build. That's a remarkable level of certainty for people who have never seen a single line of the code, the DSP, the testing pipeline or the productization work.
Love how software engineering becomes wonderfully simple the moment someone else is doing it.

Native Instruments themselves said how it was developed on their official forum however. You don't need to look at single line of the code, the DSP, the testing pipeline or the productization work you just have to take Native Instruments at their word

[Vortifex]

Thanks. Sounds like a rave/hoover track. Are you sure the synth was used on it?

Brat album by Charli xcx

Thanks. Not gonna listen to the whole album. But he named a couple of tracks himself in the promo vid. Standard supersaw sound really. But then it's kind of hard to make a supersaw sound like anything else so I'm not sure what else I expected

[machinesworking]

I thought I explained it before, but let me do so again in an expanded way

I never said that Super*Saw was Vibe Coded. All I did was make an observation regarding Super*Saw and how it fits into the new Native Instruments ecosystem and where that is heading moving forward

Based on the communication of NI on the NI Forum, soon users will be able to turn patches, and Ensembles made with Reaktor into stand alone plugin virtual instruments that will be for sale. Super*Saw is the first example of EXACTLY that.

So in the future you and I and anyone can also make a patch/ensemble in Reaktor and turn that into a stand alone plugin. My guess is NI will sell them in some kind of marketplace and take a significant cut because the whole thing is sitting on their code

It's a rather ingenious way to make revenue for inMusic. You let other people design and build your plugins and then you sell them and make money

Anyway the question then becomes how are these going to be made? Currently you can build your own Patches in Reaktor all by hand if you choose, and then in the future you could sell them as part of the new Reaktor platform.

However currently you can also use various AI tools to Vibe your own patches and Ensembles in Reaktor and in the future you can then sell them as stand alone instruments. You can use Gemini or Claude and it will give you instructions on exactly how to build what you are trying to build in Reaktor.

You can give an AI explanation of what you want the instrument to do and will give you a step by step guide on how to build it in Reaktor including going deep into Reaktor core with all of the needed math and instructions

And then you can also use AI to design the GUI for you

My observation after reading the NI forum post was that this is really going to become a haven for people that want to Vibe Code plugins, as in lots of ways it will be easier than using other tools currently to Vibe Code plugins

Again you can take that as a good thing or a bad thing, it's up to you and I am not arguing either way

I also wonder if you own Reaktor if you will be able to make your own plugins for your own personal use, with or without the assistance of AI. I currently enjoy making my own instruments for my own purposes with my own GUI with and without the assistance of AI and it's something I look forward to messing around on Reaktor

OK so the vibe coding part is just from the fact that you can vibe code a Reaktor ensemble, but then you proceed to speculate whether you can use the new front end NI talk about in that thread, to assemble VST/AU plugins without vibe coding?

Currently there is a process or at least there was a process to secure your Reaktor Ensemble for commercial use only. Not many people currently sell Reaktor Ensembles but it happens, I think it's pretty expensive to do, more so than Kontakt libraries with left browser icons etc.

From what I can tell mostly with the new front end for Reaktor it's more about it being usable on modern computers and not looking like MineCraft. You're jumping to vibe coding as a threat to being able to create reaktor Ensembles in this new environment without using vibe coding, is where you kinda jumped into conspiracy theory logic:

New Thing we are not fully aware of.

Other thing that can be used with this new thing.

Speculation that the Other thing will make new thing crazy easy and poorly assembled.

Speculation that Other thing will be necessary to make New thing.

????

Profit.

It's a GUI remodel that is more like a nice front end for spaghetti interface code from what Evil Dragon mentioned, so far there's not much indication in that thread it's going to change the process in any drastic way besides being easier to use.