I am using ADAT in various ways, to connect to a Behringer X32 Rack, using a SM Pro Audio PR8 analog-to-digital converter and in various ways at work, you can get a good line-to-adat converter from 150€ on (SM Pro Audio Q-ADAT) or spend 4000€ for a multichannel mic preamp..  http://www.thomann.de/gb...

They're both just digital interfaces, ADAT has 8 channels and S/P DIF has 2 channels. So yes, you'd have an ADAT interface that converts from analog inputs to ADAT and if you connect them to your soundcard you'd get the analog inputs as inputs to your "ADAT" inputs in the driver on the computer. The...

I think it mainly sounds so "grainy" because of the input sound which has a pretty hard attack. Pull up the ER part of the reverb, increase the initial delay, maybe simply add a short echo before the reverb to enhance that effect.

Yaay, gate/note input ftw!

I don't exactly think you can compare listening on your iPod with listening to a full scale PA on a concert, even if they'd just put in the same CD ^^

I rather think its becoming more relevant again. So yeah, its pretty much just you ^^

Most of Dubstep and DnB users use FM-8 for make DROP section. in theory Frequency Modulation is SINE, when John M Chowning who Found in 1967. that's the theory of DX-7. But after that it's modified with time. it's comes with time and new genres.  FM-8 is an example for that. the most wanted FM vst ...

What exactly would you do with different waveforms? I find it hard enough to think about what I'm doing in a FM synth with only sines :) And from what I get theres already loads of options to create waves with sines, to me its kind of the point of an FM synth.. Just like an additive synth with other...

Pretty much. I do wonder though, how much of a real world problem this is. I mean, it's so easy as a software developer to get caught up in creating the most theoretically correct system when in fact it only matters for 0.001% of cases ;) I think that's most likely why Reason currently 'resolves' c...

D4 does have a delay in my example, though I've written it wrongly. It should be: A1: { adds: 0, inputs: {}, accumulated plugin delay: 0 } A2: { adds: 0, inputs: {}, accumulated plugin delay: 0 } C3: { adds: 0, inputs: { A1 (+20 ADC), D5 }, accumulated plugin delay: 20 } D4: { adds: 15, inputs: { C...

My bad you did mention the usability, and from a usability perspective I think it can be tricky. Ideally it would be great if it could be automatic, yet at the same time there is a good reason to want control over the behaviour. This could be discussed later as it's a tricky subject that requires a...

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 ...

If you installed some VST instrument that supports being a Reason slave that instrument might have changed / downgraded your ReWire binaries and now Reason wants to install its own binaries again.

avasopht wrote:And what do you find reason doing in that case?

It has the delays where one would expect them according to the signal flow.

Have you examined how reason currently deals with this scenario? When you look into this deeply you'll see that all that is left is calculating delay compensation through a somewhat straight forward algorithm (especially when you consider how reason currently handles this). It's something I pushed ...

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,...

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. Why would that have to be flawed? And you can't solve these situations, the delay will be somewhere, how does the user know w...

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 i...

Theres always possible situations where the latency simply can NOT be compensated, as my little drawing shows, you don't even need a feedback loop for that. You'd theoretically have to bounce the whole signal flow an infinite amount of times to compensate that, so mathematically its possible, techni...

But they already deal with feedback loops with somewhat predictable behaviour. Even without RE's Reason has always had to deal with those and I can't imagine it being a bigger problem with ADC than without because if you get one you know why, you have a feedback loop. That is though, why I said the...

At least there *is* a tooltip with the current value when you hover over the fader, pan knob or width knob.

I'm one of those (maybe in a small minority?) who would be perfectly happy if they added ADC only to parallel channels since that's the only time it affects my work flow. All channels which are parallel can be easily identified by the software, and all REs are required to report their latency. Goin...

The link I always used to enter the forums still works
https://www.propellerheads.se/forum/sea ... ?do=getnew

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 a...

The REs do have to report their latency so theres no need to measure anything (the VMG can't access this info though). Still, if Reason was to decide what to do in unresolvable situations that would be a mess, how am I as a user supposed to know what Reason decided it should do? I don't think its qu...