unfortunately after the x3e update the same problem persists,it must be something to do with the update patch,the behavior is only present after the update.kinda a catch 22 if you ask me,if you don't update there are a ton of problems with X3a if you do the original problems are gone but you are unable to use prochannel at all.im not sure how to procede from here,there's no answer to this problem and from my stand point  the studio edition features i paid for currently is a donation to cakewalk tomorrow i call tech support and if no solution can be found to this im demanding a refund on the studio edition,i make very little money as it is,so buying studio X3 meant i didnt eat until i recovered the money and if i cant use it i cant afford to just throw it away.  

There are a lot of weird problems that have happened due to Visual Basic libraries not being installed or being overwritten by other ones. I think it's highly likely that with real-time interaction with someone from tech support, they'll be able to get things working.

I know it's a PITA, but it may be worthwhile trying the X3b, c & d updates to see whether the issue is unique to X3e or something in the patching process.
 

Craig, did you mean visual basic or c++?

That's a good idea,which update atleast fixes the timing drift issue and I'll try that one.

Well finally i got in touch with support,unfortunately X3 studio is still down for me,atleast anything to do prochannel wise,ive gone to far lengths to get sonar working as it supposed to but its all been in vain.ill wait and try the new demo see if the problem persists in the new sonar.if so ill be seeing my way out.thanks again for all the help to all that posted,really wished i could get this working,lord knows i tried.
 
~regards~  

I would recommend you to disable Windows "Aero" completely and set your Visual effects to "Best performance". Also try changing in Performancne Options -> Advanced, Processor scheduling from Programs to Background services. I do not remember what my settings there are but play with it :).
 
Also, try to replicate the lag and while doing that, check the Performance Monitor in Task Manager - are there any CPU or GPU or HDD spikes that are unusual? This might give you some direction I think...
 
In Control panel, disable all AUDIO devices but Scarlett, disable all network connections, bluetooth, floppy drives, even CD/DVD drives.
 
I remember having similar graphic issue in the past but unfortunately I do not remember the cause or situation when I was experiencing it.
 

ok ive tried these steps and still didn't help,but i did find out something interesting.i open a empty sonar project,no vsts,no audio,no tracks nothing at all.my cpu is at 1% if i add a prochannel module it jumps to a steady 16% for just one prochannel module.what could this mean?

I wonder if the remaining space left on your SSD is enough. Most drives need about a third or quarter of their storage free to work optimally.

Solid state drives don't have this issue,its one of there benefits you can use the last megabyte without read speed being affected noticably,also the entire program would cause a problem that being the case,this only concerns using anything related to prochannel which end up affecting the whole program...
   Im still trying tho,the tech support is trying to figure it out with me.if once its solved ill post all the results that lead to the remedy so in case of other's running into the same issue they wont have all the trouble im having.