Same with MIDI clock, it’s not necessarily how to set the MIDI clock settings I’m wondering about, more like what device (or Reason) makes the most sense to use as master. If I do it directly, on the other hand, things start getting a bit more complicated, routing-wise. Doing it through Reason is the easiest from a practical standpoint and makes the most sense in terms of consistency (as it would be identical to how the software synths are sequenced), but I don’t know if it does in terms of latency for example. I am however less sure of how to connect everything in a way that I can do all of these things I mentioned above and not have any conflicts, MIDI loops, or suboptimal routing.Īnother example: I could sequence the Bass Station II either by routing it through the virtual MIDI interface in Reason (I know how to do this), or directly from the Zaquencer MIDI out to BSII MIDI in (I know how to do this as well). One example of things I know how to do on their own is transposing Zaquencer patterns: I know how to do this if I have for example the Bass Station II MIDI out connected to the Zaquencer MIDI in, that is trivial - it’s not the basic functionality of it that I don’t know how to achieve. I imagined it was best to describe what I would like to achieve in total though, even if I actually know how to do some of them, to make sure any general recommendations don’t conflict with something I want to be able to do. Some of these things mentioned is stuff I’ve already figured out how to do individually by reading the manuals, it’s tying it all together in the best way that I’m still a bit unsure about. And of course, reading the manuals is something I have both done and will do more. Not sure there’s room in my budget at the moment though. Yeah, a MIDI patch bay is definitely something that’s been on my mind and would greatly simplify things. * Be able to connect future hardware synths that may not have MIDI over USB, keeping in mind that my audio interface only has one MIDI input/output. * Be able to transpose the Zaquencer note patterns. * Have the Bass Station II slaved to Reason BPM settings (I might just have to consult the manual for this). I came up with this while writing this post so I haven’t tried it yet. That way input on one MIDI channel can be used to control parameters of anything in the Reason rack. On the Reason side, this is probably easiest achieved by routing a Zaquencer channel to a Reason combinator, which in turn uses appropriate modules to convert MIDI to cv and route those to wherever I want. * Have a Zaquencer track control automation parameters of Reason instruments/effects. * If possible, maybe be able to automate some Zaquencer parameter settings from Reason. * Have the Zaquencer BPM slaved to Reason BPM settings. * Have the Zaquencer respond to start/stop messages from the master keyboard/Reason. So my question is How should I set this up in a way that makes the most sense? Outside of optimal routing and clock settings in general, there are a few things in particular I would like to achieve: I still only have a rudimentary grasp on MIDI outside of getting signal A to point B. Now, I have everything set up in a way that works as far as everything receiving notes, but it’s likely not the most optimal configuration and clock is probably not configured properly. * BCR2000 with Zaquencer controlling Bass Station II and Reason software synths. Has MIDI over USB and regular MIDI in/out Has MIDI over USB and regular MIDI in/out/through. MIDI in on a Reason bus/channel is routed to a virtual interface and passed on to the hardware. Reason has 4 MIDI buses with, IIRC, 32 channels each. Hardware instruments are represented by a virtual MIDI interface in the rack. I am fairly new to MIDI, and I would like a recommendation on what routing and clock settings would make the most sense for my purposes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |