I think if RS added reason+ annual subscription to the reward store I would get it but like others I prefer owning REs and Reason in the knowledge everything will just keep working even if discontinued. This is important if you own and use discontinued REs. I'd also like to see Reason upgrades added...

It is worth noting that the bassline generator is in the reward section of the prop shop, this is great to see, as it is normally held back until people have paid full price. I'm hoping to see reason upgrades and reason+ annual subscription added to the reward store next.

I agree some small workflow improvements can make big differences to end users. Personally extending Remote to cover the browser, sequencer and other areas missed would mean less mouse clicks and more control surface action. This has great potential for accessibility and doesn't need a whole new cod...

Although I don't use MIDI out I can really appreciate where you are coming from. I don't think they have updated the send MIDI clock from probably Reason 3. I remember a small update for linking Ableton I think in Reason 8 or 9 but nothing for sending MIDI clock. I have no idea why this is, I don't ...

I suspect the Reason devs are focussed on bigger issues but agreed it would be nice to see workflow improvements. The only potential issue I can think of, with new alt-takes at the start of each loop cycle when recording is empty note lanes and the other point would be should it be a new button perh...

Other DAWs already do it, VST's already do it, Reason partially does it via patch selection but is limited to the current folder of the currently loaded patch. Take a look at Push with Ableton, Machine and NI Keyboards and NKS. From an accessibility point of view, Remote can remove the need to use a...

The Alt button in the transport will create a new note lane and mute all the other note lanes when pressed. Where as the Dub button will create a new note lane without muting other note lanes. Neither are done automatically upon loop start. I believe audio tracks are treated differently, perhaps due...

thanks,

I prepose the following basic new features that keep with the backwards compatibility support of Reason and help move things forward. 1. Extend Remote document scope to include the browser, sequencer toolbar, keyboard/mouse controls for a more fully featured MIDI control. This not only gives users a...

Hi, I'm new to RE development but would like to put the idea forward: Add the upgrade and full license to the reward scheme. Add a percentage of the reason plus as reward points. Then as users pay subscriptions, and/or buy REs they build up reward points allowing for greatly reduced/free purchases o...

Add midi I/o data to the RE sdk, to allow development of devices that can split by midi channel or add midi channel splits to the new combinator. Add remote items for the reason browser and sequencer tools in document scope.

How about a new player device to manage midi i/o? To do things like split midi channel data over 16 sets of cv/note/gate ports, this simple device could be the answer for the lack of multi-channel midi support. A feature often asked for as part of the sequencer. A feature already available in other ...

Reason Remote is left behind, forgotten and under utilised. The Remote SDK is a great way to interface reason to other software/hardware via the midi protocol. Extending the remote item list to include things like the Reason browser and sequencer tools can open the DAW to accessibility through third...

Hi I agree, the Remote was a great idea when first introduced but I believe Reason Studios were hoping for third party midi manufacturers to maintain maps and codecs. However, as the take up from third parties was low and then dwindled even farther, they just left it. I'm hoping my accessibility pro...

What is missing for you in Reason regarding MIDI mapping? The Reason Remote, SDK, is an area that hasn't had many updates since version 3. A few new codecs, updated maps and the export remote info option but no remote items for the browser, toolbar and very limited remote items for the sequencer. Gi...

I've got the big meter now working and fixed an error with the channel select. Many thanks for the help, hope people find it useful.
All the best,
John

The reason why remote overrides are saved with reason document and not patches, is to avoid conflicts. Remote maps and codecs give you the best flexibility, as you map each device once and control is based on midi focus or device locking. This means you can have multiple instances of a device in one...

Thanks, I've got the braille output working on the master level meters but still no joy for the big meter, not sure why this is.
Here's a short video showing the braille output using a braille font. There are links in the description.

Thanks for getting back to us, I think the time_ms works for both in/out midi, so perhaps storing the last update time and comparing that to current time may be the way to control frequency. Can I ask, did you use the changed_items table in set_state function and did you use the item_value or item_t...

Hi, I've started a project to get tactile level meter output using virtual midi cables, a web browser and a refreshable braille display. The idea is to give tactile feedback via the refreshable braille display, that has pins raise/fall to produce braille characters. The concept is to use the big met...

The remote tends to get left behind but it has so much potential. One such idea is a web project I'm working on to use the remote with loopback and a web app to have items spoke out, much like the native-instruments nks project. However, currently there is no remote access to the browser or toolbar,...

I believe you can disable stretch on the audio track, this should allow you to set the tempo without affecting the audio. I think it's something like right-click the clip to disable stretch.

From an accessibility point of view, as I have very limited sight, I can appreciate wanting full keyboard control. Myself I use the arrow keys to select notes then click and edit the values in the toolbar, as this is easier for me than click and drag control. It would be nice to have more keyboard c...

Just as a side note, if you program web code, you can use things like webmidi.js together with the reason remote & loopback to interface between your midi hardware and reason remote.
see this quick video proof of concept where I use this tech.

I've put together a quick test web script that uses webmidi.js & speechsynthesis.js with Reason & MIDI LoopBack. The web script acts as a midi interface between midi hardware and the reason remote. The idea is to use these technologies to have speech output of midi feedback normally only available o...