Hi!
Did you already try different realtime settings?
I usually start jack by
-jackd -R -P 20 -d alsa (and optional flags)
where R stands for Realtime priority and P 20 sets the Priority to 20
(can have a value from 0 to 99, the higher the value the more priority
jack gets. jack's priority
2009/7/8 Alex x37v.a...@gmail.com
I think that pd's midi out doesn't take whole sysex messages though,
you simply send a stream of bytes. This is how it has been working
for me. I created an abstraction which takes a list of bytes and
makes it into a sysex message (stream of bytes) [adds
Is there a midi latency in mac os x? And a solution like in windows or
linux?
___
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management -
http://lists.puredata.info/listinfo/pd-list
thanks!
Martin, that's excellent using GEM for sound manipulation
Claude, I'm on mainly on Mac OSX so trying to get my head around the
install of GridFlow... but that looks like what I'm looking to do
hc, thanks for the tip on looking at PDP... will now look in more
detail.
cheers,
hmm... grep 4 *.c didn't seem to help when I tried it. Anyhow, I
found two places that would have to change: in s_stuff.h:
#define MAXAUDIOINDEV 4
#define MAXAUDIOOUTDEV 4
and in s_audio_oss.c:
#define OSS_MAXDEV 4/* maximum number of input or output devices */
On a somewhat
Hello Jose,
Thanks for your answer, I have a debian lenny with the kernet rt (Pure dyne)
2.6.24.4 rt4 and pure data vanilla 0.41.4
Midi Latency = 58 - 62 millisecondes
I think asioforall it's only for audio and for MIDI latency.
But I don't know why Max/MSP is better than Pure Data with the
Hi Hans,
I'm pleased to report that it is starting to work on the Mega. I can
toggle up to pin 53. Reporting all inputs causes buffer overruns and I
guess that's to be expected. More testing underway.
Thanks a lot for your work!
a
Hans-Christoph Steiner a écrit :
I haven't had a
