Super 8 - New polysynth by Native Instruments

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

Post

JoeCat wrote: Sun May 05, 2019 5:44 pm
Sinisterbr wrote: Sun May 05, 2019 1:25 pm
chk071 wrote: Sun May 05, 2019 12:43 pm
gentleclockdivider wrote: Sun May 05, 2019 12:41 pm But those saying that S8 it sounds like a generic plugin will probably never be able to separate a great sounding plug from a mediocre one .
TBH, that's what i thought too, when i read generic.

Read the same about Monark on Gearslutz yesterday, by the way. Maybe NI should rather sell some golden ears. :hihi:
You know, these "generic" synths are my favorites. Very simple, great sounding, inspiring, straightfoward. TAL-Mod and Oxium comes to mind.
I'm the kind of guy who hates to play complex synths, hahah

Oxium - still one of my favorite "bread and butter" subtractives - start from init, pick a few waveforms, tweak the filter and some envelopes.

Same wirh Repro, Monark - given what it would have cost to own more than a few in hardware symths years ago, it's awesome to be able to own more than a few, even if the differences are subtle. Not necessary for making great music, but sometimes fun just to play with the same basic sounds and different envelopes, filters, etc...
All XILS synths have this special quality (as repro/diva) that makes them sound like a recorded real synth, and not software.
If only they could improve their GUI..
Last edited by Sinisterbr on Mon May 06, 2019 4:24 am, edited 1 time in total.

Post

Double post

Post

Maybe if I buy this one all my dreams will come true!! :hyper: :hyper: *fingers crossed*

Post

ENV1 wrote: Mon May 06, 2019 12:46 am
AnX wrote:
ENV1 wrote: How else could the plugin even function? How could it process sound and display an UI?
the same way any other vst does?
Is any other plugin made with SE?
yes, the mac equivalent

so, how does a 'normal' vst work, say Diva? What is embedded in that?

if SE was embedded in its vst's, the file size would be huge, its not. :shrug:

Post

lotus2035 wrote: Mon May 06, 2019 4:38 am Maybe if I buy this one all my dreams will come true!! :hyper: :hyper: *fingers crossed*
lotus2035 that won't work because you can't dream with your fingers crossed, everybody knows that.
:hyper: M O N O S Y N T H S F O R E V E R :hyper:

Post

I keep testing this out in hopes I can make a sound... I make a bunch of garbage funny enough.
But hearing some of the presets, this is a synthwave beast. https://www.psychicmodulation.com/phonec.html is another good one for the same price though, also not really any built in effects.

Post

wagtunes wrote: Mon May 06, 2019 2:53 am
Using that same logic, any VST dll made with C++ means that I have C++ when I load a C++ created dll into my DAW. Except I don't have C++. I can't create my own C++ project. I can only use dlls that were created with C++.

However, with Reaktor (at least with the full version) I can take the ensemble created by Reaktor and I can modify it as much as I like.

So comparing a dll made with SynthEdit to a Reaktor Ensemble is just not accurate. They are not the same thing.

But by all means, try to take your SynthEdit dll and turn it into something else without having the original source code and the actual SynthEdit program.

Let me know how you make out.

TLDR - Having a SynthEdit dll loaded into your DAW is no different in practice from loading Diva into your dll. They are both 1 step loads whereas a Reaktor Ensemble is a 2 step load (Reaktor plus Ensemble)
Yes about c++, I did try and explain that way back...
lets also add, in the case of VSTs... you don't need the VST_SDK installed on your computer either.

Post

wagtunes wrote:
Using that same logic, any VST dll made with C++ means that I have C++ when I load a C++ created dll into my DAW. Except I don't have C++. I can't create my own C++ project. I can only use dlls that were created with C++.
How little you people understand things...

Anyway, im not into brickwall talk so i guess i better just stop here. If you really cannot comprehend that a SynthEdit VST DLL is simply your SynthEdit project wrapped in a DLL then im afraid there is nothing i can do. In my view it is clear, it is obvious, after all how could a SE plugin function without SE when SE is the very component the plugin consists of. But feel free to think what you will.

Post

ENV1 wrote: Mon May 06, 2019 7:33 am
wagtunes wrote: Using that same logic, any VST dll made with C++ means that I have C++ when I load a C++ created dll into my DAW. Except I don't have C++. I can't create my own C++ project. I can only use dlls that were created with C++.
How little you people understand things...
Anyway, im not into brickwall talk so i guess i better just stop here.
Yep. Discussing software development with non-developers is utterly pointless :shrug:

Either way, compulsory use of any kind of wrapper (be it Reaktor, VIP, Ableton Rack...) usually hinders my workflow and I'd like to avoid it whenever possible. It's not good to depend on 3rd party wrapper / host and it's not easy to port / share such project with everyone.
Blog ------------- YouTube channel
Tricky-Loops wrote: (...)someone like Armin van Buuren who claims to make a track in half an hour and all his songs sound somewhat boring(...)

Post

EvilDragon wrote: Sun May 05, 2019 5:12 pmThe connection to Pro-53 is Prophet-5 Rev 3 that was on the desk of the guy who worked on Super 8 when I was visiting NI offices some months ago. Same one that was used when Pro-53 was created. :P
Okay, but the whole synth still doesn't sound much like a Prophet-5.... :)

Does the filter sound like Prophet? I don't know, there are at least two different versions (SSM/Curtis).

Whatever they used, Super 8 sounds good to me. Bought it on Saturday.

Post

Well the oscilltors aren't based on the Prophet-5, but more akin to Juno/Alpha Juno. And as I said, it's a Rev 3, so Curtis filter.

Post

Sinisterbr wrote: Mon May 06, 2019 2:24 am
mholloway wrote: Sun May 05, 2019 10:43 pm
gentleclockdivider wrote: Sun May 05, 2019 2:09 pm Just noticed , no legato ..envelope always retriggers in mono mode
...that's a pitty
Yeah, this is the one big bummer about this otherwise great synth. I have zero idea how to "just go and change it in reaktor," so that's not a helpful response. I think Super-8 sounds fantastic, and I'm also one of those who greatly enjoys "straight forward" synths and don't need pretend-cutting-edge bells and whistles to sell me on something. TAL U-No-LX is one of my absolute favorite plugin synths of all time: it looks great, sounds great (the filter is a Juno dream, imho), and as "simple" as it (or a Juno 60) is, I'm still able to put it to effective use on a regular basis without getting tired of it. So in a similar, albeit deeper manner, Super-8 holds a lot of potential for me. The lack of Mono Legato is definitely a bummer thought, as I create a lot of bass patches that only 'work' in mono legato mode.
I suppose you also tried TAL-Mod.. God, what an amazing synth. It's got an almost perfect score considering sound quality/ GUI/ price for me.
Yes , I also own Talmod ..fantastic synth
Eyeball exchanging
Soul calibrating ..frequencies

Post

AnX wrote: Mon May 06, 2019 5:42 am
ENV1 wrote: Mon May 06, 2019 12:46 am
AnX wrote:
ENV1 wrote: How else could the plugin even function? How could it process sound and display an UI?
the same way any other vst does?
Is any other plugin made with SE?


if SE was embedded in its vst's, the file size would be huge, its not. :shrug:
No , because only the used modules are embedded

Otoh in reaktor the only modules that are embedded in the reaktor dll. are all the primary modules and the core modules .
For example , if you create a synth in reaktor with only the core macros osc's filters and envelopes ( which are stored somewhere on your hard drive )+ some primary modules for gui purposes
If you then delete all the core macro's from your hard disk , the ensemble will still load because the macros were made out of the core modules ( which are embedded in the dll ) and these were never ( can not be ) deleted .
I guess it's the same for synthedit
Eyeball exchanging
Soul calibrating ..frequencies

Post

A C++ coded (usual standard for high performance requiring realtime dsp) plugin and the used SDK sources will be translated to machine code / assembler by the compiler, and all required data like images, config files will be linked into one big file (or loaded from an app data dir, then the code needs a loader logic). A synthedit or a reaktor based synth basically is like a complex configuration file for the already existing synth "synthedit" or "reaktor". Maybe you can also extend those with custom c++ code, but normally you will get the sound, performance and capabilities that synthedit or reaktor can provide. That said reaktor provides an heavy abstraction of even the very basic maths elements of a synth, so it is not that easy like I described. So I assume you not only can drag the "analog filter" module into your reaktor project, but also build your very own filter algorithm using Reaktor's raw maths elements. In the end, such heavy abstraction will cost a lot of performance. That's why you can play 56000 notes at once with the great old pro 53, and only 64 with this one, until cpu 100% usage is reached. :hihi:

Post

I'm not familiar enough with Reaktor to do this discussion on a technical level, but with regard to directly opening a reactor ensemble, maybe we need to make a distinction between the technical level and the experience by the user.

Embedding is not needed for me, as long as one (double)click opens the synth in Reaktor.
When you open a Word document, one (double)click opens the application and then opens that document in the application. The same behavior would be quite sufficient for me. One (double)click on an (object referencing an) ensemble in your DAW opens Reaktor and then opens this synth in Reaktor. Same behaviour with drag and drop.

Surely, NI should be able to make this happen.

Post Reply

Return to “Instruments”