Reason 13 Announced- Sequencer updated!

[JamminFool]

well, it is a thread about the upcoming version (although it seems to have become more about Reason 10, lol).

[LaLivre]

delete

[Pepin]

You can also put the master bus compressor in the master inserts and add any filtering you need.

Not the same thing , then you're filtering the whole signal .
I am talking about filtering the global out and use this as signal to which the compressor reacts too , the compressor still compresses the whole signal including the low end , but the detector signal is devoid of the low end
That's how it's done 99% of the time , you eliminate the low end

This isn't what you were doing in your earlier post (ignoring the filtering for now). The "Control Room Out" is post-Master Bus Compressor, so hooking it to the sidechain input is not equivalent to enabling the master bus compressor with no sidechain. You're creating a feedback loop where the compressed signal is fed back into the sidechain input. At least that's my impression of what's happening.

You might be able to sidechain as you describe if you enable "Inserts Pre Compressor" on the main mixer and split the signal from within the master inserts. I've not tried it myself, so I don't know if that would introduce latency.

InsertsPreCompressor.png

[D-Fusion]

well, it is a thread about the upcoming version (although it seems to have become more about Reason 10, lol).

And they have Tweaked the cpu/audio engine since then so v10 might behave differently than V12-13.
There where some latency and sync problems that where introduced in their newer audio engine in V10 and 11 which is why they did some more changes in v12.

[jens]

Funny as in every DAW thread, you always find someone complaining about "this vital feature every other DAW has".
It is the same for Bitwig, live or S1 threads...

Yeah, for a DAW I would call being able to actually record vital indeed.

But it's okay - in Reason I got used to record instruments as audio instead of MIDI, since audio-recording works fine.

[gentleclockdivider]

You can also put the master bus compressor in the master inserts and add any filtering you need.

Not the same thing , then you're filtering the whole signal .
I am talking about filtering the global out and use this as signal to which the compressor reacts too , the compressor still compresses the whole signal including the low end , but the detector signal is devoid of the low end
That's how it's done 99% of the time , you eliminate the low end

This isn't what you were doing in your earlier post (ignoring the filtering for now). The "Control Room Out" is post-Master Bus Compressor, so hooking it to the sidechain input is not equivalent to enabling the master bus compressor with no sidechain. You're creating a feedback loop where the compressed signal is fed back into the sidechain input. At least that's my impression of what's happening.

You might be able to sidechain as you describe if you enable "Inserts Pre Compressor" on the main mixer and split the signal from within the master inserts. I've not tried it myself, so I don't know if that would introduce latency.
InsertsPreCompressor.png

Wel then even the props got it wrong , becasue this tutorials does exactly what I did .
Skip to 2 min.

[LaLivre]

Back to topic!

[Pepin]

Wel then even the props got it wrong , becasue this tutorials does exactly what I did .
Skip to 2 min.

If their goal was to match your diagram and avoid a feedback loop, then they indeed got it wrong. I googled the title of that video, and unsurprisingly this has been discussed before. So like I said, filter from the pre-compressor master inserts to avoid the feedback loop.

But as far as this thread goes, maybe hunting for issues in a 7 year old version of Reason isn't the most relevant.

[gentleclockdivider]

Apparently , reason only shows 270 parameters of a vst ( 9 groups of 30 )
Gforce oddity has >270 parameters of which the first ones are all xmod /xenv's (each parameter has a dedicated xmod-xenv and these count up quickly )
So most imporant parameters are not available

[gentleclockdivider]

But as far as this thread goes, maybe hunting for issues in a 7 year old version of Reason isn't the most relevant.

I am most def. not hunting for issues , I just encounter them

[JamminFool]

... a 7 year old version of Reason...

I am most def. not hunting for issues , I just encounter them

i think you missed the point.

[eerie_audio]

Funny as in every DAW thread, you always find someone complaining about "this vital feature every other DAW has".
It is the same for Bitwig, live or S1 threads...

So you think it's better to sweep the problems and issues under the rug and pretend they don't exist or won't happen again in version 13? It seems there is a pattern with Reason, and I would put money on it that you will see new bugs and old ones still remaining in 13. That's pretty vital information on a forum about a product that people are interesting in buying, don't you think? Should we all pretend nothing happened, is happening and continue on blindly?

Maybe the issue is that you can't handle criticism of a product you're a hardcore fanboy of? While veterans of the product clearly explain it's flaws with no action from development. Which sounds like something I would consider before investing $399 or a lifetime of subscription payments for.

[Pepin]

Apparently , reason only shows 270 parameters of a vst ( 9 groups of 30 )
Gforce oddity has >270 parameters of which the first ones are all xmod /xenv's (each parameter has a dedicated xmod-xenv and these count up quickly )
So most imporant parameters are not available

Another issue that’s been fixed…

[spacepluk]

Funny as in every DAW thread, you always find someone complaining about "this vital feature every other DAW has".
It is the same for Bitwig, live or S1 threads...

So you think it's better to sweep the problems and issues under the rug and pretend they don't exist or won't happen again in version 13? It seems there is a pattern with Reason, and I would put money on it that you will see new bugs and old ones still remaining in 13. That's pretty vital information on a forum about a product that people are interesting in buying, don't you think? Should we all pretend nothing happened, is happening and continue on blindly?

Maybe the issue is that you can't handle criticism of a product you're a hardcore fanboy of? While veterans of the product clearly explain it's flaws with no action from development. Which sounds like something I would consider before investing $399 or a lifetime of subscription payments for.

Apparently everybody is a hardcore fanboy. The truth is that many of these "issues" aren't actually issues and they should have been discussed in a separate thread, but I guess it's fun to bomb the release thread.

[eerie_audio]

Apparently everybody is a hardcore fanboy. The truth is that many of these "issues" aren't actually issues and they should have been discussed in a separate thread, but I guess it's fun to bomb the release thread.

Only the ones that complain about complaints, and use words such as "fun to bomb the release thread." Seems pretty obvious that something has struck a nerve in your non-hardcore fanboyism.

Reason's past, present and future history are all up for discussion don't you think? Oh wait...