So I got through my first issue with X2, solved it. So onto another issue. Massive latency, dropped & mis-timed midi notes. I've run CWPA9 for over a decade and have never had this issue before.  After I record some small snipets off of one of my synths, a Yamaha CS6X, and go to playback the Midi the timing is miles off the time signature (no matter what I set it at) and also drops off misc midi notes randomly.  I checked the buffer settings in both Audio & Midi and they are way off. Audio buffer is 29.4Ms and Midi buffer is 250Ms  I've tried playing with the buffers but seems to make no difference in the results at playback. And for the midi buffer as soon as I move it below 250ms it freezes from dropout. So I tried moving up the latency on the audio buffer I get no dropout issues but seems to have no difference of the midi's playback is still way off time. Anyone have any ideas here?

Please, give your system/soundcard specs. What driver mode are you using?

It's worth the time to put your specs in the signature, like most here have done. That way you don't need to rewrite them every time. That's the most important info when trying to solve most problems.

I'm thinking sound card too.

 I tried finding what chip-set for this machine (laptop) is and it only says in the ASUS specs for audio is "EAX Advanced HD 5.0, THX TruStudio". And If I look in X2 Edit> Preferences> audio> it only lists as Realtek HD Audio. Can you help me find further specs of the audio chipset? this is the machine I have X2 installed on.... http://www.asus.com/Noteb.../G74SX/#specifications

Well, then. What driver mode are you using? The integrated chips are usually next to useless in DAW work. If it lists as Realtek HD, then it most likely is Realtek HD.

Getting a decent USB-soundcard would make your life easier. Meanwhile, you could try ASIO4ALL driver (free download).  That has helped many to get by with integrated chips.
I still recommend putting your system specs in your signature. Not that whole spec list which includes also the alternatives which you do not have. 

Hi Kalle...

In the Audio pane It shows as WMD/AK (not sure what AK means, never seen it before).... And I know on-board sound chip-sets are not optimal for full out production work

So seeing as I can't seem to change the midi buffer without it dropping out under 250Ms so I pushed up the audio buffer from 29.1Ms (where the wave proflier sets it at I guess) up to 294.4Ms and it replays better but has a 'pushy' sounding playback... and still drops an errant note but not anywhere near what it was dropping yesterday

The machine I want to put it onto is my studio machine that is running CWPA9 perfectly now, I installed X2 onto this machine just to test drive it and was hoping to make the decision to actually purchase it. Was kind of hoping not to have to instll it on my main machine and jack up something until I actually make the plunge

While my old system is working decently I find I cannot not do alot of the things I am slowly finding and fiddling with X2. And my old studio machine is showing its age and alot the hardware and expansions units in have fallen off the radar of support. So it's quickly approaching a point where I will have no choice but (sadly) upgrade and conform to today's standards.

I've always really liked all of CW's products, and so far the work flow in X@ I understand much of it so in that respect it makes sense but also there are many things that I have come across that I have never seen before and am clueless about in X2. It just makes it hard to make a decision like this without a real good test drive.

QAnd some good insight from that do know can help me wade through my tet drive and actually make the decision.

It might be easier to add HTML line breaks <br> than a bunch of dots.

 Thanks scook...

It's been so long I've had to put BR in manually...

Wonder what the issue is here with FF?

old forum software. The only thing that really gets messy with new FF is editing a message with an embedded link and quoting other messages. You have to strip the HTML a tag from around the URL when editing or the updated message will generate a server failure.

On the subject of MIDI buffers.

Set this to 500 (as a minimum). Decreasing it won't reduce latency in the slightest, and increasing it won't affect latency either. Latency is a by-product of the audio drivers and hardware, not MIDI. Put simply, it's the amount of time Sonar looks ahead of itself when reading already existing data from MIDI tracks. A longer time period gives Sonar more time to do the necessary processing to keep up with itself, if you see what I mean.

If that buffer time is too short you get dropouts, missed notes and all sorts of MIDI timing errors.  Increasing it from the default to around 500 (or even more) will go a long way to preventing MIDI timing issues and dropped notes on playback.