I'm just wondering if anyone else is experiencing any of these things:

Sometimes, particularly on more complex projects, the auto track height feature stops working, so that clicking on a track does not expand it. I have to manually drag the track down to view it.

Clip preview in the browser has stopped working on several projects.

Velocity adjustments on midi tracks cause problems, as in, it makes that clip not process when I export the project to a wave file.

Lots of dropout problems on projects that should not have a problem playing back on my system.

Importing projects that used the mute track feature in older versions, causes problems. Like I've had instances where those muted clips are not muted in X2.

Most of the time, in the main view, if I view clip automation, such as gain, make adjustments and then switch back to clip view, the automation remains visible.

Sometimes, when adjusting the automation on a clip, automation doesn't move ... and in fact, it might be adjusting automation somewhere else in the project unbeknownst to me because it shows the db levels changing, but not the automation line. Also, when this happens, the click point to start dragging the automation is off ... it's not right on the automation line. It's usually above it. 


Using ASIO on my Echo Audio drivers, I have no way to adjust latency. Nothing but ASIO works with these drivers.


There are a lot more, but these are the ones I can think of right now.

Thanks.

Quote: Using ASIO on my Echo Audio drivers, I have no way to adjust latency

The "Number of Buffers" parameter of a given manufacture's ASIO driver is the latency
adjustment.

For example. I used to use 1024 buffers which added about 1/2 second on latency at the sample rate I was using. I did not monitor through Sonar so the delay was inconsequential,
but gave the system time to breath so to speak.

I would look at the limited memory you have for a 64 bit system.  To my understanding 8 GB is the lower limit for 64 bits.

  The more memory you have the better things will run with Sonar. 

Thanks bitman. I thought about that but wasn't sure. I had already increased it to 1024.
John, so the minimum system requirement of 64-bit is 8 GB? Did not know that. I thought by going to 64-bit I was doing a good thing so I could use the full extent of my 4GB of memory, which I couldn't use in the 32-bit realm. And I bet memory for this slightly older system is going to be high now. Dangit.

Mark

And uninstall and large hungry internet security programs such as the offerings from Norton and McAfee if you have them installed and replace it with something more lightweight such as AVAST free. - Now I'm going to bail before the flaming arrows come.

Rock on.

bitman


And uninstall and large hungry internet security programs such as the offerings from Norton and McAfee if you have them installed and replace it with something more lightweight such as AVAST free. - Now I'm going to bail before the flaming arrows come.

Rock on.

All you have to do is duck Bitman. No need to retreat. 


But seriously we need to offer our best advice without fear. It may not be the right answer but we should not worry about that. I have seen members offer what I think is "way out there" yet proved to be the right answer.  

I can't tell if you are running the X2a patch. If not you might want to apply it. The patch has a lot of Win8 specific stuff.

Have you reduced your undo history from the default 128? I've reduced mine to 8 as I've only got 2 gig of Ram. It made a difference.