I'm not a Reactor user, but the picture is puzzling me...
Are you using the G2 Demo as a VST in Reactor, or, are there just some windows layered, or, is it one HOAX using PhotoShop, or am I just a nitwit?

Where are the module folders? How about those cables between the G2 mixers and the scope???

The cables beetween both are fake, but only the cables...
(i just used them to show how the signal flows)

Expect to see more complex wave images than this, in future posts, Reaktor has several limitations (graphical object misalignment, no patch cables in the front panel, limited character font sizes, 4x4 grid, etc...), but aside from these, fortunately, it has a very powerful oscilloscope, with a very high resolution with 384khz bandwidth.
(It was an important decision factor for evaluating whether it was capable to analyse G2 waves or not... [after all, i need a "Plan B" for the possibility of not having access to the G2 dsp source code])

Great idea!!!
(I was originally considering doing only the (1/2)/(3/4) approach... but when passing through the in/out/bus/fx modules i´ll put some steroids in their first version, and will standardize with 16 channels (1/2|3/4|5/6|7/8|9/10|11/12|13/14|15/16) [that is the same number of in´s and out´s in Reaktor].

Neon Sega wrote:

New 3 modules?

First, i´m prioritizing the original modules, with a few improvements in them.

But with some new ones appearing in between, like the half module that is proving to be very useful here to, shrink some original modules that have very few controls inside them.

Uh oh.... tough question...
(This is such a long list, that probably, at some point, it may be moved to a topic of it´s own, and some new aspects may also appear during the porting)

It´s also of such importance that i´ll tag all related messages with

"rg2comp"

on the subject.
(Reaktor G2 Comparison)

Let me first start with a definition of atomic fail:
"It´s some kind of problem at such a small/deep level, that, on the "user side" of the problem, you can´t obtain a solution, to get the job done, using current technology."
(I´ll also separate every criterion in single messages.)

It´s normal, having to deal with lot´s of wires/modules inside both Reaktor and G2.

Every macro (Reaktor) that is opened, also shows another layer of modules and wires.

The problem in Reaktor is:
You have N layers of modules and wires (and believe me, that N can be very large) but...
in the last... topmost layer... Doh!!!
No wires????

How people are supposed to learn some modular architecture easily, if... at the top layer, which is the most abstract one, there are no wires to patch up things?
(That´s what i call "uniform behavior", having modules and wires in *all* layers.)

Please don´t use "Herw Modular" as a counter argument for this.
(He did a fantastic job [very complex and laborious] trying to fix this flaw in Reaktor, but that´s what it is, a flaw fix, which can be surely solved in some better way, if... in next versions, is implemented *in* the product, and not counting for some user to solve this one, which is clearly NI´s responsibility.)

I imagine something like creating IN and OUT ports that appear like rounded and square conectors in the topmost layer, and adding an extra wire manager, which would allow using or not, wires in the front panel.

On the other hand, G2 has only one layer (no macros), with wires, which means it deals only with the topmost abstraction level, but when people start to understand high level modules, there is no option to access deeper modules. (Which is a clear situation that shows that porting G2->Reaktor is the only direction possible. [One is recursive, the other is not])

Give me a break!
(everybody knows that the cpu has more bitwise operations than those...[since the 80486])

What about ROL, ROR, SAL, SAR, XCHG, BSWAP?
(For a platform that has the shift operations implemented already, it´s just one more hour work to implement these...[and these are as important as shift operations])

(not to mention MMX, and SIMD instructions, to perform operations in paralel, to speed up things...)

During this period you can expect mostly:
-Images of some graphical details of the interface
-WAV´s
-Communnication logs from other channels
-Images of internal structures
-Videos of the interface (rare... only for some special cases)
-Other related videos/images/graphics

Currently, i could supply some WAV´s for the clock generator, but honestly, those are not much interesting.

(probably the WAV´s will be posted for the white noise case, but not in sequential order because i am researching some other modules in paralel)

(The implementation of the Voss-McCartney algorithm may take some time...)

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum

Please support our site. If you click through and buy from our affiliate partners, we earn a small commission.