BM2 doesn't like to share clock?

edited May 2013 in Support
Using BM2 in the input slot in audiobus and loopy hd in output. Both are set to receive midi clock from my mpd32. Now granted the clock from the akai is a bit shaky, but I give it a bar of warm up time....
Loopy locks in, but BM2 runs at twice the tempo!

After re-setting everything up, the same exact way, BM2 has gone completely insane and is showing a tempo of 186 THOUSAND and something!!! And it keeps starting and stopping on its own.. Something is not right here...

Comments

  • edited 5:51PM
    Maybe BM2 receives 2 times a clock signal (from Loopy AND your MPD32)?
    Make sure that in the MIDI In(!) section of BM2 only the MPD32 is enabled.
    Does it help?
  • edited 5:51PM
    Thanks still2... I'm not at the iPad right now but that makes perfect sense <!-- s:oops: --><img src="{SMILIES_PATH}/icon_redface.gif" alt=":oops:" title="Embarrassed" /><!-- s:oops: -->
    I'm trying to set up a live scenario with BM2 and loopy... You mess with loopy at all?
  • edited 5:51PM
    Just checked it out and it's still doing weird stuff no matter which way I send clock... Sometimes loopy goes at twice the speed too...
    I've tried every way I can imagine to get it to work, to no avail...
  • edited 5:51PM
    Hm, strange.
    Does the problem just appear when BM2 and the MPD32 are working in Audiobus?
    Are you using virtual MIDI ports? For beeing sure I would disable them (for BM2 in the iOS preferences). Is an other app like i.e. MIDIBridge working?

    Yes, I bought Loopy when it was on sale. I like it very much, because it's working as promised without any heavy bugs. I also like to use it in live situations, but honestly I miss some options to manipulate my loops on the fly (like FX, or other stuff). But I wouldn't say that I'm a poweruser of Loopy. Why do you ask?
Sign In or Register to comment.