Let's talk reaktor 6.4

[WasteLand]

double post

[WasteLand]

looks like the site is closed again....

but have the free pack....

[Deep Purple]

The plot thickens...

[pdxindy]

Well the standard osc in the free package looks like bento osc
Hmm funny , the site isn't accesable anymore , while 5 min. ago it was

Yup... I was able to read it, then it disappeared... very impressive though! Looks like it has polyphony options too

[bob swans]

looks like the site is closed again....

but have the free pack....

I guess that's me out if the beta group then

[WasteLand]

it's a strange strange world (blue velvet)

[ccooll]

Nope. He has the usual Reaktor version (well, also betas I would suppose). Blocks need to be encoded and entered in NI's product database, so that it can be authorized and then referenced in Racks. Pretty much the same thing as with Kontakt.

I've been thinking this over, and I find it extremely hard to believe.
How could an iterative development process work if every time there was a significant change to your code, you needed to register the new version with Native Instruments.
Not to mention the crazy number of different IDs that would have to be registered for every single Block developed by every single developer. Nah.
Sounds to me like you are just guessing and pretending to be an authority!

Developing Blocks for Racks is pretty much the same as with regular Blocks, plus some additions on how the inputs/outputs should be handled UI-wise, etc.

If registration of different versions of the same block is required - as it would be if the developer were using a standard version of Reaktor, then the Process would be very different to that of regular Blocks - very different indeed!

[I'm Ant]

I really like how I can now use Reaktor like Softube modular. Thanks NI

[Echoes in the Attic]

Why does it not fit automatically to the visible blocks in reaktor.

It auto-fits in komplete kontrol, but it leaves an extra bunch of room at the bottom. Why.

[thelizard]

Nope. He has the usual Reaktor version (well, also betas I would suppose). Blocks need to be encoded and entered in NI's product database, so that it can be authorized and then referenced in Racks. Pretty much the same thing as with Kontakt.

I've been thinking this over, and I find it extremely hard to believe.
How could an iterative development process work if every time there was a significant change to your code, you needed to register the new version with Native Instruments.
Not to mention the crazy number of different IDs that would have to be registered for every single Block developed by every single developer. Nah.
Sounds to me like you are just guessing and pretending to be an authority!

I would say that EvilDragon is not guessing : https://blog.native-instruments.com/mar ... -and-more/

That was pretty much the process in my experience. They didn't do the encoding until late in the process after a lot of QA had taken place. It was very easy to work with them!

[ccooll]

That was pretty much the process in my experience. They didn't do the encoding until late in the process after a lot of QA had taken place. It was very easy to work with them!

So how did you test your blocks and racks during development if they weren't encoded until late in the process?

[EvilDragon]

How could an iterative development process work if every time there was a significant change to your code, you needed to register the new version with Native Instruments.

No, you wouldn't. You register your product, all its version updates can be under that product's "docket". Pretty much exactly the same as it works for Kontakt Player. Updates to a library don't have to be reencoded.

If registration of different versions of the same block is required

It's not. This is where you're wrong/missing the point.

So how did you test your blocks and racks during development if they weren't encoded until late in the process?

You can test your Blocks normally in ensemble mode as before. You do racks after encoding the blocks, IIRC.

[WasteLand]

and

https://www.toyboxaudio.com/

is open again. together with blocks prime, base, unfiltered audio 18 modules and the free pack of 44 modules of toybox, you have, i guess 100 modules...

[aMUSEd]

and

https://www.toyboxaudio.com/

is open again. together with blocks prime, base, unfiltered audio 18 modules and the free pack of 44 modules of toybox, you have, i guess 100 modules...

Wondering who made these?

Some of the endorsements are a bit dodgy - ' Changed how I produce' - right, 6.3 has been out how long exactly?

[WasteLand]

Wondering who made these?

Some of the endorsements are a bit dodgy - ' Changed how I produce' - right, 6.3 has been out how long exactly?

yes also wondering, i think NI.., not sure.. and the endorsements are very, very strange.. but there can be beta testers... but still, endorsements are only acceptible, i think, once a product is launched, and after some time. i noticed it too, but was really busy to get the free pack, yesterday, and today, looking at the other packs.

other company's do (almost) the same, by the way, but irrelevant for this particular case..