This is a really good point I never thought about :thumbs_up: Totally. Not to mention R11! R11 was one of the biggest updates to the sequencer, yet people spread disinformation about Reason ditching the sequencer when R11 was released. R11 was the most attention the sequencer has gotten since pitch...

Yeah makes you wonder if they had just stuck to the rack, focused on just making the rack the best experience it can be, and then offered the rack as a plugin and never pursued the other things, would we be free of all the expectations and haters today? I find, for example, that most of the demands...

I would like to have a series of simple pads. Maybe one row of 8 and an 8x8 matrix. Maybe with customisable pads that are either toggle or onshot pads. Also the ability to trigger in a quantized manner. And also be able to set to a note. Normal trigger pads are curently not implemented in CB2 so it ...

Wouldnt have making Reason a VST plugin solved most issues he had back then? I mean it would have pissed me off but wouldnt that have been a logical step. That was what I was thinking. Did you mean before Record or Record was morphed with Reason? It would have made even more sense before they added...

They never took Session view seriously even though propellerheads where allways pattern orientated - another kindof paradox and missed opportunity.

Yeah the audio track issue back then could have been integrated in the rack concept instead of record. It would have been accepted and could have later transitioned inot the sequencer or not. People left because of this. And they overthought the midi out issue aswell. Sysex, Midi Mixer, transpose? w...

They clearly want to push the perpetuals over to + which will not happen with alot of people. Though it means you actually get more when using + over an update a year. Thats why the increase is so steep. It shouldnt be economically feasable to stay perpetual. The increase is obviously too high for w...

Wouldnt have making Reason a VST plugin solved most issues he had back then?
I mean it would have pissed me off but wouldnt that have been a logical step.

At least Jengstroem in the Remote developer forum reacted to my post and advised me to send a report to a developer email. The support Ticket i sent earlier is being unanswered so far. The bug they tried to solve in 11.39 was that some stepped remote items covered more ranges than they should. The i...

One would think it sends the CC on load. But maybe the emi needs a gate trigger. Would be awkward though.

I'd like to be able to solo the individual tracklanes. Currently you can only mute them. I also would like to see a split clip into tracklanes by note. You can currently manually select a note and then copy all of the same note to another lane but that should be automisable for Drum tracks. Eg i pri...

I second this.

I have been wanting some form of Clip Launching for years and since i am a "remote developer" i came up with a solution that sort of works and i wonder if it could be facilitated by doing that via a dedicated RE. Now, it is not a Clip launcher but my solution stores a number of predefined Loop Marke...

Man, sorry for ranting but i am really banging my head against the wall and need to vent. They didnt touch the internals of Remote for a decade on when alot of remote developers asked for functional changes and now they suddenly want to fix some wrong scaling to smooth something on displays and now...

The thing is this, if you come from Reason suite it installs clean. I had a Reason 10 and a Reason 11 suite installed and it first installed with the Reason 10 settings. I had some issues with that so i deinstalled 12 and 10 and reinstalled 12. That time it installed clean. Not what i wanted but it ...

Now what should i do? Go into the 30k lines of spaghetti code and rescale a ton of values when it might or might not be changed anywhere soon? And then i have to do it again? I can understand your anger but you can´t blame RS for your spaghetti code though ;-) I haven´t checked my custom codecs yet...

lol, yeah. 11.35. Thx alot.

Man, sorry for ranting but i am really banging my head against the wall and need to vent. They didnt touch the internals of Remote for a decade on when alot of remote developers asked for functional changes and now they suddenly want to fix some wrong scaling to smooth something on displays and now ...

Heigen5 wrote: ↑

02 Sep 2021

electrofux wrote: ↑

02 Sep 2021

My current (working) version is 13.5 suite. I really need this version installed on my new Laptop soon.

Here they are - i.e. old versions. https://www.reasonstudios.com/en/reason/updates

Thx, but these are the non suite versions- I think i need the suite version. I found 13.4 though.

You can technically do a hardcoded per patch mapping within the codec (the lua file). But that is a alot of programming work and probably not easily doable on an existing codec. Reason can send the patchname to the codec and this then can decide on the patchname how things are mapped. But as said th...

My current (working) version is 13.5 suite. I really need this version installed on my new Laptop soon.

Is there a link to the pre 11.3.9 version? i might be stuck with it for a while.

There were changes made to remote in version 11.3.9. From the change log: Fixed a bug in Remote where controls scales incorrectly between control surfaces and Reason. Stepped controls mapped to knobs/faders and stepped outputs mapped to smooth displays were incorrectly scaled However, this change s...

It gets even worse:

EG the Mute Button in Mixfood Knock now reports a value of 32 when not pressed and 96 when pressed!
WTF! It used to be 0 and 127.

Nothing works anymore - this bricks any existing bidirectional comunication.

I have quite a few custom codecs for my Launchpad Pro/Mini, Livid Base, dedicated to different devices like Step Note Recorder, Thor etc. My Main Codec has 30k lines of code. Apart from a few bugs they work nicely in Reason 11 suite. In Reason 12 however they dont work anymore! It started with my Li...