Reason 11.2 Out!

[antic604]

Sorry, but the request is valid: using Reason as a single rack (in the same way as standalone) would save resources. You add one instance of Reason as VST3 to your song, add RE‘s and devices as needed and play everything isolated by different source tracks from your host with different MIDI channels.

Now it is a bullshit solution to use Reason Rack as a Container for each track. If you use 12 Reason devices on 12 tracks on your host, then it means 12 independent instances of Reason in your RAM.

Nope. In Cubase, you're saving RAM (and propably some CPU) by for example loading single instance of Falcon and then sending data from separate tracks on separate MIDI channels to separate patches within that single instance of Falcon (or Halion, or Kontakt, etc.).

Even if Reason Rack VST supported separate MIDI channel inputs, you still wouldn't be able use e.g. 5 channels to send their data to 1 instance of Europa (or Grain or Parsec, etc.) because they're NOT multitimbral and none of Reason or RE synths are. Which means you'd still need to load 5 instances of Europa into the Reason Rack VST, which would still use 5x RAM and 5x CPU. As such it would be no different from just loading 5x Reason Rack VST each with single Europa. The Reason Rack VST by itself barely uses CPU and RAM, because it's just an empty shell. It's what you put into it that makes the difference

And please don't be disrespectful.

[antic604]

It absolutely makes sense, a key feature that has set Reason apart since the beginning is CV modulation between devices. You can’t do that between VST instances.

Ok, this I can agree with.

[Crossinger]

Now it is a bullshit solution to use Reason Rack as a Container for each track. If you use 12 Reason devices on 12 tracks on your host, then it means 12 independent instances of Reason in your RAM.

So, you´re writing tracks with only 1 Vst instrument?

Err, no. You also have only one rack in Reason to host all your devices. Why not the same with the VST3 rack? It could host all REs for your song and you use them by assigning different MIDI channels. A single Rack could host Kong for Drums, Monotone for the Bassline, Radical Piano for the keys, etc. and each of them addressed by individual MIDI channels.

[Crossinger]

The Reason Rack VST by itself barely uses CPU and RAM, because it's just an empty shell. It's what you put into it that makes the difference

And please don't be disrespectful.

I don‘t believe this and never will. For plain technical reasons each instance must cause a little overhead by design. And it is by no means an empty shell. I rather suspect it‘s a more or less full instance of Reason running in memory. It must work this way, otherwise you wouldn‘t have the possibilities of Reason (cabeling etc.) at hand. So in the end it‘s like having 10x Reason open in the background. As far as I know, the full executable of Reason is copied into the VST folders.

Disrespectful? To whom? Maybe the Props, but they have a thick skin as you can observe from years of fruitless feature requests.

[Crumbfort]

For those being interested in this:

In Reaper it works both... a VSTi after Reason receives midi notes as well as Midi CC!!

Ah, really? I haven't been able to get MIDI CC out to work in Reaper so far, only Note/Gate data.

Perhaps you have to change the midi cc number...
By default it is set to CC 0 ... with this setting it didn´t worked for me neither

I set it like in the image made a midi learn in Serum and it worked immediately:
Midi.jpg

Huh, yeah I've got it all hooked up properly but no MIDI CC data is coming out of the rack plugin. Hrmm... Will investigate further.

[antic604]

I don‘t believe this and never will. For plain technical reasons each instance must cause a little overhead by design. And it is by no means an empty shell. I rather suspect it‘s a more or less full instance of Reason running in memory. It must work this way, otherwise you wouldn‘t have the possibilities of Reason (cabeling etc.) at hand. So in the end it‘s like having 10x Reason open in the background. As far as I know, the full executable of Reason is copied into the VST folders.

Disrespectful? To whom? Maybe the Props, but they have a thick skin as you can observe from years of fruitless feature requests.

It's not a matter of belief.

I just loaded 20x empty Reason Rack VSTs playing simple 1-bar clip each (all at once) and DSP use was at 3-4%. When I added Complex-1 with 1st patch (Animated Bass) to each of 20x instances and played that, the DSP use went up to 38-40%. So maybe it's not nothing (I said 'barely uses'), BUT it's definitely not full Reason running in the background 20x.

Regarding disrespectful I meant the " " which clearly was misplaced, as you conveniently changed the subject from Reason's & RE synths even being able to utilise multiple MIDI channels per instance to some made up stories about running full Reason in the beckground.

[aeox]

I want to share a comprehensive Reason feature request poll so that we can hone in on what features are most important. We need as many participants as possible for accuracy. Appreciate your time. https://forms.gle/4vAXcAR1FtCCG7gK8

[lotus2035]

Does this update make it possible to control each instrument in the rack separably via MIDI channels?
I've only recently started using Reason Intro in Cubase, I haven't a clue how to get it set up.

Why? Reason's instruments aren't multi-timbral anyway, so I can't see how would that matter? And usually you keep only one instrument (or their combination for multi-layering) in Reason Rack VST anyway. It's not ReWire anymore.

Just load separate instances of Reason Rack VST plugins on separate tracks.

Multi-timbral had nothing to do with my post.
I want the rack to function as a rack not as a container for single instruments, if single instruments were the focus why not just release all the contained plugins (including the combinator) as single VSTis, No need for rack at all.
But seeing as there is a Rack I would like it to function like the rack in Cubase.

I'm affraid you don't understand the difference. Cubase's rack holds instruments that are multi-timbral, i.e. they can at once play sounds with different patches, using midi from different midi channels. There are no such instruments in Reason's ecosystem, therefore it doesn't make sense to have input for multiple midi channels.

You mentioned multi-timbral twice now even though I told you I don't care about it.
I want a rack loaded with all my Reason instruments and effects in ONE WINDOW. I don't want a bunch of windows from multiple instrument tracks all over the place.
In this way the Reason Rack would be superior to the Cubase rack since it would contain all the interfaces and controls of many instruments in one window.
Workflow is very important to some and the less clicking on and off I need to do the better.
If the Reason Rack operated as I wished I would have it open on a separate monitor and leave it open.

[THE INTRANCER]

Until the Props address the Reason VST Rack (including that of the RE's within it) to be scalable, I ain't interested. The same could be said of Reason but then I have as much need for the full Reason program as much as having a cat, and I'm allergic to cats.. I've since moved over to Windows 10, and the thought to even install Reason at all, has only just occurred as I type this... Reason 7.01 and a stack of 14 RE's collecting dust still remain in never never land...

As for this algo rhythmic stuff... Well, it's nothing really new... I was using Algomusic way back on the Commodore Amiga 1200 back in mid 1990's. Sure the lack of a GUI and being text based is different but the principals are much the same.

AlgoMusic 2.4 (20.08.98): GIFTWARE

Ever been tired of looking into your soundmodule-directory and yawning
your head off because you've heard all your mods thousands of times? Well,
here is the ultimate solution!

AlgoMusic is quite a complex program that creates and plays a song
randomly out of a series of algorithms in a Techno/House manner. Just try
it, it sounds nice.

AlgoMusic works on every Amiga with at least AmigaOS 2.0 (V36) and about
512 K of free memory. MUI 3.x is required if you want to use the prefs
program.

Installation is performed via Commodore's/AT's Installer.



Elsewhere and more on topic ..

[Crossinger]

Regarding disrespectful I meant the " " which clearly was misplaced, as you conveniently changed the subject from Reason's & RE synths even being able to utilise multiple MIDI channels per instance to some made up stories about running full Reason in the beckground.

Ok, point taken. No more about this subject from my side.

[JoeLP]

Has anyone been able to route midi from one track to another in Logic so for example the notes generated by a Reason Scales and Chords trigger on one track will (a chord triggered by pressing one key) will be fully recorded on another?

Also, has anyone been able to automate the player and utility Midi FX inserts in Logic?

And finally, how do you record various patterns using the new BeatMap utility onto a midi track? How do you automate the X/Y Access?

Appreciate any help!

[JoeLP]

Has anyone been able to route midi from one track to another in Logic so for example the notes generated by a Reason Scales and Chords trigger on one track will (a chord triggered by pressing one key) will be fully recorded on another?

Also, has anyone been able to automate the player and utility Midi FX inserts in Logic?

And finally, how do you record various patterns using the new BeatMap utility onto a midi track? How do you automate the X/Y Access?

Appreciate any help!

[Anosou]

Has anyone been able to route midi from one track to another in Logic so for example the notes generated by a Reason Scales and Chords trigger on one track will (a chord triggered by pressing one key) will be fully recorded on another?

Also, has anyone been able to automate the player and utility Midi FX inserts in Logic?

And finally, how do you record various patterns using the new BeatMap utility onto a midi track? How do you automate the X/Y Access?

Appreciate any help!

These are more Logic questions than Reason questions, but I got the same one yesterday so I happen to have some info! Here's a YouTube tutorial on the (quite annoying) way to record the MIDI FX output in Logic:

The more commonly used way in Logic is a little plugin that "records" the MIDI fx output for you, and you can drag/drop it after that: http://www.audiocr.com/

Automation is completely handled by the host, so however you automate any other MIDI FX plugin in Logic is how you'd automate Reason Rack Plugin when used as a MIDI FX.

[Jace-BeOS]

I want to share a comprehensive Reason feature request poll so that we can hone in on what features are most important. We need as many participants as possible for accuracy. Appreciate your time. https://forms.gle/4vAXcAR1FtCCG7gK8

“Sign in to continue
To fill out this form, you must be signed in. Your identity will remain anonymous.”

Ha ha ha ha ha... NO.

[SynapT!c]

I want to share a comprehensive Reason feature request poll so that we can hone in on what features are most important. We need as many participants as possible for accuracy. Appreciate your time. https://forms.gle/4vAXcAR1FtCCG7gK8

“Sign in to continue
To fill out this form, you must be signed in. Your identity will remain anonymous.”

Ha ha ha ha ha... NO.

What the problem (besides not having a Google account at all)?