Koshdukai's Music(al) Reason(ing)

Missed Part I ? Click here  ...or, just jump right into Part III with a link to ready made Remote Templates and some info on how to use them :) Q3 : Is there a better, full-proof way to get the proper Remoteables list used by a Rack Extension device ? A3 : Sure, from the Rack Extension device's documentation... if/when available :) (or, the tedious manual way already mentioned on the previous Part I post) So, try getting the Rack Extension User Manual, Remote Mapping Chart or even the MIDI Implementation Chart if available and check the index or (usually) the last pages of the User Manual (or try searching for "Remote", "Mapping", "Chart"). The only current example (that I know) of proper Remote documentation: PEFF   Buffre  Beat Repeater : Go to the " Product website " or the " Product support page " and  download the Operation Manual . Check Page 35 (true for v1.0.1) and there it is, the Remote Mapping Chart. The ...

Update : Maybe you should just skip all this and jump right into Part III  since there's a link to ready made Remote Templates and some explanation on how to use them :) But... if you still want to know how those Templates were made, here's some details that helped achieve that: So, we finally got 3rd party devices inside "THE RACK" uh? :) After all the fuss, hype...iness, trying every available Rack Extension possible and buying the "must have" ones, there's an issue related with the Remote side of each one of these new devices inside our Reason 6.5 rack: The only Rack Extension supported by default on all the "factory" provided Remote Codecs+Maps is Propellerhead's own Radical Piano. Yup... so now what ? Here's some tricks for every Remote Dev/"hacker"/enthusiast and/or power user that knows how to or likes to keep their own customized versions of their controller Remote Codecs and Maps. Q1 : What...

...and iOS Figure debut :) ...and here's my Propellerhead Rack Extensions related videos playlist

uh... well... users kept asking me if this'n'that was possible, so, while explaining how to do it I ended up adding stuff to the Codec, namely, it even sends MIDI Program Change now :] Here I'm showing the larger note range: 104 notes now, from C-1 to G7 through the use of 4 Codec instances, each controlling 32 note segments, like shown at the end of the video. These technical demos are always a bit boring, I know, especially non-voiced over ones (and with lame note/chord sequences ;), but I'm in a noisy room at the moment so... I preferred doing yet another "silent" video with just the synths output being recorded. Sorry :) oh, and I keep using VSTi's just because it's easier to capture everything on screen, but any external hardware device could be the target of the MIDI output. Then you can simply record its audio into a Reason audi track, et voila'!

Hi ! :) Made this little demo video today, showing something I tried a while back just to see if it was possible and... yeah, it is, but quite cumbersome and limited of course... Aaaanway, since I mentioned it on a Prop forum thread about MIDI out , I felt like I should at least show I wasn't crazy or lying ;) But... I won't waste any more time on this. I prefer to wait for a proper MIDI output solution from Propellerhead, like I did wait for a proper solution for Audio Input, Sampling and Recording.

FYI : Reason 6.5 and above includes a newer version of TE OP-1 Remote Codec & Map! You can read jump to the Quick Reference Guide down below to get some info about it :) ---x--- Hey! :) You're a  Reason 6  user and you just installed the recent Reason 6.0.2 update  ? (No? What are you waiting for!?!?) Do you have a  TE OP-1  ? (Yeah? Congratz! ;) ...and if you still haven't upgraded your OP-1's firmware to at least OS #12234 (or newer), you should really update your OP-1's OS  ASAP!:) Yeah, so now you can use your OP-1 as a Control Surface for Reason  ! Neat uh ? :) V.1.2 update Before going into some quick basics about this new functionality, let me tell you that there's a newer version of this  TE OP-1's  Remote Map . It's basically a maintenance release to fix a couple of bugs I've noticed and fixed after the first release. This (or a higher) version will surely be included in fut...