Reason 13 Announced- Sequencer updated!

[spacepluk]

Mistery solved then

[gentleclockdivider]

Weird issues still keep coming , don't know if these are resolved in later versions .
Enable masterbuss compressor , with a healthy amount of compression , fastest attack and release ,squashing transients and
sidechain turned off .
Listen to the result .
Drumbeat , verry heavy compreesion

Now route the Monitor out ( without any effect processing ) to the sidechain input (make sure the monitor out has the exact same volume level as the master out ) , the result should be the same as the first case but there is a clear difference in compression being applied , transients-first milleseconds are led through before the compressor kicks in .

I suspect this is because there is no lookahead , so the compressor's output is missing the first 10 milliseconds when it's own output signal as side chain .
I wonder ..did these creep in since reason 10 or have they been there all the time ? ( I stopped using reason sine version 5.0)

[gentleclockdivider]

Disabling this setting more or less solves the issue at the cost of plugin performance
It's still weird why this affects realtime performance without plugins
So with this feature enabled , ctrl room out is dodged as a side chain signal because it adds latency to the sidechain signal and thus overall response of the compressor

[Pepin]

If Reason considers your routing to be a potential feedback loop, it will introduce a 1 batch delay.
By unchecking that box, you're telling Reason to use a 64 sample batch size instead of your audio card's buffer size. That was the behavior up until Reason 10 iirc, which added this setting.

Edit: Details here
https://help.reasonstudios.com/hc/en-us ... -what-s-up

[spacepluk]

Also the Delay Compensation section in the manual is very good.

I think Reason does a pretty good job at this. I don’t know if things have improved recently but I remember most DAWs having issues with latency compensation in sidechains.

[gentleclockdivider]

Anyone else who has Gforce oddity 3 , It doesn't seem to respond to automation at all
Clicking the automate + parameter does nothing , tweaking the sliding neither .
Strange becasue gforce SEM woks great

[gentleclockdivider]

If Reason considers your routing to be a potential feedback loop, it will introduce a 1 batch delay.
By unchecking that box, you're telling Reason to use a 64 sample batch size instead of your audio card's buffer size. That was the behavior up until Reason 10 iirc, which added this setting.

Edit: Details here
https://help.reasonstudios.com/hc/en-us ... -what-s-up

Yep , routing the ctrl room out back into sidechain could be considered a feedback loop , but it's the only way to highpass filter the mainout and use it as sidechain .
So we have to delve in the settings to either fix this added delay value .
Props could have hardcoded a highpass filter in the buscomp instead .

[spacepluk]

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

[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

[spacepluk]

I'm pretty sure you can set up that routing in the inserts.

[spacepluk]

Maybe something like this

Screenshot 2024-06-01 at 14.17.57.png

[spacepluk]

I've never used it like this though, I always use a different signal for the sidechain.

[gentleclockdivider]

Wel I am still on reaon 10 , so I don't have the masterbusscomp as a separate device

[jens]

in fact, the only reason i haven't explicitly said so before this was due to my assuming that it would be in this version. it just seems so obvious. and yet...

Yes, this baffles me for years - it's just such a basic basic crucial crucial feature...

Not sure what you guys are referring to…?

To MIDI loop-recording as has been available for Audio for years and as is available in just about any other DAW

MIDI Loop recording was always available since Reason 1 - built in instruments and now VST’s
Are you referring to external hardware synths?
Shouldn’t be any different…

No, I was certainly not referring to external hardware-synths. I was referring to MIDI-recording. What has hardware to do with this? And why do you post a link to a 30+minute youtube-video?

[Jac459]

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