Re: [Jack-Devel] OS X jack midi message issues between jack and core midi

PrevNext  Index
DateSun, 15 Jul 2012 19:10:13 +0200
From Stéphane Letz <[hidden] at grame dot fr>
ToIain Duncan <[hidden] at gmail dot com>, Devin Anderson <[hidden] at charityfinders dot com>
Cc"[hidden] at lists dot jackaudio dot org Developers" <[hidden] at lists dot jackaudio dot org>
In-Reply-ToIain Duncan [Jack-Devel] OS X jack midi message issues between jack and core midi
Le 15 juil. 2012 à 18:58, Iain Duncan a écrit :

> Hi everyone, following Paul and Stephane's suggestion, I ran jack_midi_dump along with a standard os x midi monitor during my sync tests.
> 
> Files, including source and screenshot, are at:
> http://industry.flyingnotfalling.com/audio_code
> 
> Here is what I've found ( duplicated in link as jack_midi_test_notes )
> 
> - system is OS X 10.6.8
> - jack is Jack OSX 0.9 ( beta from Stephane )
> - test app compiled with: 
>   g++ -o jack_midi_1 -framework Jackmp jack_midi_1.cpp
> 
> - occasional clock messages are either dropped or duplicated
> - if you look at the top of the screen shot, you can see:
>   - 24 clock messages per quarter in the jack_midi_dump output
>   - a duplicate clock message at 9:38:838 and 9:38:839 in the midi monitor
> - when these duplicate messages happen, there is a noticeable lurch in the sync
>   with abletone live ( running using jack as audio driver )
> 
> With my larger app, it's mostly dropped messages instead of duplicates. I could get screen shots of that happening if that is useful too.
> 
> Not sure what, if anything, I can do next. Does this mean that the Jack midi to Core Midi bridge is the culprit?

Possibly yes.  Devin Anderson <[hidden]> wrote this code.

Devin any idea? or any idea how to test ?

Thanks.

Stéphane 
PrevNext  Index

1342372229.6474_0.ltw:2,a <EE45F745-9A57-4A6D-A522-8256AB889EB3 at grame dot fr>