Qt-jambi-interest Archive, August 2007
Combining qt jambi with jjack
Message 1 in thread
Hello!
I've recently tried to combining the jjack library (java bindings
towards jack on Linux, now also with JavaSound support :-) with qtjambi.
I experienced a great deal of performance reduction on
capture/renderering sound through jjack when running it inside the
QtJambi scope (that is between the QApplication.initialize() and
QApplication.exec().
However, just testing, I was able to have normal performance when doing
the capture/rendering stuff outside the qtjambi scope, by for example
starting it in a thread before the initialize()/exec() block.
It seems thus that qtjambi is somehow "taking over" the real-time
scheduling in my application. Is there a "qute" way of dispatching such
non GUI needy threads away from the jambi loop besides starting off
threads before the QApplication.initialize() block, which I understand
isn't really allowed...
Regards,
Helge Fredriksen
Message 2 in thread
Helge Fredriksen wrote:
> Hello!
>
> I've recently tried to combining the jjack library (java bindings
> towards jack on Linux, now also with JavaSound support :-) with qtjambi.
> I experienced a great deal of performance reduction on
> capture/renderering sound through jjack when running it inside the
> QtJambi scope (that is between the QApplication.initialize() and
> QApplication.exec().
>
> However, just testing, I was able to have normal performance when doing
> the capture/rendering stuff outside the qtjambi scope, by for example
> starting it in a thread before the initialize()/exec() block.
>
> It seems thus that qtjambi is somehow "taking over" the real-time
> scheduling in my application. Is there a "qute" way of dispatching such
> non GUI needy threads away from the jambi loop besides starting off
> threads before the QApplication.initialize() block, which I understand
> isn't really allowed...
>
Hi Helge,
It is perfectly ok to start threads whenever you like in Qt Jambi. The
only requirement we have is that you don't use these threads to access
objects created _in_ the GUI thread. Could you be a bit more specific as
to where you found this information, so that we can update our
documentation to be more clear?
best regards,
Gunnar
