Hi,
I'm having the dreaded "audio I/O stuck" problem for the first time. I've searched the archives to try to find a quick fix, but it seems to be a recurring problem with no obvious solution. Is that the case?
I've got the problem running on two machines: my production machine (which has a hammerfall9652, no problem until today) and a brand new Compaq laptop. The problem happens in both cases.
On the production machine, I've added some -path and -lib flags to my the .bat file that launches pd. I'm not quite sure yet which external or library is actually causing the problem (it may take a while to troubleshoot, having to restart each time.) After the audio gets stuck, even if I restart, just launching pd.exe on its own gets "audio I/O stuck", which I don't understand.
What does I/O stuck mean? Does that mean the drivers are hogged by some other application? Or do I have a bogus 'lock' file somewhere that makes windows think the driver is in use?
Which raises the question: is there a way to explicitly free the driver right before launching pd?
Thanks!
- martin
if the driver is in use by another application, u should receive an error-message saying so. maybe the audiobuffers are to small. marius. ----- Original Message ----- From: Martin Dupras To: pd-list@iem.kug.ac.at Sent: Wednesday, November 27, 2002 8:51 PM Subject: [PD] Audio I/O stuck, win2kpro
Hi,
I'm having the dreaded "audio I/O stuck" problem for the first time. I've searched the archives to try to find a quick fix, but it seems to be a recurring problem with no obvious solution. Is that the case?
I've got the problem running on two machines: my production machine (which has a hammerfall9652, no problem until today) and a brand new Compaq laptop. The problem happens in both cases.
On the production machine, I've added some -path and -lib flags to my the .bat file that launches pd. I'm not quite sure yet which external or library is actually causing the problem (it may take a while to troubleshoot, having to restart each time.) After the audio gets stuck, even if I restart, just launching pd.exe on its own gets "audio I/O stuck", which I don't understand.
What does I/O stuck mean? Does that mean the drivers are hogged by some other application? Or do I have a bogus 'lock' file somewhere that makes windows think the driver is in use?
Which raises the question: is there a way to explicitly free the driver right before launching pd?
Thanks!
- martin
Small step forward,
I just discovered that part of the problem seems to be having syncgrain~ (win32 version) in the externs folder. I would have thought that externals do not even get seen let alone loaded before called as objects, but I suppose that must not be the case.
New questions:
does anyone else have the 'audio I/O stuck' problem with
syncgrain~ under windows?
is there another good granular synthesis external somewhere?
Many thanks,
- martin
Hi, Martin Dupras hat gesagt: // Martin Dupras wrote:
I just discovered that part of the problem seems to be having syncgrain~ (win32 version) in the externs folder. I would have thought that externals do not even get seen let alone loaded before called as objects, but I suppose that must not be the case.
You mean, having syncgrain~.dll in the folder without a syncgrain~ object beeing used is enough to stuck you audio card? That is very strange, and I have no idean, what this could mean.
Unfortunatly I don't have Win32 at home, where I develop, so I cannot try to reproduce you problem. (Actually, I don't even know, if there were changes to the yncgrain~ code made, while it was ported to w32)
is there another good granular synthesis external somewhere?
I'd like to hear about that one, too.
ciao
Frank Barknecht _ ______footils.org__
-
Frank Barknecht -
marius schebella -
Martin Dupras