Reason 11 announced!!!

[reggie1979]

Reggie, I've learned long ago that reasonable people, of which is a silent majority, generally can sniff out the asshole in the room and tend to keep their discovery to themselves. So stand by your convictions and opinions, and let those assholes stink as much as they like they aren't fooling anyone.

Fortunately there's not many around here, the air is still fairly fresh.

Thanks, I'm just off of my game today. Now, back to Reason 11 bashing

[EnochLight]

Which can be done with rewire too , everything can be controlled over midi by the master , and renoise made it superconvenient by just magically exposing all the midi cc's for the selected instrument .
Audio in , ok that's a vst rack advantage .
Sure you get 16 audio tracks in rack vst , but only 1 midi channel ... so ONE rack instance will never replace rewire , you will need to load muliple instances

It's clearly boiling down to personal preference. You seem to prefer ReWire, so I can understand how its deprecation must be disappointing.

For me, I've always found it annoying to work with: running 2 DAW at the same time, having to maintain 2 different files between sessions, horrible CPU consumption (though I seriously don't know if running separate Reason Plugins will make a difference), and no ability to run audio through Reason's myriad of effects processing. For me, it seems ReWire is a woefully outdated approach.

Taking into consideration Propellerhead/Reason Studios chose to release Reason as a VST plugin instead of update ReWire (and try to convince all of the DAW makers to also adopt a new ReWire codec/SDK), clearly they felt more people would prefer what we got. The have pretty accurate numbers of just how many people actually use ReWire. Apparently it was low enough to justify trimming the fat.

[gentleclockdivider]

A little question about Reason Rack plugin: how many MIDI ports to rack devices does VST3 plugin support? With ReWire I was able to control every single rack device with a dedicated MIDI virtual port from ReWire master, so it would be useful to have same flexibility from the new VST3 plugin.

VST3 like VST2 supports different MIDI ins and outs, so, with so many instruments in the rack, it surely makes sense.

No it doesn't ( the rack vst ) , some people here are just hypothesising
From cdm article

https://cdm.link/2019/08/reason-11-new-plugin/

quote
Reason Studios also provide some answers on other features:

-You can route audio input into effects, sidechains, splitters, etc.
-There’s no sampling support in Reason Rack Plugin, only in Reason itself.
-Reason Rack Plugin receives both host automation and one channel of MIDI input
-Yes, you can have multiple instances of Reason Rack Plugin. (That means if you want different channels controlling different instruments, you’ll just add more instances in the host.)
-There’s no MIDI output from MIDI generating devices like the Matrix and MIDI effects in this version. (You can still use those to automate internal Reason instruments and effects, though, inside Reason Rack Plugin).

end quote

[Aloysius]

Reaperson

[ShawnG]

A little question about Reason Rack plugin: how many MIDI ports to rack devices does VST3 plugin support? With ReWire I was able to control every single rack device with a dedicated MIDI virtual port from ReWire master, so it would be useful to have same flexibility from the new VST3 plugin.

Thats what I am trying to point out why rewire is superior , rack vst has only 1 midi channel ( not a bus )
So if you're not sequencing fron the internal rack sequencers you're forced to load new rack vst's instances

I don’t see the horror in loading additional rack instances, much less compared to the horror that is running rewire. IMO rewire has always been a dumpster fire of a way to use Reason with other daws, and I am sooo glad I wont have to anymore (I actually found bouncing stems to be way preferable in my workflow than using rewire)

But to be fair to those people who do use it however, I don’t get why it had to be dumped, as it was still working. Maybe if I was Props I’d never update it again, but I don’t think i’d toss it out. This from the people who haven’t updated subtractor because then 20 year old reason 1 files wouldn’t sound the same...

[ShawnG]

If you are an Ableton user and got Suite, can you use the plugin as a MIDI or Audio VST? Just curious if you can use the Reason sequencers in plugin form to trigger either something like Kong for drums or a Reason synth.

Let’s say you can and use Reason’s drum sequencer (I love the randomization options of Reason’s sequencer) to control Kong. Does the plugin then support Multi-out to Ableton?

I asked the same and got no reply. As far as I understand, no, this is not possible with the reason rack vst. This was the most important feature that has to be implemented with the rack version. To drive 3rd party plugins with reason players and sequencers. And exactly this feature is missing.

Right, but that wasn’t really what he was asking about. According to a guy using the beta on RT, the rack plugin does support multi audio outputs, it is not multi timbral, and will not pass the MIDI through to the DAW, but you can hook up the drum sequencer to a Kong and route 16 channels of audio out to separate mixer channels in the DAW.

[chk071]

A little question about Reason Rack plugin: how many MIDI ports to rack devices does VST3 plugin support? With ReWire I was able to control every single rack device with a dedicated MIDI virtual port from ReWire master, so it would be useful to have same flexibility from the new VST3 plugin.

VST3 like VST2 supports different MIDI ins and outs, so, with so many instruments in the rack, it surely makes sense.

No it doesn't

So it doesn't make sense to you? (Read properly)

Anyway, i never wrote that it actually has multiple MIDI ins. Thanks for the clarification though.

[pgwalsh]

ReWire going away is a bit surprising and I understand why people are upset. You've invested time in setting up your workflow.

However I'm thrilled that the rack is coming to VST. I'll be using Reason a lot more and this will open up Reason to nearly every DAW making it more popular, which means more customers; which means further development and that's fantastic.

I think long-term this is the right approach (maybe not for rewire), but opening up your system to a much broader market is smart.

[stash98]

If you are an Ableton user and got Suite, can you use the plugin as a MIDI or Audio VST? Just curious if you can use the Reason sequencers in plugin form to trigger either something like Kong for drums or a Reason synth.

Let’s say you can and use Reason’s drum sequencer (I love the randomization options of Reason’s sequencer) to control Kong. Does the plugin then support Multi-out to Ableton?

I asked the same and got no reply. As far as I understand, no, this is not possible with the reason rack vst. This was the most important feature that has to be implemented with the rack version. To drive 3rd party plugins with reason players and sequencers. And exactly this feature is missing.

Thats a major shame. Thank you for that. Is it at least possible to drive the reason drum machines and synths with the Reason sequencers? I’d be fine with being able to do that.

[stash98]

If you are an Ableton user and got Suite, can you use the plugin as a MIDI or Audio VST? Just curious if you can use the Reason sequencers in plugin form to trigger either something like Kong for drums or a Reason synth.

Let’s say you can and use Reason’s drum sequencer (I love the randomization options of Reason’s sequencer) to control Kong. Does the plugin then support Multi-out to Ableton?

I asked the same and got no reply. As far as I understand, no, this is not possible with the reason rack vst. This was the most important feature that has to be implemented with the rack version. To drive 3rd party plugins with reason players and sequencers. And exactly this feature is missing.

Right, but that wasn’t really what he was asking about. According to a guy using the beta on RT, the rack plugin does support multi audio outputs, it is not multi timbral, and will not pass the MIDI through to the DAW, but you can hook up the drum sequencer to a Kong and route 16 channels of audio out to separate mixer channels in the DAW.

Oops, missed this. Thank you for that. Not passing MIDI through to the DAW is a bit of a bummer but I can deal with that. Essentially we can use the reason sequencers to control the Reason instruments and then print the audio in our DAW when ready. I can work with that.

Any idea what the CPU usage is like?

[xbitz]

A little question about Reason Rack plugin: how many MIDI ports to rack devices does VST3 plugin support? With ReWire I was able to control every single rack device with a dedicated MIDI virtual port from ReWire master, so it would be useful to have same flexibility from the new VST3 plugin.

VST3 like VST2 supports different MIDI ins and outs, so, with so many instruments in the rack, it surely makes sense.

No it doesn't ( the rack vst ) , some people here are just hypothesising
From cdm article

https://cdm.link/2019/08/reason-11-new-plugin/

quote
Reason Studios also provide some answers on other features:

-You can route audio input into effects, sidechains, splitters, etc.
-There’s no sampling support in Reason Rack Plugin, only in Reason itself.
-Reason Rack Plugin receives both host automation and one channel of MIDI input
-Yes, you can have multiple instances of Reason Rack Plugin. (That means if you want different channels controlling different instruments, you’ll just add more instances in the host.)
-There’s no MIDI output from MIDI generating devices like the Matrix and MIDI effects in this version. (You can still use those to automate internal Reason instruments and effects, though, inside Reason Rack Plugin).

end quote

+" There’s also no drag-and-drop facility of audio, which is too bad – that’s something I know a lot of people use with Native Instruments’ Maschine and Ableton Live, for instance. (That said, implementation in various plug-ins can be a bit rocky.)"

[antic604]

Any idea what the CPU usage is like?

Hard to say at the moment, because it's a "logging" version meaning it collects and sends all sort of diagnostic data. What I noticed it varies drastically depending on what you put in the chain and I don't obviously mean the difference between Subtractor and Vk-2, but even between old, native Reason devices. But I guess that's what beta is for.

[WasteLand]

not to be able to use "Remote" for the vst rack, will break my workflow, with the panorama p1 (and the "scripts" from the community). i do not mind to use rewire, cpu usage is never high.

[qvprod]

A little question about Reason Rack plugin: how many MIDI ports to rack devices does VST3 plugin support? With ReWire I was able to control every single rack device with a dedicated MIDI virtual port from ReWire master, so it would be useful to have same flexibility from the new VST3 plugin.

Thats what I am trying to point out why rewire is superior , rack vst has only 1 midi channel ( not a bus )
So if you're not sequencing fron the internal rack sequencers you're forced to load new rack vst's instances

Why is loading multiple instances such a problem? It’s just a rack, not the entire Reason program. Multitimbral plugin benefits are debatable anyway. Rewire being limited to one core definitely has no advantage in this regard. The only things that Rewire has as an advantage (as of now) is being able to use the Regroove mixer and use players or modulators with an EMI to send midi out to plugins via virtual midi. Otherwise the plugin does everything Rewire does and better.

[Gamma-UT]

I understand some users not wanting to lose Rewire. OTOH, as someone who never uses it, I'm not unhappy that it's one less plugin to fish out of the Rewire folder as, if you're not using the function, they don't seem to do much more than make the host DAW lose stability.