27 May
2004
27 May
'04
2:48 p.m.
On Thu, 27 May 2004, Kjetil Svalastog Matheussen wrote:
Hmmm.
I guess you're right. Oh well. Is there anything sensible I can do to
investigate the problem?
Thanks
Carl
Carl Hetherington:
If the audio thread gets killed by the watchdog, there is something
serious wrong. Which watchdog, vstserver's or jack's watchdog? Does your
machine freeze in ten seconds before the audio thread gets killed?
vstserver's, I believe. There's the message about the audio thread
taking 10 seconds and being killed; the audio disappears during those ten
seconds.
I guess this should be an option. In the mean time, in the
jackclient.c file, remove the following lines:
effect->dispatcher (effect,
effEditOpen,
0, 0, NULL, 0);
And recompile.
Thanks Kjetil, that works great. The problem I'm having now (;-) is that
the audio thread gets killed by the watchdog.
Am I right in
assuming that wine doesn't have much to do with the audio
thread?
Sometimes, but it might be necesarry for the plugin developer to sometimes
at least send some kind of message, with the help of wine, to the
non-audio part of the plugin. I guess... If so, what
could be different about the audio code's environment
on Linux compared to windows? Any suggestions on how I can investigate
the problem?
If the non-audio part of your plugin behaves strange, everything can
happen (write wrong bits to memory used by the audio-part for example),
so...