Teaser II (?): Improved MIDI output Codec demo...

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'!

Comments

  1. meowsqueakFebruary 28, 2012 at 7:33 PM

    This is great-n-all, but I can't see where you've made this available to your readers... maybe I missed that.

    ReplyDelete
  2. KoshdukaiFebruary 29, 2012 at 4:51 PM

    Hi meowsqueak :)

    I see you're as excited about this as I am about releasing Version 0 of it ;) (well, V.0.1)

    But seriously, there's still some stuff I want to try to add, now that I had the trouble to come this far, this is why there's still no public release, yet.

    I forgot to add channel-aftertouch support (oops) which is quite easy to add (that's for V.0.2) and I'm even interested to see if MIDI Clock sync out is possible (not sure about that, but, I can always try, can't I?)

    After that, I'll be doing some tests and maybe I'll release it, if Reason 7 doesn't show up all of a sudden with MIDI out properly implemented ;)

    Honestly, even though this works, I'm not that proud of how clumsy it is to set it up :/ ...you need at least 4 virtual MIDI ports being merged into another virtual or physical MIDI port. Then, this version of the Codec has MIDI Channel 1 hardcoded, so everything's being sent out as Ch1.

    So, while testing, I'll be also thinking of a more clever way to at least use other MIDI Channels, besides the obvious source-code change by the user or presenting this as 16 sets of 4 Codecs... quite a brute-force solution to this, right?

    Anyway... no hurry, I think, since noone's paying for this, so, it'll be ready when it's ready :)

    ReplyDelete
  3. meowsqueakMarch 1, 2012 at 5:16 PM

    Cool - if you need any help testing on OSX, or want someone to test your instructions, you know where to find me :)

    Otherwise, I'll be watching with great interest - good luck!

    ReplyDelete
    Replies
    1. KoshdukaiMarch 1, 2012 at 5:38 PM

      Thanks meowsqueak! :)

      btw, I just implemented a very elegant solution (well, IMHO ^^) for dynamic selection of the MIDI Channel, so that's the end of the temporary hard-coded Channel 1 I was using initially (for convenience).

      I'm very happy with how it's working :D

      Now, all that's left, I think, is to see if MIDI beat clock can be implemented in a usable way (as in, not drift too much).

      Delete
  4. Jed S.May 31, 2012 at 7:19 AM

    hey man! oddly enough I'm working in almost the same thing you are.. Got a remote codec, a special patch that does midi to CV and a little c++ app that converts this to midi... My day job makes development REALLY slow...

    Odd thing i got full midi note range with only one codec... anyway contact me if you're interested in any help...

    ReplyDelete
  5. KoshdukaiJune 22, 2012 at 7:18 PM

    Hey Jed, thanks for your comment!

    I just realized that my initial reply to your comment vanished and was never posted (darn Blogger! ...or maybe darn my internetz!) anyway, I think I recall saying at the time that, maybe you got full midi note range because you were doing a monophonic stream of any note (thus covering the full range, one note at a time) ?

    I had to use that 4 device trick to be able to implement polyphony through the Remote Codec, using the lightest process possible, to add the least latency to the process... but still, Remote isn't "fast" (i.e. time accurate) enough for this to be a generic solution to everyone, even though it works and it's usable, depending on what we're trying to achieve :)

    ReplyDelete

Post a Comment

Popular posts from this blog

Generic MIDI Channel aware Remote Codec+Map

Image
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 ...
Read more

Arturia SparkLE Remote Codec+Map

Image
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 ...
Read more

Random access to a CV values list

Just added this little CV tool in the free download section (on the right): "K's Basics - Random access to a CV values list" It's basically a way to access through CV indexing, a list of 3x32 "cells" of CV values (well, one of the list is within the Note range of CV values, but this example is enough to demo the concept). So, if you're ever in need of generating a specific sequence of CV values controlled by another CV source, this is one way to do it :) It's like having random or sequential access (in whatever direction you want) to a specific custom list of CV or note values, by using a CV controlled "cursor" (just connect the CV "cursor" source to the Rotary 1 CV input and tweak the Combinator modulation programmer Min/Max values to your needs). This device was enough for something I was testing, but I'm sure it can be optimized with some thought and more time. It won't work well in a real-time fast switching situation,...
Read more