brconflict


I highly recommend a rollback point. Also, I really don't like calling support--wasn't a very good experience in the past, but Webex could be useful. Sidenote: Using ASIO Driver Mode doesn't recognize my MOTU 24 i/o even though the MOTU supports ASIO.

br, this is where your problem lies brother. You definitely gotta find a way to use ASIO. I can't even use WDM on any of my systems since moving to Win 7 x64. I'd contact MOTU and see if they can help you figure out why your card is not being recognized. I'm sure you've done this...but if not, see if there are any current driver updates. If you have the latest, sometimes going back a version may help with an issue. I've had to do this a few times too.
 
Also, just for the heck of it...if you have that 64 bit precision mix engine thing enabled, try killing that check box. I can't even use that on my systems for some odd reason. I get pops, clicks, glitches and other weird artifacts whenever I have that box checked. But definitely contact MOTU...you soo have to be using ASIO or you'll always have an issue. If you are using X1 via WDM mode...you're actually lucky to be quite honest. At any rate, good luck...I hope you can fix your issues.
 
-Danny

@Danny; I should have clarified, X2 does actually "see" the MOTU device, even when ASIO Driver is selected, but the DAW not allow me to select them (all grayed out). And yeah, I left the 64-Bit Double Precision unchecked. It works fine for me, but I don't need it. Thanks!

So what's the consensus on the X2a update?

Is it safe to install, or should I hold off for a while until X2b is released?

Thanks.

Ditto, certainly no negatives here with the patch.
 

Noel Borthwick [Cakewalk
]

Thats pretty strange. Have you tried resetting your audio configuration to defaults? 
I suggest that you call  support since can help you troubleshoot it. Its likely to be a configuration issue. 

Well, I did a clean reinstall of X2 and the X2a patch.  The problem I had before is there again:  there is a 3 second delay after hitting play for a project that started pretty much instantaneously in X2 without the patch.  There is a 6 or 7  second delay upon hitting record that was also not there with the same project before the patch.
 
So I tried resetting audio configuration to defaults, and now the project won't play at all for more than a second.  (Thanks for that advice, Noel!  LOL!)
 
I hate getting on the phone with support--often futile--but I have to now.
 
X2 sucked for me because take lanes were so buggy.  (Hit mute on a lane, and it sometimes plays anyway, copy/paste weirdness, etc.)
X2a sucks for me because it won't even play.
 
I'm convinced that X2a has introduced performance issues for some Win7 x64 systems.
 
I've been with Sonar for every version since 2.2.  It's been like having a spouse who is a drunk, and I always knew the only real solution.

Thanks for your input, John.  Of course, you have Win 8.  You're very calm and reasonable, as always, while my post was downright ornery (sorry about that).
 
I got on the phone with tech support, and the problem is still not solved.  We went over some settings in configuration and buffers, but basically, the tech suggested that the problem is something in my old project (which was created in X2), since a brand new project worked fine in X2a.  I even tried dumping all the audio from my X2 project into a new X2a project, as he suggested.  However, the problem persists.  This leads me to conclude again that, with my Win 7 x64 system, the patch has introduced a performance issue.  I must reiterate that the same project had no such problems in X2, but they appear in X2a:  long delay after hitting play and record, long delay in rewinding to now marker, long delay in undo recording along with weird auto-scrolling around the project during the delay. 
 
Sure, X2a seems to work fine with a new project with hardly any tracks, but that doesn't get to the performance issue.  This is disheartening.  I have to work, so I'm going back to 8.5.3 (for layers) to track and X1 to mix.  I have to give up on X2, and my future relationship with Sonar is in doubt.  Maybe I'll try X3 or just fork out the big bucks for a new Pro Tools system.

No problems with either X2 or X2a here with W7 64 bit (except one instance of a random crash with X2 after opening Rapture). For me X2a is more solid than X1d was. 

I upgraded straight from X1d to X2a and noticed a hit in performance too. After playing around I changed the "ThreadSchedulingModel" to 2 even though it's not recommended for dual core systems (I have a Core2Duo Macbook with Windows 7), and it seemed to work a lot better. Now almost all my projects play fine at low latency.