6 Sep
2009
6 Sep
'09
1:01 p.m.
Paul Davis wrote:
On Sat, Sep 5, 2009 at 5:33 PM, Iain
Duncan<iainduncan(a)telus.net> wrote:
Also, if it is python we are talking about, it is probably best if those
two loops not be in the same python process, so think the
multiprocessing module rather than the thread module.
Hi everyone, I'm wondering what most linux
audio developers think about
pyqt vs wxpy for writing audio app guis now that qt is gpl'd.
Specifically I'm interested in tightly controlling the timing of event
loop ( ie making some accurate external clock source like the csound
engine be the time boss ) and making decent faders widgets.
my recommendation is that you rethink whatever architecture you're
imagining. you will not, and almost certainly should not, drive a GUI
event loop from anything audio related. you should (IMHO) be thinkng
about two different loops: a GUI event loop driven by mouse, keyboard
and system time(r|out) events, and an audio engine loop driven by the
"clock" of the audio API (JACK, ALSA, whatever). the GUI doesn't need
tight timing (remember that your display almost certainly only
refreshes at no more than 100 times per second, and quite possibly
more in the range of 60-80 times per second.