Clip launcher and macro controls pages

[visheshl]

I'm requesting after a very long time.

But two very key features missing in reason.

1. Session view/ clip launcher view like Ableton and bitwig.

2. Macro controls pages for every device.

Ableton first added macro controls. Your midi controller by default controls the macros of the selected device. You can map any parameters of the device to the macros. Now you can control any device parameters using a hardware midi controller.

Bitwig took this a step further. It added device based macro mapping but in addition to that, it also added patch specific pages.
The most important controls for a particular patch are by default on the performance macro page. You can select any patch and start performing with the midi controller.

I believe all reason devices including the combinator, should have macro pages.
And the devices should come premapped to macros, which the user can modify as per their preference.

Then all you need to do is to configure your controller faders or knobs to control the macros, page selection buttons and device selection buttons.

Add support for launchpad type controllers to control the clip view, and DAW functions.

(In case you're not familiar with bitwig or Ableton, your controller sends 8 midi CCs which control macros of any device. Each page of 8 knobs controls different parameters. You controller also controls the page + and page - buttons on any device., in addition to this your controller could also be mapped to select the device, it could send select device - and + CCs, so you could scroll up and down the devices.
Another reason specific button could be, minimize, maximize selected device.
And also open/close the device group
(combinator)

These features would bring reason standalone at par with Ableton and bitwig.

[jam-s]

The combinator is the Reason way of doing macro controls. I don't think there will be any parallel structure implemented to this.

[Pepin]

Bitwig's system works well, but IMO the biggest issue with Reason's controller support is that everything goes through Remote. Lots of VSTs already have their own MIDI Learn and hardware integration features, but none of that works properly because there's no way to send MIDI data directly to a VST. It shouldn't be necessary to write a custom remote map for a VST that already has MIDI Learn built in.

[jam-s]

You can simply write a sensible remote map for the combinator with a sensible layout once and then use the combinator to map the controls to the VST(i) controls.

Instead of introducing an additional system RS should imho rather make it easy to create remote maps from within Reason.

[Pepin]

You can simply write a sensible remote map for the combinator with a sensible layout once and then use the combinator to map the controls to the VST(i) controls.

Obviously I'm aware this is possible, but it's a drastically inferior solution when compared to the deep integration offered by plugin/hardware developers these days. Stuff like Mini Freak V gives a 1:1 mapping of controls with the corresponding hardware and all the visual feedback that entails. You're not going to achieve that with Remote. This type of integration is becoming more and more common.

VST developers know better than RS how controllers should interface with their plugins, so Reason should provide the option to simply send the MIDI data and let the plugin decide how to handle it. Every other DAW can do this. Remote was clearly designed for the days before VST support existed in Reason, and it's not really suited for VSTs at all (imo).

Instead of introducing an additional system RS should imho rather make it easy to create remote maps from within Reason.

For REs, I agree

[jam-s]

Sure, native support for NKS would be very welcome, but I highly doubt to see it in Reason unless RS is bought up by NI. Also in general the whole MIDI implementation inside of Reason could use some overhaul (also for MIDI 2.0), but I doubt to see this in the next few years as RS is still struggling to get even something rather simple like the file browser working really well.

[esme]

cubase is ecellent for macro support
define it once use on anything

[esme]

clip lanch would be good fit with reason

[Aquila]

I've been wanting a clip launch feature for years now. They could've expanded on the Blocks feature to create an incredible live arrangement and performance tool but haven't really done anything with it since it was first introduced in Record 13+ years ago.

I've had to figure out how to juggle Reason with Ableton in the meantime for any clip launch functionality.

[deigm]

Instead of introducing an additional system RS should imho rather make it easy to create remote maps from within Reason.

This please!

[visheshl]

Instead of introducing an additional system RS should imho rather make it easy to create remote maps from within Reason.

This please!

The thing with macros is that you only need to tell reason which CCs control the macros, page up down buttons, and device select up down buttons.

Then it's as simple as right clicking any parameters and map to macro 1 or 2 or whatever.
You could then save it as a device mapping or a preset based mapping.so whenever you load a device, the device macros are loaded, when you change presets, the preset macro pages are loaded.(Preset pages are arranged/shown before the device pages)

Anyway,
I don't think you guys see the potential to quickly map any midi controller and use it to control any selected reason device.
This feature would remove the need to make remote maps altogether.

Nevermind.
I think I'll just macro map my favourite reason devices in Bitwig and save the presets.
A little tedious, but doable.

[visheshl]

The combinator is the Reason way of doing macro controls. I don't think there will be any parallel structure implemented to this.

I beg to differ, the combinator is a hybrid device made up of many devices inside it, it is not a replacement for a macro controls device.
The combinator itself is a device like any other devices in reason, with its own controls up on the face plate.

And then you would have the macro control device on top of every device including the combinator.
And you would map the control of this combinator to the macros just like any other reason device and save the patch.
Also due to reason's implementation of the combinator, this device would only have patch based macro pages and no device level macro pages.

[deigm]

Then it's as simple as right clicking any parameters and map to macro 1 or 2 or whatever.
You could then save it as a device mapping or a preset based mapping.so whenever you load a device, the device macros are loaded,

That does sound convenient.