Screen reader support, NI, Arturia, Ableton and others have all worked on this but Reason 12 has less screen reader support than older versions. It's commercially sound, just look at the success of others who have done it.

Hi, I've been working on various ideas to improve Reason's accessibility through Remote and a web UI to provide speech feedback. I'd be interested to learn if there are any Reason users on here that would benefit from such a project. You can see some videos on these projects on my youtube channel @j...

You can checkout other videos on my channel @johnsexton8082
https://www.youtube.com/channel/UCiN-gC ... UHmTUmSacw

There's more videos on my Reason accessibility project and a few videos on ableton's public beta that now offers screen reader support for live.

As a blind Reason user, who's limited sight has got worse as Reason's screen reader support has also got worse, alturnative options have to be looked at. This latest web prototype I have been working on, uses Reason's Remote SDK with Web UI to provide keyboard navigation and speech feedback of the m...

Well I hope it to include screen reader support, it's possible, other DAWs are now doing it.

I first asked about screen reader support before reason 12 then again after its release. As reason 12 has less screen reader support than previous versions. Although I'm working on a speech web ui to work with reason remote, this is limited as there is no remote control over midi, pitch or rex editi...

Hi, I'm currently working on adding a speech web app for the launchkey mk3 to work with reason. A large part of this work is rewriting the luacodec and thought I'd ask for your feature requests. So far I have come up with the following: 1. A separate ssl mixer luacodec that is locked to the ssl mixe...

If RS extended the Remote to cover block selection you could then have 32 loops of multi-track content all via your midi controller. It is kind of already possible with lua codecs, I believe the nektar P4 does something with loops. There's also the rack extension jammer loops trigger module by retou...

For me it is improved accessibility, add top-menu rooting option, extend remote to cover everything from the browser, tool window, sequencer and sequencer toolbar, blocks etc. If blocks were in the remote scope, you could switch blocks via a midi controller much like ableton session view and if patt...

Yes, accessibility should be an important part of any UI design! Personally my limited sight means almost any text is difficult to read regardless of contrast and size and due to almost no screen reader support, usability of Reason has got worse in V12. This is why I have been pushing for things lik...

As rmtcvolte says, the codec needs to match the midi hardware and the remote items in document scope to set the r/l loop position will not work well with a standard 0-127 pot/fader but instead work best with delta endless encoder or in some cases buttons. However, the code concept is to have the mid...

After following this thread, it seems the nektar doesn't switch the reason 32 blocks in block mode but instead set/store/recall multiple loop l/r markers and moves to the left marker. This can be done with lua codec by using lua variables to store l/r loop presets and the document scope. Therefore, ...

Yes and the gorilla engine by ujam. I didn't know the gorilla engine was a graphical environment. But I never looked into it, to be honest. I'm doing pretty complex coding during my day job already, so I tend to stay away from DSP development in any form :puf_smile: I've not used the gorilla engine...

Would it be possible to add a fade-in / level / fade-out / cross-fade interface to individual note clips, similar to the audio clips? It works fast, and keeps the fader and other volume controls for other tasks. How should this possibly work? A MIDI clip/track has no inherent relation to a mix chan...

However, that said, there is already a visual editor for RE development. Are you talking about what pongasoft is building, or am I missing something? Yes and the gorilla engine by ujam. Although myself I find scripting easier than visual editors because of very limited sight. Screen readers work mu...

I'm on the side of open combinators, kind of an open-source platform. Now if someone was able to write a combinator rack extension compiler that takes a combi patch and generates the build45 sdk source files, that may be something. However, that said, there is already a visual editor for RE developm...

The combinator is a different issue, as it is a rack device in its own right. What I was refering to is the general rooting of devices in the rack, for example, rooting redrums audio outs to seperate mix channels or redrums gate outs to kong pads etc. To do this in reason, you have to flip the rack ...

My guess is the nektar lua codec updates the nektar of beat changes and the nektar controller uses this info to trigger hid keyboard output. As there are remote items for bars, beats, 16ths and ticks. If the midi data being sent is quite minimal, it can update in less than 30ms, enough to sync beats...

I'm not a nektar owner myself but believe it has HID driver as well as MIDI ports, so my guess is that it uses the HID driver to send keyboard actions to switch blocks as I don't believe there are any remote items to do this. To fully understand how the nektar controller works with reason, you will ...

The midi overide map option is saved to the reason song file where as midi remote maps work across all reason projects. Have you made sure your controller is not selected in the quick midi section. As this quick midi ignores the remote sdk and only gives basic midi keyboard control. To get full remo...

Unfortunately there are no remote items to fold/unfold rack devices or sequencer tracks. It may be possible to use third party software like bome to root midi to keyboard actions but its not something I have done myself. Although be aware, remote works from sequencer tracks having midi focus and not...

I hope RS will give Remote some much requested attention, add new remote items like arm rec, select/mute/solo note lanes, browser panel, toolbar, tool window etc.
Remote is how I access most of reason, as screen reader support is almost none in v12.

You can midi map the track monitor and quantize (toggle) in Remote using the document scope. However, there is no remote item for the track arm record instead tracks are armed as they get midi focus and unarmed when not in focus as you select tracks. There is remote items for record automation again...

Tried live some time ago but couldn't get the hang of its midi mapping for controllers. Also live costs more and back when I tried it, the upgrade costttttttttt was higher. Both DAWs are not screen reader friendly and although the push is a good controller, to my knowledge there is no voice output o...

If you are talking about the track enable record sequencer buttons, there are no remote items for these and I have no idea why. However, if you are talking about the enable record automation buttons in the sequencer, then there is a Remote item for these in the document scope. As for record buttons ...