Intua PLEASE: Midi Clock Sync

edited December 2012 in Support
Intua guys,

I know you are busy with audiobus <!-- s:) --><img src="{SMILIES_PATH}/icon_e_smile.gif" alt=":)" title="Smile" /><!-- s:) -->:):):)

BUT can you please sort the midi clock jitter issue out, I am not able to slave BM2 to my MPC4000. The timing is just bad.

I have used both iRig Midi and Network connection and its hard to tell which one is worse!

More than glad to provide some test, I have a innerclocksystems.com sync gen box which provides sample accurate Midi clock from Pro tools (YES its possible) and a MPC4000 which sends a tight clock signal so plenty of gear to do some testing.

A statement at least of what the situation is would be great, a lot of it will be down to IOS and the iRig interface but at least a starting point to understand what is going on and why its so bad.

Comments

  • edited 11:40PM
    Last I slaved bm2 to reason, and vice versa with just a midi cable. Had to adjust midi latency in bm2 but that was all. I also slave bm2 to the clock from my mpd32, but that clock is a bit shaky!
    It's not sample accurate for sure, but it depends on what kind of music you are producing I guess....
  • edited 11:40PM
    Don't get me wrong, It does sync but the timing is poor and I agree that depending on music it may make more of a difference.

    I can't understand that no one seems to care about sync and jitter, I've seen some conversations on kvr and some blogs recently on timining and it appears that none of the developers seem want to investigate, can of worms?
  • edited 11:40PM
    Same problem, man!

    thanks to this new update midi clock realy sends, but there is nothing i can call synchronisation - the tempo is recieved, but every time i press play, the first beat comes to a different place in time regarding to metrronome in BM2((

    So for me, it is still useless((
  • edited 11:40PM
    Thanks for confimation, I have done a ton of testing. Conclusion is always the same..

    Getting this right would mean so much. Hope Intua will consider.
  • edited 11:40PM
    Don't get me wrong, It does sync but the timing is poor and I agree that depending on music it may make more of a difference.

    I can't understand that no one seems to care about sync and jitter, I've seen some conversations on kvr and some blogs recently on timining and it appears that none of the developers seem want to investigate, can of worms?

    That's because it's just not a reliable way to "sync". There is no location info in midi beat clock.
  • edited 11:40PM
    dubhausdisco,

    Midi clock is reliable providing source and destination can communicate well. Location information is not needed for two devices to run in sync.

    <!-- m --><a class="postlink" href=" ... 2g&index=1</a><!-- m -->

    there are some very nice videos there and its all midi clock.

    I understand that you may not have the need for this, many electronic musicians use midi clock and if BM2 would truly support it well it would be great
  • edited 11:40PM
    OK- did more much-needed research, and id like to post this in response to my own words.. <!-- s:oops: --><img src="{SMILIES_PATH}/icon_redface.gif" alt=":oops:" title="Embarrassed" /><!-- s:oops: -->

    from innerclocksystems.com:

    "Discussions about timing precision in music always invoke passionate debate and there are many who see any quest for tighter timing performance as an obsessive desire for extreme rigidity and control. The assertion being that this is a very negative characteristic and that ‘going with the flow’ and accepting some element of ‘human-feel’ is a far more musically appealing way to be.
    Rigidity has negative connotations for most musicians but a desire for precision and consistency in sequencing is not about rigidity or stiffness at all. Quite the reverse in fact.
    Rhythmic feel fundamentally relies on the strict principle that if a snare is deliberately placed 5 ticks late it must always sound 5 ticks late to faithfully maintain the groove. The potential feel in any rhythm becomes less focused when the snares fall 3 ticks late sometimes and 7 ticks late other times in a pattern or loop when this timing variation is of a random nature."

    the bad news is that even though some of the apps did quite well on their own, when externally synced the same apps fail miserably. This leads me to believe that maybe ios does not like to be externally clocked?
    Have you any more links that i could check out om this subject?
  • edited 11:40PM
    hello dubhausdisco,

    if you can please do some external clock testing using with this newly release app: its called bluemidi and works over blutooth

    <!-- m --><a class="postlink" href="http://www.iosmusician.com/2012/12/bluemidi-bluetooth-midi-for-ios-is-here-has-virtual-midi.html">http://www.iosmusician.com/2012/12/blue ... -midi.html</a><!-- m -->

    according to this the Standard Deviation between messages has much less latency than other methods. I will test and report back, see chart below

    <!-- m --><a class="postlink" href="http://www.jaycoggin.com/home/ios-midi-over-bluetooth/">http://www.jaycoggin.com/home/ios-midi-over-bluetooth/</a><!-- m -->
  • edited 11:40PM
    Update:

    unable to test, only works on ipad3+ iphone 4s with Bluetooth LE
  • edited 11:40PM
    I've got an ipad3, but my phone is a 4. No dice here.
    As I am using the akai EIE, I have numerous USB and one din midi in/out I use. Don't have much use for Bluetooth midi yet. Looks cool though.
  • edited 11:40PM
    Hi,

    do you have a mac computer though? If so you could slave your BM2 on ipad3 to a DAW on your mac and see if jitter is lower than using your normal midi interface

    I may have to get hold of a ipad3+ somehow.. to test
  • It's 2014 And Beat Maker Ver: 2.5.4 ! Midi Sync o'clock timing is still sucks!! I use Beat maker as a Sampler with keyboard midi out Midi in to Beat Maker ! Lots of time it goes of time :( please please fix it!!! Thanks
Sign In or Register to comment.