Koshdukai's Music(al) Reason(ing)

It's Christmas time and all the gift buying'n'giving (and some other random conversations with like-minded people) reminded me of a bunch of hardware I almost got as a kid but... due to unfortunate (financial) circumstances, it was never meant to happen :P Let me begin then, not with the "I wished I could access them" but the main "I almost got them" as a kid: 1)  Casio Keyboard CZ-101 (1984) Because that was the most affordable (4 voice) polyphonic MIDI enabled synth (I thought) I could get my hands on! Also, besides polyphonic, it was multitimbral! =D ...which, in my mind, would kinda solve the issue of only having 1 synth ;) ...and... that never happened :] 2)  Amstrad Studio 100 (1985) I clearly remember passing by a local shop and seeing a mixer-like panel and instantly stopping to investigate it further. It was a 6 Channel mixer with a built in simple BBD echo and a 4 track tape recorder plus a stereo/2 track ta...

Hey :) When connecting an hardware instrument to Reason, where it can work both as a MIDI Controller (sending notes, controls, etc to Reason) and also as a MIDI Instrument (receiving notes, CCs, etc from Reason) it's always good practice to turn off its Local Control. (unless you prefer to set the outgoing vs incoming to different MIDI Channels). Local Control?  What is that ?! Well, usually, MIDI enabled instruments are able to disconnect their physical user-interface (keyboard/pads, knob/fader/buttons controls) from their sound "engine" or section(s). Why is  Local Control needed ? To avoid MIDI feedback loops or double triggering of notes, etc. Imagine the following scenario in Reason (or any other DAW): You have the External MIDI Instrument (EMI) rack device point to Arturia DrumBrute's (in) MIDI port, so you can send MIDI notes from Reason and trigger DrumBrute's pads (sounds). But you also want to receive notes from the D...

Reason9_remotables.txt.zip Now, the only thing better than this would be for Propellerhead Software to keep this list updated, each time a change or new RE is published to the Shop :) ...that or allow the users to extract themselves this information through Reason, at least from the installed REs. Source:  List of remotables added to Downloads page

Part 1: Exploring the NN-XT Patches Explored ReFill: BITLEY WAY BEYOND FAIRLIGHT.rfl Link: http://bitley.laconicsounds.net/way-beyond-fairlight/ Note : This is the previous release, not the newer WAY BEYOND FAIRLIGHT R2 release.

If you have a controller capable of sending MIDI messages on multiple MIDI Channels, like an M-Audio Axiom 's 4 Keyboard zones (so 4 MIDI Channels from the same keyboard) plus the Pads on Channel 10 or an Arturia BeatStep PRO that can send 2 sequences on their own MIDI Channel (1 and 2) and its Drum sequencer on MIDI Channel 10 plus the controller on, say, MIDI Channel 16, etc,  then you certainly felt the need for a MIDI Channel-aware type of Remote Codec like this one. Taking the BSP example, here's how to get its 4 sources of MIDI into Reason with this Remote Codec+Map. Add a Control Surface per MIDI source  with these 3 easy steps: 1)  Add a Control Surface from the " <Other> " Manufacturer and choose the correct " Generic Controller on MIDI Channel __ /< " Model with the MIDI Channel you'll need 2) Give it a proper name, so you know what's the real controller being used with this generic map (that you ...

Hey all :) I've been asked last week to share my Arturia SparkLE Codec so here it is :) (unofficial) Arturia SparkLE Remote Codec (and partial Map) V1.0.2 ReDrum: Added Drum Channel selection support through the Dial encoder Edit Flam with Select+Loop Button Flam Amount  with  Select+Tempo Encoder Shuffle On/Off through Loop Button Actually, this has been sitting on my Remote projects folder for 2 years now (and far from being alone in there, eh), waiting for me to complete the rest of the Remote Map, because my initial need for it was really just to control Kong, Dr.OctoRex and ReDrum, that's why those are really the ones that got some partial love on the included map. Early this year, due to the improvements added to the ReDrum remoteables s ince Reason 8.2 , I ended up making some editing to support the new ReDrum remoteables :) I'm hoping that anyone wanting to extend it or complete it has enough examples already in the partial map I'm ...

Reason's BV512 Digital Vocoder rack device always had a very useful behavior regarding its use as a MIDI-to-CV utility device. Before the Kong Drum Designer rack device, which is typically the easiest and preferred device to convert a MIDI Note (i.e. Pad hit) into a CV Gate output (each pad has a CV out gate at the back) the BV512 Vocoder was the only rack device offering a similar behavior. How? (RTFM ;) The BV512 MIDI Implementation made it respond to a range of MIDI keyboard note input to control each of its 32 Vocoder Bands. This allows various cools tricks related with directly controlling specific and multiple bands while in Vocoder mode. The 1st 16 of those Vocoder bands, when activated (either by audio modulation or MIDI note input) will have their respective value output as CV at the back of the device. So, as you can see, prior to Kong , this was the perfect way to get at least 16 MIDI Note-to-CV Gate/Vel...