|
|
Post by paddymercier on Dec 9, 2013 5:44:31 GMT
Hello to all.
I'm trying to use MIDIBridge to filter out start/stop messages from FunkBox so all that's coming out of FunkBox is the clock.
I use iPad / FunkBox to pass clock data out to a Boomerang III, but starting and stopping FunkBox also starts and stops loops that are recorded onto the Boomerang.
I'm able to filter FA and FC messages using a MIDI Solutions Event Processor but this causes a latency issue with the MIDI signal which causes the Boomerang III sync to be off.
I haven't been able to find any settings in MIDIBridge that allow me to do this, but I'm guessing I can use Stream Byter to do this.
I don't know much, if anything at all, about the coding language that's used in Stream Byter.
Does anyone know how to do this with MIDIBridge?
Thanks!
|
|
nic
Soapbox Supremo 
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on Dec 9, 2013 8:43:55 GMT
Hi paddymercier,
Yes, you need the Stream Byter and this one line rule:
# block start/stop/continue
FA-C = XX +B
That should do it.
Regards, Nic.
|
|
|
|
Post by paddymercier on Dec 15, 2013 21:50:28 GMT
Hi Nic!
Apologies for the delayed response and thanks so much for the help.
I've placed that rule into Stream Byter in a couple of places in the midi network and nothing's working yet.
I'm sure I'm doing something wrong as I really have no real know-how with this stuff.
Is it possible to send some newbie instructions? I'm happy to send screenshots of what I'm doing if it's helpful to you.
Thanks again!
|
|
|
|
Post by paddymercier on Dec 15, 2013 22:35:39 GMT
Hello again.
Nevermind! I've got it up and running and it's working.
I am seeing a latency in the midi signal getting out of the iPad - assuming that's due to the extra processing...but I don't think that will cause an issue with the loop synching.
Thanks again...really appreciate the help.
|
|
nic
Soapbox Supremo
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on Dec 16, 2013 9:50:29 GMT
Hi paddymercier,
I'm intrigued by the latency comment above. Are you measuring it or are you noticing it just through use?
MIDI data is very sparse compared to audio (for example) and the latency of a signal passing through MidiBridge even with a module enabled is usually not at all noticeable. It would take nanoseconds for the Stream Byter to decide whether to pass or block each message with that rule above. It is possible to run hundreds of Stream Byter rules with no increase in latency normally.
You don't have a value set for jitter/sync delay in the options by any chance do you?
I'd be happy to follow up the latency issue with you. If so, maybe email me and I can get you to send me some screen shots of your setup so I can understand the MIDI signal flow.
Regards, Nic.
|
|
|
|
Post by paddymercier on Dec 18, 2013 22:43:11 GMT
Hi Nic.
I'd be happy to work with you to ferret out this issue - thanks so much for offering.
I will check on the jitter/sync setting...but I don't recall setting any value for that.
Oddly enough...I experienced the same latency issue when using Midi Solutions hardware to do the same thing (refer to my very first post on this topic).
My initial thoughts are:
1. Since there is no latency from the iPad to the Boomerang when no filtering is happening, it wouldn't appear to be the iPad.
2. (what looks like) The same latency is happening whether using Midi Solutions hardware or MidiBridge, so it wouldn't appear to be either of those either.
3. Boomerang sync hesitates to start when start/stop messages have been filtered from the clock signal no matter how the filtering is done...seems like that's the culprit to me.
Perhaps the issue is with the Boomerang software...maybe it gets confused for a brief moment if it doesn't get an explicit start message. The ability to tempo sync is fairly new for Boomerangs...it's a feature of the latest firmware release.
Let me know your thoughts...I'm happy to send screenshots of whatever you want to see. Sorry if this is a dumb question...but where do I find your email address?
-patrick
|
|
nic
Soapbox Supremo
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on Dec 19, 2013 14:04:07 GMT
OK, I reread your original post.
I tend to agree with you that the latency you are seeing is in the Boomerang unit as it tries to sync to the ticks to determine the BPM to run to. It may need to have received a certain number of ticks before it decides the BPM and that clock is indeed running. Ticks are sent 24 per quarter note, so I would guess it wants at least that number of ticks before it says 'OK, this is a clock'. Also, given that it is not receiving the start (or continue) message which is meant to be part of the MIDI sync spec probably means it falls back to that mechanism, where if it received the start message it would start its transport immediately and then adjust its bpm after the fact based on the timing ticks.
Given it exhibits the same behaviour with MidiBridge and the Midi Solutions unit sort of rules both of them out, so I don't think sending me screenshots or trace from MidiBridge is going to tell us anything. I'd say this is one for the boomerang people, but they'll probably tell you not to filter the start out. ;-)
Regards, Nic.
|
|
|
|
Post by paddymercier on Dec 19, 2013 15:31:45 GMT
Hi Nic.
Once again thanks so much for your quick response and all the great info.
Since the only major practical issue is potentially stopping my or someone else's loops during a tune by stopping the clock, I'm wondering if I should just filter out the stop command. I'm thinking that would be a good test too to see if what we're thinking about the Boomerang is true.
If I were to do that - would the rule look like this:
# block stop
FB = XX +B
Thanks so much,
-patrick
|
|
nic
Soapbox Supremo
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on Dec 19, 2013 15:39:53 GMT
FC = XX +B
FB is continue
Regards, Nic
|
|
