Reason 12.2.4

[kmonkey]

I create ambient pads and drones all the time and have never heard of midi chase

Same here first time hearing for this. What is it relly?

update: ok there's a video - thanks

[kmonkey]

Can anyone explain what this does:

- Auto-scale implementation for VSTs in Reason standalone

I don't see any auto scale - everything is same since always. Not that I need it, everything works I am just curious about the feature.

[antic604]

Can anyone explain what this does:

- Auto-scale implementation for VSTs in Reason standalone

I don't see any auto scale - everything is same since always. Not that I need it, everything works I am just curious about the feature.

If you're running windows at scaling other than 100% (e.g.you have a small 4K screen, for example) then many plugins will automatically detect that and adjust, so that they aren't unusably small. But many - Waves, NI, Soundtoys, etc. - won't and there was no way to fix that previously in v12. Now there's a per-plugin setting in Manage Plugins section where you can force such plugins to scale.

BTW, that can also work against you, i.e. some plugins will scale by themselves but won't report it to the DAW, so they will be scaled "twice" making them too big and likely blurry. In such case you need to disable that option and let plugin handle it.

Those sorts of options have been present in many Windows versions of DAWs for years now - Live since 10, Bitwig since 2, Studio One since 4 or 4.5, Cubase since 11.5.

[kmonkey]

If you're running windows at scaling other than 100% (e.g.you have a small 4K screen, for example) then many plugins will automatically detect that and adjust, so that they aren't unusably small. But many - Waves, NI, Soundtoys, etc. - won't and there was no way to fix that previously in v12. Now there's a per-plugin setting in Manage Plugins section where you can force such plugins to scale.

BTW, that can also work against you, i.e. some plugins will scale by themselves but won't report it to the DAW, so they will be scaled "twice" making them too big and likely blurry. In such case you need to disable that option and let plugin handle it.

Those sorts of options have been present in many Windows versions of DAWs for years now - Live since 10, Bitwig since 2, Studio One since 4 or 4.5, Cubase since 11.5.

Thank you! I am at 100% so this does not affect me but thanks for the lengthy explanation.

[aMUSEd]

Ok so it's a pretty obscure feature - I never use piano roll so I guess that's why I've not used it

[xbitz]

If you're running windows at scaling other than 100% (e.g.you have a small 4K screen, for example) then many plugins will automatically detect that and adjust, so that they aren't unusably small. But many - Waves, NI, Soundtoys, etc. - won't and there was no way to fix that previously in v12. Now there's a per-plugin setting in Manage Plugins section where you can force such plugins to scale.

BTW, that can also work against you, i.e. some plugins will scale by themselves but won't report it to the DAW, so they will be scaled "twice" making them too big and likely blurry. In such case you need to disable that option and let plugin handle it.

Those sorts of options have been present in many Windows versions of DAWs for years now - Live since 10, Bitwig since 2, Studio One since 4 or 4.5, Cubase since 11.5.

Thank you! I am at 100% so this does not affect me but thanks for the lengthy explanation.

remark, Waves ones has been fixed from this point of it was the big news in v12 https://www.waves.com/v12

[antic604]

remark, Waves ones has been fixed from this point of it was the big news in v12 https://www.waves.com/v12

I wouldn't call it "fixed". AFAIK they did exactly what DAWs do - they stretch the GUI, but have not updated the original assets to be high-res, so it's OK size but blurry.

[xbitz]

^^^ that was one of the novelties of the current version https://www.waves.com/v13 it's ongoing or https://www.waves.com/support/waves-plu ... k-displays at least there is some progress here

btw. this part was annoying "Please note: The V13 update includes plugins only. It does not include Waves applications (eMotion LV1, SuperRack, StudioRack, SoundGrid Studio) which remain V12. However, V13 plugins are fully compatible with and will work in V12 applications." apps like StudioRack has to be updated manually not from the Waves Central from v11>12

[SLiC]

If you're running windows at scaling other than 100% (e.g.you have a small 4K screen, for example) then many plugins will automatically detect that and adjust, so that they aren't unusably small. But many - Waves, NI, Soundtoys, etc. - won't and there was no way to fix that previously in v12. Now there's a per-plugin setting in Manage Plugins section where you can force such plugins to scale.

BTW, that can also work against you, i.e. some plugins will scale by themselves but won't report it to the DAW, so they will be scaled "twice" making them too big and likely blurry. In such case you need to disable that option and let plugin handle it.

Those sorts of options have been present in many Windows versions of DAWs for years now - Live since 10, Bitwig since 2, Studio One since 4 or 4.5, Cubase since 11.5.

Thank you! I am at 100% so this does not affect me but thanks for the lengthy explanation.

remark, Waves ones has been fixed from this point of it was the big news in v12 https://www.waves.com/v12

Funny thing is the cost to upgrade my older waves plugins is more than I paid for them in the first place!

[xbitz]

^^^ I was also super happy but DAWs (Bitwig) wasn't able to resize plugins that are opened by Wave apps (from StudioRack) so ... meh

[antic604]

I genuinely think to just remove all Waves stuff from my computer.

I rarely ever use them and it's a huge hassle - waveshells are messy as f**k, there are multiple versions of every plugin (mono, stereo, mono/stereo, 5.1, light/live, etc), the waves central needs to be updated almost every time I run it (and it's few hundred MBs for some reason)...

[xbitz]

^^^ softsynths love OneKnob Phatter

16:09 > you can drop the rest btw. Bitwig can see the individual plugins (with 'waves' in the search field) but back to Reason ...

[fudgewastaken]

Regarding midi chase:
It's most annoying when you have evolving pads over the course of several minutes and a composition on top, which you're trying to balance against the pads. Simple automations become huge chores because you always have to play your midi from the beginning for it to play.
What I do now is, I instantly bounce my pad into audio. But then I'm somewhat restricted. So whenever I want to make slight changes to the sound of the pad, I have to go back to the midi, make the changes, and re-bounce it. In almost every project I do this with several instruments, multiple times. It's just terrible for workflow. I have yet to encounter a DAW other than Reason, that doesn't have midi chase. I'm actually looking to get Studio One just because of that (and a few other things like VST3 support to be fair)

[Smasha]

Good news ,this update has solved the Sampletank 4 issue where if loading an instrument in Sampletank 4 caused icons on the Reason transport bar and elsewhere to disappear.

TY