Has anyone completed the recent reason plus survey? https://www.surveymonkey.com/r/reasonplus I was a little concerned about some of the questions like how important is the add-on shop, rack extensions etc. The site is pushing subscription while almost hiding third party REs, Refills and purchase of...

Its in the sticky file locations, I think it changed in Reason 10 or 11.
viewtopic.php?f=4&t=7514631

Here's a short video showing how difficult it is accessing the browser panel using OCR + NVDA, the only way to get text to speech (TTS) of the browser text as Reason 12 has no API for screen reader access to textual content. https://youtu.be/Q3_X0iZwvSA To get an idea of what zoom level I need, run ...

I think the best way would be to have options to save channel presets which can optionally include inserts even connected devices perhaps the option to save groups of channel strips. At present the only way I know of doing this, is by saving song templates with all channels setup but this doesn't al...

As a visually impaired reason user, recent updates to the browser have made accessing the browser more difficult. Now no text inside this panel is accessible to screen readers not even via mouse over. I get poor results with OCR + NVDA and wondered if anyone knows what font is used in the browser pa...

The player device works a little differently to other devices, as it has an automatic gate/note connection between the player and the connected instrument. This allowing for note data to flow back and forth between the player and connected instrument while midi focus is on the instrument. However, t...

Yes, the player device only listens to midi note data, this is a shame and I hope this will be looked at in a future RE sdk update. On a side note, other devices, Instruments, Utilities and I believe Effects can listen to midi performance data and as my first rack extension I am looking building a u...

The timing did range from 34 seconds up to 1 minute 41 seconds based on the length of sysex messages. I was using the first 2 bytes as identifiers followed by 7bit ascii strings, one byte per char with a zero byte to terminate the string. I used loopmidi ports with xamp localhost running webmidi.js ...

thanks for getting back to us and thanks for your work on the remote codec/map, much apreciated, it worked fine, only issue was my braille display driver but that's something compleatly separate. Another thing I noticed today, is the spider audio/cv devices have remote info files with midi outputs b...

While looking at the surface locking tab in options, I noted their is an option to lock a control surface to the hardware interface but even when it has midi focus, the export remote info is disabled. You can not create a sequencer track for the hardware interface, so surface locking seems to be the...

Just did a test with loopmidi, webmidi.js and custom lua codec/map sending 8194 short sysex messages. This took 34 seconds, around 241 sysex messages per second. I'll do some more tests to see if longer sysex messages take longer to send and may be test other midi messages like note/cc.

Just did a test using loopmidi, webmidi.js and custom codec/map sending 8194 short sysex messages and it took 34 seconds from start to finish. Thats about 241 sysex messages per second. I'll do some more tests and see if longer sysex message take longer to send and may be test the speed of sending n...

thanks for getting back to us mc, much appreciated The aim of my project is to use virtual midi cables with a web app and midi hardware, so that the web app can speak out control parameters and their values. I have some initial prototypes working but what I am looking at, is would it be workable to ...

Thanks, I ask as I am looking to write a speech midi app, a kind of cross between the NI NKS speaking software and the novation automap software. The automap software, has 256 pots and 256 buttons and on first focus of a device, the codec sends up to a max of 512 sysex messages to update the automap...

Thanks for getting back to us, the reason I ask these questions is I am looking to write a virtual midi controller, that provides speech feedback of mapped parameters. This is a little like the native instruments NKS project but for Reason Remote and coded a little like the Novation Automap software...

Hi, Has anyone done any timed testing of the remote system? I know there is a 1mb size limit on the length of sysex messages but how many sysex messages can be sent per second from Reason, does the size of sysex message affect the speed? How many general midi messages like note/cc data can be sent a...

Hi, Has anyone done any timed testing of the remote system? I know there is a 1mb size limit on the length of sysex messages but how many sysex messages can be sent per second from Reason, does the size of sysex message affect the speed? How many general midi messages like note/cc data can be sent a...

Why try and make a digital audio work station (DAW) into a video editor? Surely there are better video software already out there? If cubass, protools and logic already do the video support you are after, surely rrp is the solution and if vst3 means you can use video vsts, wouldn't that offer anothe...

Some good ideas, many requests amount to the same thing even if called something different. For example, markers and cue points, track folders and group tracks, extending midi remote to cover the browser, sequencer, like hoboys said, pitch edit. Although it would be impossible to have remote items f...

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...