GFX and audio engine coded in a same thread in XT2?

[monsterbeetle]

Hi,

I bought my XT2 license yesterday night, I couldn't resist to the discounted price tag

yet, I'm really annoyed by the graphics performance problem lots of people encounter (running the beta).

I'm on a laptop with a 1.4Ghz pentium M recording guitar and bass through the podXT live ASIO driver, and playing drums on Ezdrummer using padkontrol, playing a few VSTis like nubi and Mr ray at the same time and I get crackles even at the highest ASIO buffer size when there are lots of things displayed on screen, especially when editing furnished midi tracks...

I was just starting to think that both the GUI and audio engine are running in a same thread, in an interleaved sequence... hence the crackles when the audio buffer becomes empty but that the audio rendering code that fills this buffer needs to wait for the graphics rendering code to terminate before it can execute...



Reading old threads on this, it seems like XT 1.4.1 also has this problem, so it like its built into the very architecture of XT 1 and 2...

I just hope its not the case just split that code in threads or use a profiler

When will this be fixed ???

[druid]

I hope it's a different thread as well... Even better if multiple CPU support was added, so that if it were another thread, another CPU can handle it!

[aMUSEd]

I thought it already supported multi CPU?

[disturb]

Would that explain why the graphics engine is 10 times more responsive and non cpu hogging with eXT loaded as a vst in another host ?
Cause that's what happens with eXT1, and probably will with eXT2 too if things stay as they are.

[monsterbeetle]

Have Jörgen or Jon ever made an official statement on this problem?

XT also seems to have a hard time streaming audio to/from the HDD compared to other hosts I know.

[jens]

Sorry, but I really don't think we should have another thread about this (we're in the process of consolidating FR/BR) - please use this one instead:

http://www.kvraudio.com/forum/viewtopic ... 0&start=30

I hope you understand - Thank you!