Re: [Jack-Devel] CoreMIDI driver bug fix

Hi Christian,

On Tue, Mar 5, 2013 at 3:13 AM, Christian Schoenebeck
<[hidden]> wrote:

>> "For now" could end up lasting for a while, and you might just be
>> providing a workaround to a real problem that could present itself
>> again in the future.
>
> No. "For now" means for this very first iOS release.

I hope you're right.

> What would you do? Release this first iOS version of JACK without those 2
> potential fixes, and you already know the CoreMIDI driver won't work this way
> for certain people? I prefer to have them addressed, even just on theoretical
> basis already.

In your place, I would create a pre-release version of JACK has:

0.) jack_error() and jack_info() logging
1.) Verbose debugging enabled
2.) A fix to the problem we know about
3.) A *loud* debug message that's emitted if running status is found

... and I would ask some of the users that complained about the
problem to test the pre-release version.

Knowing what the actual problem is may serve you well in the future.
Not knowing what the problem is may very well bite you in the ass in
ways you don't expect.

-- 
Devin Anderson
surfacepatterns (at) gmail (dot) com

blog - http://surfacepatterns.blogspot.com/
midisnoop - http://midisnoop.googlecode.com/
psinsights - http://psinsights.googlecode.com/
synthclone - http://synthclone.googlecode.com/

1362546130.24271_0.ltw:2,a <CAG7zqTp7+S2S2n9nEFq890b7=oEAqXkQc6K1r6EqcY9mE5AWjg at mail dot gmail dot com>