If you have encoders with delta function you can set the loop makers to them and set it up freely in the timeline, rotarys with values from 0 to 127 wont work for this. It depends on numbers of knobs, buttons, faders, pads and what midi functions each of them can deliver. But the one for the Nektar Panorama series is about 11000 lines and a search for "loop" in the codec gives more then 300 hits, to "borrow" something isnt verry useful imo.Īs all midi controllers are different and have a special codec a general solution is not possible. Ideally we could do with someone who has a Nektar device sharing their Lua codec files so we can borrow the code therein.Īs djsmex stated, it is doable with an adapted luacodec. Therefore, in theory can be replicated for other midi controllers if you are able to write suitable lua codecs for it. This can be done with lua codec by using lua variables to store l/r loop presets and the document scope. At a price of around £75, possibly £50 to £60 second hand, it will be money well spent, a game changerĪfter 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. Personally mate I would just purchase an Impact LX25+ for Reason integration alone and with the scenes button you can start getting on with your projects very quickly the way you intended without having to come to a halt of some sort and inadvertently kill the flow and creativeness you were aspiring to. 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?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |