[CM] error building latest sndlib

[lieven moors]

It doesn't seem to drift as much, but it doesn't sound tight either.
This is what I get when monitoring Juce's midi out (just a small sample from
the beginning):

10072,Juce Midi Output:0,Note on,1,70,101
10072,Juce Midi Output:0,Note on,1,67,101
10072,Juce Midi Output:0,Note on,1,64,101
10070,Juce Midi Output:0,Note on,1,60,101
10051,Juce Midi Output:0,Note off,1,70,0
10051,Juce Midi Output:0,Note off,1,67,0
10049,Juce Midi Output:0,Note off,1,64,0
10043,Juce Midi Output:0,Note off,1,60,0
9949,Juce Midi Output:0,Note on,1,70,101
9949,Juce Midi Output:0,Note on,1,67,101
9949,Juce Midi Output:0,Note on,1,64,101
9947,Juce Midi Output:0,Note on,1,60,101
9922,Juce Midi Output:0,Note off,1,70,0
9918,Juce Midi Output:0,Note off,1,67,0
9897,Juce Midi Output:0,Note off,1,64,0
9889,Juce Midi Output:0,Note off,1,60,0
9826,Juce Midi Output:0,Note on,1,70,101
9824,Juce Midi Output:0,Note on,1,67,101
9807,Juce Midi Output:0,Note on,1,64,101
9793,Juce Midi Output:0,Note on,1,60,101

Is it correct to assume that these time values should be the same every 
four notes,
or could they be influenced by the performance on my computer?



Heinrich Taube wrote:
> eval this an tell me if this drifts:
>
> (loop for i from 1 to 61 by .25
>       do
>       (loop for k in (key '(c4 e g bf))
>             do (mp:midi i .2 k .8)))
>
>
>
>
> On Apr 6, 2009, at 1:39 PM, lieven moors wrote:
>
>> Bill Schottstaedt wrote:
>>>> configured with "configure --with-alsa" and build
>>>> with "make CC=g++".
>>>>
>>>
>>> This won't work.  If you're going to use C++, you have to configure
>>> it with C++.  Use
>>>
>>> make clean
>>> configure --with-alsa CC=g++
>>> make
>>>
>>>
>>>
>>>
>>>
>> Sorry, my mistake...
>> thanks
>>
>> _______________________________________________
>> Cmdist mailing list
>> Cmdist at ccrma.stanford.edu
>> http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist
>
>