midi questions

So ever since I recently hung up a few patchbays in a rack solution, I’ve been filling the empty space up with outboard gear. A few reverb units, eq’s, compressor etc. Looks like everybody is going digital and selling of their hardware on ebay-like sites for cheap, nice opportunity to go hybrid B) .

Some of the units have midi support on the back and I am looking for a way to incorporate this functionality with Renoise, last time I did midi over din cables was the beginning of 2000 so I’m n00b with the oldschool ways of daisychaining using thru ports, usb midi ftw! What I remember from back in the days in cubase, I had set the roland alpha juno to receive all I think, and stuff worked, but I figure with multiple devices you have to set the channels differently across units.

Now my question is, what would be the best order of chaining devices, or maybe this doesn’t matter much latency/flexibility wise? (soundcard midi out->alesis v49->bcr2000->korg esx->reverb units-> etc?)

Ideally I’d like to be able to control the reverb units internal parameters without having to go under the desk all the time fiddling with dials and menu pages, I have a bcr2000 which I’d like to use for this through renoise…not sure what would be the best set-up doing this…could also hook up the bcr directly, but like to use the sliders of an instr. midi control device on screen (have these sliders midi-mapped to the bcr).

For now I’ll do the google thing and check the manual midi section, but tips/experiences etc are appreciated :D.

I don’t think you’ll see that much of an impact when sending out MIDI through daisychained devices.

But it’s another thing to control internal parameters of FX devices - for really custom MIDI setups, tools like Guru and xRules could be useful.

But still, see how far you can push it using native mappings first?

But it’s another thing to control internal parameters of FX devices - for really custom MIDI setups, tools like Guru and xRules could be useful.

But still, see how far you can push it using native mappings first?

Yeah, I’ll try native midi-mapping before diving into the specialist tools, think I’ve seen doofers containing the midi meta-device, so that might be a solution getting the most necessary parameters wrapped into one loadable device. Not sure if midi mappings of doofer parameters are saved with the doofer itself, or you have to ctrl+m map them every time you load such device? Will do some testing and see what works best coming week.

Better begin with a midi splitter/thru …reduces the jitter

http://www.kentonuk.com/products/items/utilities/m-thru-5.shtml