27 May
2004
27 May
'04
3:48 p.m.
Carl Hetherington:
Seems like you are out of luck. Last thing to try is to start
the vstserver with the --nonrealtime option to see if it can
be the watchdog that is screwing things up. But I doubt it.
I guess you're right. Oh well. Is there anything sensible I can do to
investigate the problem?
You can try to complain to the author(s) of the plugin, and tell them that
it does not work under wine...
--
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. 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...