Reason 12 is here

[aMUSEd]

Would be nice if they updated their keyboard and controller support - still completely skips my NI S Series mk II (and all NI keyboards in fact)

Although it won’t detect your Komplete Kontrol S mk2 automatically, you can get the transport controls working by adding it as a Mackie Control (the KKS mk1 and 2 both support MCU). I have a mk1 and the transport controls work fine. Note that you also have to add it as a regular controller keyboard to use the keyboard and knobs. Let me know if you need more details.

Thanks I was able to add it manually as MCU but the implementation seems limited to transport and scroll using the jogwheel - not even able to toggle loop, metronome or tempo, solo or mute

It's just that they seem so slow to add new devices, NI keyboards have been out for years now. Doesn't make me optimistic about them adding support for more modern things like MPE or Midi 2.

[festeringheap]

I believe it was smart from the heads to think fast and decide to publish a general road map. I was selling it before he the announcement, but decided to keep it once I read it's a matter of months and everything hopefully will be alright

Job well done by the CEO then.
And likely has stopped any requests for a refund of $129 for the year 2021, for anyone who just recently bought the upgrade and felt it didn't measure up to Reason standards. And it will likely generate some future sales when they hit their time targets.

This roadmap could have been published just before the release. But it came after a lot of negative sentiment everywhere. It's damage control really. But it has quelled some people's anxiety about the company and stalled some refunds. Though the people who bought the upgrade earlier this year on sale are well past the 30 day window of return. (they still get two+ versions for the price of one though)

[Artie Fichelle]

I got weak, I bought the update. Not justified, I was frustrated about my fellow humans being brainwashed by big evil.
But it is fun. It can help you trough tough times. Something money can buy.

[EnochLight]

Personally, I don't really care if it was for damage control or whatever - I'm just glad to actually see a roadmap.

[Artie Fichelle]

Yes, VST3 is good, since some of my plugs do not show up, i.e chromaphone 3.

[WatchTheGuitar]

I don't know how well they work with Reason, but there are loads of hosts like Patchwork, Unify, Element etc that should in theory let you host a VST3 inside a VST2 plugin if you really want to use one

[Artie Fichelle]

https://soundcloud.com/tassos-kalides/r ... ropa-patch
thats reason 12, could also be 11

[hotmitts]

I'm using 12 and getting freeze-ups with stuff that worked smoothly in 11...hmmn...also disappointed there's no work being done on integrating all those MIDI VST's which currently don't work in Reason

[EnochLight]

I'm using 12 and getting freeze-ups with stuff that worked smoothly in 11...

I'd reach out to support if I were you...

[antic604]

Yes, VST3 is good, since some of my plugs do not show up, i.e chromaphone 3.

Check plugin manager - perhaps there was some error during the scan? Or you simply have not installed VST2.4 version? Every AAS plugin has both VST2.4 and VST3, inluding the newest one.

Zrzut ekranu (214).png

Zrzut ekranu (215).png

[Arashi]

Thanks I was able to add it manually as MCU but the implementation seems limited to transport and scroll using the jogwheel - not even able to toggle loop, metronome or tempo, solo or mute

Yep. I only have a KKS mk1, so I don't have some of those buttons, but it just gives me transport controls. The Loop button is always lit and doesn't do anything. Can't navigate tracks or clips.

It's just that they seem so slow to add new devices, NI keyboards have been out for years now. Doesn't make me optimistic about them adding support for more modern things like MPE or Midi 2.

I'm not sure how Reason's remote system works, but there are a handful of newer controllers that do work with it. I suspect some effort is required from the hardware company to make their controllers work in Reason, and a lot of companies just don't bother. I have a LaunchKey Mini mk3, which was released in Dec 2019, and it works with Reason — though the support is rather basic. For example, pressing play again while the sequencer is running doesn't stop it. I have to hold Shift and press Play to stop. Maybe Reason's remote interface requires independent play and stop buttons and doesn't have the concept of a toggle. Seems like there's very little effort put into this from either side.

[ShawnG]

I'm using 12 and getting freeze-ups with stuff that worked smoothly in 11...hmmn...also disappointed there's no work being done on integrating all those MIDI VST's which currently don't work in Reason

I’m not sure if anyone at props is working on midi vsts or not, but if they are, it won’t be easy, and it will take a full rewrite of how Reason handles midi in the first place. Unless you’ve never noticed that you don’t have normal midi channel and routing controls anywhere in the program…

[Arashi]

I'm using 12 and getting freeze-ups with stuff that worked smoothly in 11...hmmn...also disappointed there's no work being done on integrating all those MIDI VST's which currently don't work in Reason

I’m not sure if anyone at props is working on midi vsts or not, but if they are, it won’t be easy, and it will take a full rewrite of how Reason handles midi in the first place. Unless you’ve never noticed that you don’t have normal midi channel and routing controls anywhere in the program…

Well, "Players" are basically MIDI effects. I imagine MIDI VSTs would just work the same way, where there's a device in the rack that attaches to any other device and processes the MIDI that gets sent to it.

There actually are ways to route MIDI. By default, MIDI is routed to whichever track you have selected in the sequencer, which corresponds to some device in the rack. But you can also connect individual MIDI inputs to specific devices — right-click any device and select "Lock [MIDI controller name] to This Device". You can see what's connected to what with the "Surface Locking" window (Options > Surface Locking…). I wish it was just a table instead of having to select each controller one by one, but I guess most people don't have that many controllers.

[WatchTheGuitar]

There actually are ways to route MIDI. By default, MIDI is routed to whichever track you have selected in the sequencer, which corresponds to some device in the rack. But you can also connect individual MIDI inputs to specific devices — right-click any device and select "Lock [MIDI controller name] to This Device". You can see what's connected to what with the "Surface Locking" window (Options > Surface Locking…). I wish it was just a table instead of having to select each controller one by one, but I guess most people don't have that many controllers.

I have multiple external MIDI devices and the absolute ballache of setting anything up to use discrete MIDI ins and outs on Reason DAW is one of the main reasons I don't use the DAW much. It's so horrible. Just have an option on each track to define the MIDI input ffs like 99% of all other DAWs.

[Arashi]

I have multiple external MIDI devices and the absolute ballache of setting anything up to use discrete MIDI ins and outs on Reason DAW is one of the main reasons I don't use the DAW much. It's so horrible. Just have an option on each track to define the MIDI input ffs like 99% of all other DAWs.

Yeah, Reason is not great with external gear. It's 2021 and you're still limited to sending MIDI clock to one device only, so you can forget about using pattern-based hardware like drum machines (unless you only have one). There are workarounds, but they're all unpleasant.

Surprisingly, Logic (which was my main DAW from 2002–2019) is pretty crummy at routing MIDI input devices too. All inputs get merged and sent to the currently selected track(s), and the only way to route directly from inputs to channels is the ancient, terrible Environment (which is basically unusable, because it just has a single input "device" with numbered inputs, and the order isn't guaranteed). You can use channels as a workaround, but it's not great. That was one of the main reasons I finally switched from Logic to Ableton Live. Frankly, Ableton's MIDI input routing is quite limited too, for reasons I won't get into now, but it's far better than Reason or Logic.