![]() You can also download the combinator 1 effect patches that go with the these devices. I presume you have checked out the PEFF effect devices Directre and/or Buffre, they may be of some use. I also purchased Sugar Bytes Turnado, so my loop options are now very good along with the Impact LX+ scenes option, and resetting steps in player devices and not forgetting Octorex Looping effect options with RE player devices like Drum Sequencer which has reset step and Sequences with Auto Reset are very very useful inside a Combi with a flick of switch or perhaps key my 32 bar loop goes to 4 bar for a nice fill in or just 32 to 8 bar for instance loop feel during part of a track like a so called middle eight etc. The problem being it is manual with more things to do than just hitting a pad on the Impact LX+, and of course it isn't quantized. Unfortunately whatever it is, it isn't very well documented anywhere.īefore I purchased the Impact LX49+ with the lovely 'scenes' button, ooh yeah! I was using pc keyboard shortcuts : So set loop or L - R indicators to say 0-16, ALT+arrow up or down to move the set loop left or right across the sequencer quickly, then, with NUM Lock ON, press 1 to hit L indicator immediately or 2 for R indicator. Regardless someone should be able to reverse engineer this so it can be generically triggered. midicodec file or Lua Codec support via a. There must be something going on that taps into a feature natively available within Reason be it undocumented keyboard shortcuts, MIDI remote signal support via a. This is the mystery as if they're simple keyboard actions, surely these could be replicated using just any standard keyboard? I have requested many updates to remote, including adding remote items for blocks, browser, sequencer, toolbar and tool window. To fully understand how the nektar controller works with reason, you will need to monitor both the midi ports and hid port plus see how the lua codec manages the midi. 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. I'm away from my DAW at the moment but will have a play later and see if with a little hacking this is something that could be easily accessed for all Reason users. Just reading this soundonsound guide here, perhaps of some use. ![]() I didn't know about this before yesterday but I actually think it's the strongest potential I've seen yet for the in-time clip triggering behaviour of Ableton Live to be replicated within a Reason environment and not just for Nektar users but for all Reason users. midicodec files to trigger those same commands from any hardware controller? Or perhaps none of this is necessary and it just requires hacking around in. Then we can duplicate those exact same MIDI commands in software which would mean any piece of hardware could then theoretically trigger those same MIDI commands, perhaps using something like ControllerMate or Bome to translate if need be. What would be good is if someone with a Nektar which works like this can use a MIDI monitoring app to see exactly what the MIDI messages are that the device is sending to Reason when those clip buttons are pressed when in 'scene trigger mode'. i gues you're thinking about something like this, right? This commercial software is also written with larger scope in mind, meaning potentially developing from ground up will be a hardship.Yep seen it. The website has not been updated since 2018. there was a working beta version of Karabiner always available- I cannot say the same with ControllerMate. Given the fact that Karabiner was able to jumpstart the process with a beta version in hand, -i.e. It took roughly 11 months for Karabiner to release a stable version when major kernel changes took place in Sierra. ![]() Unless your computer runs on specific environment which primarily runs only that application, it is better to simply look for an alternative app. And personally, I cannot recommend postponing a major upgrade for an application with no time table to support a new OS. Karabiner is a superb application but with a caveat it cannot grab non-standard keys, such as a calculator key. There are two options for ControllerMate-only users: a. Unfortunately, circumstances surrounding the app seem to suggest the developers either do not have a specific time table to support Catalina or do not plan to support Catalina. I’ve been made aware ControllerMate does not work with Catalina in current version. This is a quick announcement for anyone who read my MS Sculpt Keyboard posts. ![]() ControllerMate Not Compatible with Catalina
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |