Hi All,
Portaudio crashes on my computer when I use PD. (But only about 1 in 10 tries). I can use PD almost free of errors, but 10% of the time - give or take 50% - PD crashes when I execute pd.exe with the -asio flag.
I've been quiet about this problem because I wasn't certain of the cause. But I KNOW FOR CERTAIN that it's Portaudio.
My computer: Windows XP Service Pack 1 MOTU 2408mkII PD 0.35 test 4 (but the problem has been occuring on my computer for months - since approx 0.26 when I started using PD with -asio)
I thought perhaps PD was causing the problem...but after some investigation I realized that I can produce the exact same problem when I execute the following Portaudio Diagnostic executables: available at http://www.portaudio.com/downloads.html (Windows ASIO package)
pa_fuzz.exe (1 in 3-5 attempts) pa_devs.exe (1 in 3-5 attempts) patest_sine.exe (1 in 3-5 attempts) patest_multisine.exe (0 in 40 attempts) did NOT cause the problem even after 40 or so attempts.
With each error, I can see in the Windows Error Report that the AppName (any of the above) caused a problem in module named "PCI-324 ASIO.drv" (which is the Mark of the Unicorn proprietary ASIO driver software.) The MOTU drivers works without flaw in other applications on my computer.
SO MY QUESTION IS: Does PD 0.35 test 4 use the latest version of the Portaudio software? If NO, then has the newer version been tested? If YES, then should this error report go to the Portaudio email list?
Many thanks Regards, Dave Sabine
hi all,
Pd uses portaudio_v18. I doubt that's the latest version, and will check. There's no reason in general to assume a newer version works better than an older one, of course...
cheers Miller
On Sat, Nov 09, 2002 at 11:34:20PM -0600, David Sabine wrote:
Hi All,
Portaudio crashes on my computer when I use PD. (But only about 1 in 10 tries). I can use PD almost free of errors, but 10% of the time - give or take 50% - PD crashes when I execute pd.exe with the -asio flag.
I've been quiet about this problem because I wasn't certain of the cause. But I KNOW FOR CERTAIN that it's Portaudio.
My computer: Windows XP Service Pack 1 MOTU 2408mkII PD 0.35 test 4 (but the problem has been occuring on my computer for months - since approx 0.26 when I started using PD with -asio)
I thought perhaps PD was causing the problem...but after some investigation I realized that I can produce the exact same problem when I execute the following Portaudio Diagnostic executables: available at http://www.portaudio.com/downloads.html (Windows ASIO package)
pa_fuzz.exe (1 in 3-5 attempts) pa_devs.exe (1 in 3-5 attempts) patest_sine.exe (1 in 3-5 attempts) patest_multisine.exe (0 in 40 attempts) did NOT cause the problem even after 40 or so attempts.
With each error, I can see in the Windows Error Report that the AppName (any of the above) caused a problem in module named "PCI-324 ASIO.drv" (which is the Mark of the Unicorn proprietary ASIO driver software.) The MOTU drivers works without flaw in other applications on my computer.
SO MY QUESTION IS: Does PD 0.35 test 4 use the latest version of the Portaudio software? If NO, then has the newer version been tested? If YES, then should this error report go to the Portaudio email list?
Many thanks Regards, Dave Sabine
hi
is anyone else having audio clicks and pops in pd when moving windows or the mouse in OSX? i'm not sure if it's related to portaudio or not. just for fun i ran the portaudio test suite and everything was ok, no glitches while moving windows etc.
some info in case anyone is curious:
PortAudio Test: output sine wave. SR = 44100, BufSize = 64 PortAudio on OS X - Latency = 384 frames, 8 msec* ... numSines = 104, CPU load = 0.811689 Test finished.
Number of devices = 4 ---------------------------------------------- #0 Name = Built-in audio controller Max Inputs = 2, Max Outputs = 0 Sample Rates = 44100.00, Native Sample Formats = paFloat32, ---------------------------------------------- #1 DefaultInput Name = iMic USB audio system Max Inputs = 2, Max Outputs = 0 Sample Rates = 8000.00, 11025.00, 22050.00, 44100.00, 48000.00, Native Sample Formats = paFloat32, ---------------------------------------------- #2 Name = Built-in audio controller Max Inputs = 0, Max Outputs = 2 Sample Rates = 44100.00, Native Sample Formats = paFloat32, ---------------------------------------------- #3 DefaultOutput Name = iMic USB audio system Max Inputs = 0, Max Outputs = 2 Sample Rates = 8000.00, 11025.00, 22050.00, 44100.00, 48000.00, 88200.00, 96000.00, Native Sample Formats = paFloat32,
this is all on a g3/400 powerbook.
cgc
*yeah that's 8msec latency with a $30 USB imic and no OS tweaking at all. i think it might be lying about the 96khz output part.
hi all,
Pd uses portaudio_v18. I doubt that's the latest version, and will check. There's no reason in general to assume a newer version works better than an older one, of course...
cheers Miller
On Sat, 9 Nov 2002, Miller Puckette wrote:
hi all,
Pd uses portaudio_v18. I doubt that's the latest version, and will check. There's no reason in general to assume a newer version works better than an older one, of course...
In this case probably yes, because the V18, if so , only has bugfix releases. The V19 will have a different (only slighly) interface, and will have support for almost any Audio/IO architecture that exists. It will be released in some months or so.
Guenter
cheers Miller
On Sat, Nov 09, 2002 at 11:34:20PM -0600, David Sabine wrote:
Hi All,
Portaudio crashes on my computer when I use PD. (But only about 1 in 10 tries). I can use PD almost free of errors, but 10% of the time - give or take 50% - PD crashes when I execute pd.exe with the -asio flag.
I've been quiet about this problem because I wasn't certain of the cause. But I KNOW FOR CERTAIN that it's Portaudio.
My computer: Windows XP Service Pack 1 MOTU 2408mkII PD 0.35 test 4 (but the problem has been occuring on my computer for months - since approx 0.26 when I started using PD with -asio)
I thought perhaps PD was causing the problem...but after some investigation I realized that I can produce the exact same problem when I execute the following Portaudio Diagnostic executables: available at http://www.portaudio.com/downloads.html (Windows ASIO package)
pa_fuzz.exe (1 in 3-5 attempts) pa_devs.exe (1 in 3-5 attempts) patest_sine.exe (1 in 3-5 attempts) patest_multisine.exe (0 in 40 attempts) did NOT cause the problem even after 40 or so attempts.
With each error, I can see in the Windows Error Report that the AppName (any of the above) caused a problem in module named "PCI-324 ASIO.drv" (which is the Mark of the Unicorn proprietary ASIO driver software.) The MOTU drivers works without flaw in other applications on my computer.
SO MY QUESTION IS: Does PD 0.35 test 4 use the latest version of the Portaudio software? If NO, then has the newer version been tested? If YES, then should this error report go to the Portaudio email list?
Many thanks Regards, Dave Sabine
PD-list mailing list PD-list@iem.kug.ac.at http://iem.kug.ac.at/cgi-bin/mailman/listinfo/pd-list
-
cgc -
David Sabine -
guenter geiger -
Miller Puckette