Next Propellerhead Reason upgrade (9.5) to include VST support

Audio Plugin Hosts and other audio software applications discussion
Post Reply New Topic
RELATED
PRODUCTS
Reason 14$299.00Buy

Post

Anosou wrote:
johnppp wrote:Hi Anosou, can you confirm that the VST's will still work when Reason is in rewire slave mode?
Afraid not! When in ReWire slave mode, VSTs are not enabled. Similar to how it is in Ableton Live.
Well, that's a deal breaker for me then as I almost exclusively use R8 in slave mode.
I like the idea of not having to choose between Reason and Studio One.
But thanks for being straightforward about it.

Post

ghettosynth wrote:
Anosou wrote:
johnppp wrote:Hi Anosou, can you confirm that the VST's will still work when Reason is in rewire slave mode?
Afraid not! When in ReWire slave mode, VSTs are not enabled. Similar to how it is in Ableton Live.
Which, of course, makes Live less interesting as a rewire slave as well.

Yep, always been a problem with Ableton. Also this breaks one of the main "all in one place" aspects of Reasons usability, now if you slave you'll be missing those elements that depend on a VST instrument or effect.

I think Props have missed a chance to take a big cut of the Vienna Ensemble Pro users territory , especially for Pro Tools users if they'd sorted this out.

Post

and what about MIDI generators(arps, step sequencers) I can see only gate input on the VST devices, do they will be supported later as player devices ?
"Where we're workarounding, we don't NEED features." - powermat

Post

incubus wrote:Image

Two years ago I didn't want this. The only thing I really care about is if I can exchange/sell RE's now.
I just got the email.
Didn't realise that there was a thread about it already.
But yes that was my first reaction.
Hell has surely frozen over.
rsp
sound sculptist

Post

There's so many people in this forum straight up chowing down some crow right now.

Just nommin' crow.

Post

Lol! Guess it's time to bring this out! :D
Image

Post

ghettosynth wrote:
deep'n'dark wrote:
Automatic return is bad for those, who stop to fix something where the cursor stopped. Right now you stop and press stop one more time to get the cursor back.
+1

Just because people whine about things doesn't mean that's what the majority wants. Stop means stop, not stop and move.
Exactly, I would also not like this to happen. I want to be able to edit where the cursor stops, not having it jump to start without me telling it to.

Post

Numanoid wrote:
Urs wrote:Yes, it's been difficult for us ...essential for our survival.
:scared:

Things are bad?
I think Urs means that VST/AU is their core business - it pays the bills and is obviously essential. If they pulled development off to do RE's (which clearly would make far less money with just 1 DAW to sell to), that's... well.. difficult!
Win 10 | Ableton Live 11 Suite | Reason 13 | i7 3770 @ 3.5 Ghz | 16 GB RAM | RME Babyface Pro| Akai MPC Live 3 & Akai Force | Roland System 8 | Roland TB-3 | Roland MX-1 | Dreadbox Typhon | Korg Minilogue XD

Post

EnochLight wrote:
Numanoid wrote:
Urs wrote:Yes, it's been difficult for us ...essential for our survival.
:scared:

Things are bad?
I think Urs means that VST/AU is their core business - it pays the bills and is obviously essential. If they pulled development off to do RE's (which clearly would make far less money with just 1 DAW to sell to), that's... well.. difficult!
But some u-he plugs have been made NKS compatible, so I guess they see Native Instruments as a more safe bet that Propellerheads.

Post

Numanoid wrote:
EnochLight wrote:
Numanoid wrote:
Urs wrote:Yes, it's been difficult for us ...essential for our survival.
:scared:

Things are bad?
I think Urs means that VST/AU is their core business - it pays the bills and is obviously essential. If they pulled development off to do RE's (which clearly would make far less money with just 1 DAW to sell to), that's... well.. difficult!
But some u-he plugs have been made NKS compatible, so I guess they see Native Instruments as a more safe bet that Propellerheads.
Entirely minor changes needed compared to RE format implementation.

Post

VST support in Reason is long over due, especially in today's market.

Although Reason will not become my go-to DAW now or in the foreseeable future, as it still needs several other features, IMHO, I will definitely upgrade my version 7 license when version 10 is released.

Post

Some of the Reason team seems to be reading the responses here, so...

On the play cursor issue, I agree that it is annoying. Reason's stop behavior is actually pause behavior. So what is needed there is a return to last play position function (a stop function). But more broadly, Reason is long overdue for user defined hot keys. That said, I do very much appreciate it when someone from an application development team goes to the trouble of defining sane defaults for hot keys. It has value for beginners and advanced users alike. But it is very frustrating when some of those default hot keys go against the grain of what makes sense to me and works for me personally.

And related to this hot keys issue, it is also frustrating when there is already a function in an application for something that I regularly use which can't be accessed via hot keys, forcing me to use a mouse, or when there is a very obvious function which should be implemented but is missing.

Reason team: Consider giving some thought to functions and hot keys. Removing points of continuous frustration is as big of a deal as adding major new features, from a user perspective. To users, these frustration points might as well be bugs, because things just don't work how they should. Anyone remember that MIDI editing annoyance that eventually got fixed? With grid snap on, dragging a note to a new location would snap the end of the note to the grid rather than the most sensible default behavior of snapping the beginning of the note to the grid. It may have seemed like a minor issue from a developer perspective, but I assure you that it was very frustrating as a user, as are the functions and hot keys issues.

Here is a practical example of the general functions and hot keys issue (in addition to the play cursor issue): Reason has a fullscreen mixer. It is accessible via the hot key, F5. First, F5, F6, and F7 keys aren't the most user friendly choices for switching between views. There is no obvious mnemonic association between those keys choices and what they do, which becomes a small point of frustration to new users. Second, when accessing the mixer, it is usually a specific section of the mixer that is being thought of, not the whole mixer. For example, if I'm working on a snare track and it comes to mind to make an eq adjustment to the snare, what I want is immediate access to the eq of the snare track, not a complete view of the mixer or a view of the mixer with collapsed sections. So last that I spent any time in Reason (v6.5), it worked like this: I'm in the arrange view recording and editing drum parts. I want to make an eq adjustment to the snare. I press F5 to bring up the mixer section, look in the navigator for the eq, and click it to switch to the eq. Then I look for the track that I'm working with in the mixer. And if the eq section is collapsed, I click to expand it. Then I finally make my eq adjustment. But this was all a very indirect way of doing things, and each time that I do this, I think to myself about why the development team hasn't ironed this out yet and that I have not been enabled as a user (via functions and hot keys) to do anything about it personally. Now how it should work from my perspective as a user: I press my user-defined hot key (a key combo that makes sense to me, personally) for the eq section of the mixer, and since the last track that I was working on was the snare track, the eq section of the mixer comes up and gives a little flash to the snare channel, immediately pulling my eyes to the eq for the snare (a direct connection to what I was thinking about), all with one key press.

Don't take the above example as being a single specific issue. I only wanted to illustrate a practical example of a general issues and how many small frustrations come of it.

And when I get time, I want to harp on about why it makes sense to develop for linux. But I have already sacrificed a good portion of my music practice time today in writing this post, so it will have to wait... I'm already commenting on a daw that I won't be using in the future (not out of application preference, but out of os preference).
Last edited by sellyoursoul on Fri Apr 28, 2017 4:26 pm, edited 3 times in total.

Post

Just to be sure. Are there any limitations on vst's? We can use Toontrack stuff?

Post

aMUSEd wrote:Exactly, I would also not like this to happen. I want to be able to edit where the cursor stops, not having it jump to start without me telling it to.
When you're recording multiple takes it is extremely annoying having to press stop twice to go back where you've been.

Post

Reason was always my favorite go-to music production software some 10-15 years ago. Now when it finally has VST support it will probably become my primary DAW again. FINALLY! It has been "in the shadows" and not my #1 tool for too many years now.

The news that Reason will get VST support is the biggest audio production related news for me in 2017, I'm very happy that PH finally delivers on the number one feature request among Reason users!

Now I'm really looking forward to start working in Reason Lab again!! :love:

THANK YOU PROPELLERHEADS!! :tu: :clap:

Post Reply

Return to “Hosts & Applications (Sequencers, DAWs, Audio Editors, etc.)”