There's more to it than that. Reason has a policy for deciding which device takes priority and is processed first. Have you identified what that policy is? (I have identified it). Secondly, how do you imagine the case of ADC would be complicated? Have you constructed any test models to see whether a...

I hear you on the smaller market and the complexity still of anyone's got a year of coding to spare, it could be a worthwhile project for the intrepid coder.

Yes like an RE building app for non coders.

Wait I've just realised what went wrong, probably because I wrote this on my phone the OP says "graphical rack extension", should have said, " graphical rack extension designer ".

They would still have to design the GUI using the SDK provided system.

Yes that's exactly what I meant.

And what do you find reason doing in that case?

Selig, you're probably misunderstanding what I'm saying. What I'm saying is absolutely possible, there's not one part that is an issue. An application as the editor that spits out SDK compatible code. The RE would not be editable. It would behave just like any other rack extension because all the Re...

PS, there most certainly is a next batch. You'll see this when you experiment. I'll upload a file later today for classification on what I mean as it's easy for miscommunication.

I saw flawed as it's possible (even likely) they're not expecting there's a 64 frame delay that is out of their control. In terms of how the delay will be compensated, in that case it won't. In terms of how the user knows where it is, it will be dealt with in the exact same way it currently is now,...

Please do not discuss the SDK on this forum. Developers are well aware they are under NDA and thus shouldn't be commenting in public. I won't lock this thread as it was started by a user based on a post from an other public source, but Devs - you should know better. Use the official RE Developers F...

There's a big difference between discussing and juvenile fighting.

I saw flawed as it's possible (even likely) they're not expecting there's a 64 frame delay that is out of their control. In terms of how the delay will be compensated, in that case it won't. In terms of how the user knows where it is, it will be dealt with in the exact same way it currently is now, ...

When people are saying they're doing lip service to reason they're forgetting many things. Maybe their homepage will target reason on the next reason upgrade. Maybe enough users have upgraded indicating there will be little need for reason to appear on the main page. Maybe discover will develop into...

Some people lack the vision to see how useful these mobile apps and discover can be. Sometimes I get ideas during the day and record beatbox renditions to later then into full tracks when I'm at my computer. Sometimes I'll use a mobile music app to sketch out an idea. Drop to Propellerhead allows me...

What I mean is, the Reaktor like editor would be a user application that spits out the ensemble as c++ code that is then compiled into a regular rack extension. Compared to the IDT, this allows the creation of custom DSP algorithms featuring per voice processing without the need to learn scripting o...

That's what I meant when I said, "it's possible that many people may be creating circular references in a flawed attempt at automating parameters."

I'd factored that in too.

Well I meant more in the sense of providing something like IDT. Available only to developers, spitting out C++ code based on your design which can then be compiled by the SDK. Possible for any developer willing to develop it, and like IDT you would probably want to take a share of the sales, or mayb...

But your diagram contains a feedback loop (or at least a circular reference, which is the real problem). You can't compensate for the delay, no, but in those cases you simply defer to the next batch according to the prioritisation process, which is currently device creation order in Reason. There is...

Wheres the actual need for a feedback loop though? :) Reminds me of this guy standing in the line in front of me in a music store.. He said he got a feedback when he pulled up the aux send on the channel where he put the return of his reverb and asked for a feedback destroyer for that ;) Well feedb...

Resolving it in some way isn't the big deal, the big deal is making transparent what actually happens because the "impossible" delays will crop up somewhere.  But they already deal with feedback loops with somewhat predictable behaviour. Even without RE's Reason has always had to deal with those an...

Reason currently has a policy on how it handles feedback loops by prioritising device processing. Calculating delay from that position iirc was a fairly straight forward algorithm. I would have to build a configuration generator to confirm the processing cost on larger setups and also to test the al...

NI libraries have always been stellar.

All I would say is that the lack of libraries on reason gives room for you forum users to chime in and make a little earner

As the title says, a graphical rack extension for the code averse.

Technically it's possible for any developer to create this technology. Uhe has something like this for their plugins.

Maybe they are going to announce something that sucks and it would have had the forum up in arms again and they decided to kick it just before the sh*tstorm. Actually I think maybe it will be really boring and they will just announce that Reason 8 share thingy that we already know about. The PUF wo...

As I see it, there are two different kinds of latency compensation situations: 1. General track timing related latency, e.g. vocals that are a bit off due to the large latency of processing like Neptune/Polar. In these cases, shifting the track by ear in the sequencer or with Regroove will do. 2. P...