Reason 13 Announced- Sequencer updated!

[Jac459]

But I can't agree on the modularity....Actually bitwig is far (but far far far) more modular than reason.

Yep, you still don't get it. Most people don't seem to

So, try this in Bitwig: break a mixer channel out of the main mixer and use it inside a patch of whatever you want to do. Here's a more crazy one: try to use a mixer channel as an insert inside another mixer channel. That last one is not that useful (however, it might be), but it illustrates the real modular nature of Reason. Or have signals somewhere in your project routed to hardware outputs (or inputs for that matter) without having them to go through the main mixer.

This made it possible for me to build a monitoring management console INSIDE Reason, while every other DAW needs external hardware for that kind of routing. My solution even takes care of different correction curves for each monitor set and headphones that I have connected, something even the hardware monitor stations cannot do (unless you buy one with embedded DSP, but then you need to sell a kidney).

These things are not possible in Bitwig afaik (never seen any example or video to the contrary). And they are not possible in any other DAW I know of besides Reason.

Well you didn't answer on polyphonic CV which I believe is much more important need for modularity . No clue ? Or you don't get the interest ? I can point you to tutorial videos if you want.

So, try this in Bitwig: break a mixer channel out of the main mixer and use it inside a patch of whatever you want to do. Here's a more crazy one: try to use a mixer channel as an insert inside another mixer channel. That last one is not that useful (however, it might be), but it illustrates the real modular nature of Reason. Or have signals somewhere in your project routed to hardware outputs (or inputs for that matter) without having them to go through the main mixer.

That is a very basic scenario... You just load an FX Layer, put whatever software EQ, Compressor you want, then load an HW FX (input and output available) or an HW Clock, or an HW CV for that matter, and you save the preset after. No big deal. You can also route through an audio receiver from anywhere if you want.

This made it possible for me to build a monitoring management console INSIDE Reason, while every other DAW needs external hardware for that kind of routing. My solution even takes care of different correction curves for each monitor set and headphones that I have connected, something even the hardware monitor stations cannot do (unless you buy one with embedded DSP, but then you need to sell a kidney).

That is also a classic, I used to have "morphit vet" used as an headphone corrector on a specific channel that I was using to output sound in a different channel that the master I was using to bounce the full project.

So, what about polyphonic modulations ?
I think it is much more important because if I want to create a synth based on many synths, I need it to be more than monophonic isn't it ?

And then after we can talk about audio rate modulations ?
https://www.soundonsound.com/techniques ... audio-rate

[crimsonwarlock]

Well you didn't answer on polyphonic CV which I believe is much more important need for modularity . No clue ? Or you don't get the interest ? I can point you to tutorial videos if you want.

Don't try to be a smart ass. I didn't react to every little thing you think is important. Just pointing out some things that are impossible in Bitwig should make things obvious.

Polyphonic CV is perfectly possible in Reason, at least for the examples you gave. Yes, it is more complex to setup, but no it is not impossible.

So, try this in Bitwig: break a mixer channel out of the main mixer and use it inside a patch of whatever you want to do. Here's a more crazy one: try to use a mixer channel as an insert inside another mixer channel. That last one is not that useful (however, it might be), but it illustrates the real modular nature of Reason. Or have signals somewhere in your project routed to hardware outputs (or inputs for that matter) without having them to go through the main mixer.

That is a very basic scenario... You just load an FX Layer, put whatever software EQ, Compressor you want, then load an HW FX (input and output available) or an HW Clock, or an HW CV for that matter, and you save the preset after. No big deal. You can also route through an audio receiver from anywhere if you want.

So the answer is that you can't do that in Bitwig. Setting up some example scenario where you accomplish something that doesn't need that functionality is definitely not the same.

The question was simple: Can you do this in Bitwig, YES or NO?

mixer-in-mixer.png

That is also a classic, I used to have "morphit vet" used as an headphone corrector on a specific channel that I was using to output sound in a different channel that the master I was using to bounce the full project.

So again, the answer is no. You cannot connect to outputs outside of the mixer in Bitwig.

You still trying to make this into a pissing contest. It is NOT about one or the other being better, it is about the statement that Bitwig is more modular than Reason. It is not, and I tried to illustrate that with a few examples. Workarounds don't count. In Biwig, the mixer channels are NOT modular components, and the hardware inputs and outpus are also NOT modular components. This has nothing to do with Reason being better, or smarter, or whatever. It has to do with Reason emulating a hardware environment, and big surprise, in a fully hardware based studio, EVERYTHING including the hardware console is a modular component in that studio. Other DAWs, including Bitwig, are simply not designed from that perspective.

Here's one last example: in a hardware studio you can simply jack a microphone into the mic-input of a vocoder. As simple as that. Reason is the only DAW afaik where you can connect an input o your audio device directly into the mic-input of a vocoder RE or even VST, in the exact same simple way. And don't tell me this is also easy in Bitwig by using this and connecting it to that because the argument is that in Reason you don't need to connect or use anything else but that one virtual cable that connects your microphone directly to the vocoder.

If this doesn't make it clear, I don't know what will

[carrieres]

What a boring pissing contest
The only thing we understood is that both of you pee on his shoes

[Jac459]

What a boring pissing contest
The only thing we understood is that both of you pee on his shoes

How so that where this smell is coming from ?

[crimsonwarlock]

What a boring pissing contest

I never said mine's bigger than his

[Jac459]

...
Here's one last example: in a hardware studio you can simply jack a microphone into the mic-input of a vocoder. As simple as that. Reason is the only DAW afaik where you can connect an input o your audio device directly into the mic-input of a vocoder RE or even VST, in the exact same simple way. And don't tell me this is also easy in Bitwig by using this and connecting it to that because the argument is that in Reason you don't need to connect or use anything else but that one virtual cable that connects your microphone directly to the vocoder.

If this doesn't make it clear, I don't know what will

Well if your point was to say that in Bitwig you don't have cute green and blue cables, then you are 100% right...
As per connecting directly from outside to anywhere in the chain, yes, it is easy in Bitwig (and I guess all good DAWs).

For polyphonic or audio-rate modulation in Reason, I would have been happy to be proven wrong on the fact that it is not possible. But I guess you won't go there...

Anyway, you are right to say that it turned to be a pissing contest and I certainly take my part on the blame for that. At the beginning, I was more curious to learn things I don't know about Reason, but it seems I started to discuss with someone who know even less about Bitwig. But It is absolutely your right, after all, it is a Reason thread.

[Jac459]

What a boring pissing contest

I never said mine's bigger than his

No but mine is more modular than yours (just kidding ).

[Jac459]

What a boring pissing contest
The only thing we understood is that both of you pee on his shoes

I agree that the tone of this discussion may be boring to read, but in the end, sharing the "how-to" of various technics across DAWs is quite interesting.... At least to me...

[carrieres]

It was very interesting but after a while it became ... a childish contest to me

[crimsonwarlock]

As per connecting directly from outside to anywhere in the chain, yes, it is easy in Bitwig (and I guess all good DAWs).

If that is true, show me how you connect an input from your audio-interface DIRECTLY to the input of a VST-plugin. No workarounds or additional tools allowed, so not using the grid (because I can also load VCV-rack into Reason and do all kind of stuff). And not going through mixer-channel configurations (that's how most DAWs route their hardware ins/outs).

I dare you

[crimsonwarlock]

It was very interesting but after a while it became ... a childish contest to me

I actually don't see why asking someone how he/she thinks that things are possible or not, is somehow a 'childish contest'.

And if you don't like it, you can just block me

[Jac459]

As per connecting directly from outside to anywhere in the chain, yes, it is easy in Bitwig (and I guess all good DAWs).

If that is true, show me how you connect an input from your audio-interface DIRECTLY to the input of a VST-plugin. No workarounds or additional tools allowed, so not using the grid (because I can also load VCV-rack into Reason and do all kind of stuff). And not going through mixer-channel configurations (that's how most DAWs route their hardware ins/outs).

I dare you

Ok, but first you show me polyphonic and audio-rate modulation .
After I show you the direct access to your audio interface. Pinky promise.

[Jac459]

It was very interesting but after a while it became ... a childish contest to me

After I show you the direct access to your audio interface. Pinky promise.

Frankly, I have no idea what you are talking about .

[carrieres]

It was very interesting but after a while it became ... a childish contest to me

I actually don't see why asking someone how he/she thinks that things are possible or not, is somehow a 'childish contest'.

And if you don't like it, you can just block me

You still trying to make this into a pissing contest

A pissing contest is a childish contest in my book

[liquidsound]

Please people, don’t interfere with this.
This is quite entertaining.