rad3d
Converser
Posts: 10
|
Post by rad3d on Oct 22, 2014 13:34:27 GMT
New to MidiBridge, as I'm in the process of moving my Ableton PC setup to iOS. I'm a guitarist and I use Midi foot controllers to trigger samples/loops during live performances. We don't sequence so there's nothing tied to Midi clocks.
I've been using Bome's Midi Translator to handle some more advanced midi translations on the PC - one of which is translating a single NoteOn from my foot controller and having it cycle through a series of NoteOns to a specific output. Essentially, it let's me cycle through a set of pre-defined notes or chords (usually trigger chords on a synth or sampler from a single note) by hitting the same footswitch repeatedly.
Bome's handles this through variables that can be incremented and/or set. Stream Byter looks like it might be able to do, though I'm not sure if it has any variables or logical controls.
Interested is whether this is somehow doable in MidiBridge, either with Stream Byter, or using a combination of other components in the app.
|
|
nic
Soapbox Supremo 
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on Oct 22, 2014 13:45:28 GMT
Hi rad3dCurrently The Stream Byter has no variables as you describe I'm afraid. The only way it can be done is by using the note on events to cycle though a series of scenes with each scene then containing your other mappings. There are a few posts here about using events to trigger scene changes (you essentially clone your trigger event to a program change event which then switches scenes). If you do not wish to wade through various posts (and who would!) just get back to me and tell me a bit about the note on event the footswitch is sending and I can advise how to set it up so that it will cycle through your scenes. Regards, Nic. |
|
rad3d
Converser
Posts: 10
|
Post by rad3d on Oct 22, 2014 14:05:45 GMT
Thanks for the quick reply. Yup, I noticed the scenes feature and was wondering if that was a way to do it. Just wanted to get guidance as to where to start. I'll play around a bit first (only way to learn), and let you know if I need help from there.
|
|
rad3d
Converser
Posts: 10
|
Post by rad3d on Oct 22, 2014 15:47:27 GMT
|
|
nic
Soapbox Supremo
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on Oct 22, 2014 16:05:00 GMT
Yes, that's one of them. This is the relevant postEssentially you set the scene channel to 16 (not usually used) in the MidiBridge prefs and then in your Stream Byter on the input port add a rule like so: 9X 3C = CF 01 +C # switch to scene 001 on middle C note onThat one would be placed into scene 000, then modify that rule on a per scene basis to select the next scene (change the number in bold) until you get to the top scene and it's rule would be to switch to scene 000 so you have your cycle. Regards, Nic. |
|
rad3d
Converser
Posts: 10
|
Post by rad3d on Oct 23, 2014 13:04:03 GMT
Thanks! An initial test worked well. Now I need to get more of my rig together to validate how complex of connections I'll need through MidiBridge. My only concerns with using presets for this is that for each preset, it appears I'll need to solidify, then replicate all of my connections within each preset.
I've got 4 different USB Midi controllers coming in, and at least 2 of them require some custom mappings for various songs through MidiBridge (things I used to use Bome's for). Concerned that every time I make a change in something not related to the cycling scheme, I'll have to replicate updates to all presets used for cycling - and I probably have 6 cycles of about 3-6 events each (~25 total presets needed).
If that's the case, it's probably still workable - and still good to know I can do some of these tricks in iOS. I have to get further along with my rig changeover before I see if this causes any real concerns.
Any possibility you might add some simple variable functionality to Stream Byter? That would keep something like the cycling in a single preset.
Again - the help is much appreciated. Great app!
|
|
nic
Soapbox Supremo
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on Oct 23, 2014 13:34:26 GMT
Hi rad3d, Suggestions noted! Seems like an ability to #include sets of rules might be useful too as well as variables. I am working on a new app which will incorporate the Stream Byter and I may enhance the Stream Byter with some of the ideas that have surfaced via emails and the forum here (Stream Byter 2?). If so, then I would be able to update MidiBridge with the new Stream Byter (in theory). There is a time constraint here in that Apple are disallowing apps to be submitted that don't include a 64 bit slice as of Feb 2015. Neither the Line6 nor Akai libraries have 64 bit slices so I have to drop support for those interfaces with 64 bit iDevices (Line6 MMZ v1 and Synthstation 25) which is something I don't want to do... Have to think about that. Regards, Nic. |
|
rad3d
Converser
Posts: 10
|
Post by rad3d on Oct 23, 2014 14:50:27 GMT
#include would go a long way, as well. Assuming this would be much easier to implement than a full variable implementation.
Understand that nothing comes quickly, so I appreciate you've got these ideas in your suggestion stack.
Thanks!
|
|
