Forgive me if this sounds like rant. It is and it isn’t.   First I would appreciate if anyone has any similar experience or ideas how to quash some of the following bugs I now encounter on a regular basis with the final version of X3.  

Importing audio/mp3 - When I switch screen set after importing some mp3s/audio into project message at top of screen says “importing audio” again for each audio item, and I can’t work whilst it is doing it (a progress bar appears for each and every item). Also happens when I close the project “importing audio” why?

Still frequent situations where i can’t grab the clip edit point on the bottom edge of clip (volume envelope prompts instead) 

Looping STILL eventually goes out of sync with soft synths! this has been happening since 8.5. seems inexcusable. 

I get plenty of crashes as a result of no particular task. I can' reproduce it.  Could be anything, it just falls over, could this be something to do with bit bridge and plug-ins? Not that crashes are a result of adjusting plug-ins but as an example I recently installed the Line 6 "Gearbox" VST and it is crashing Sonar too. 

  Now I am sure some of you will inform me, along with other adverts  that i can upgrade to Platinum and these bugs should be ironed out but seriously… This was why I bought X3 over X2 and X2 over X1. Can we not see a pattern emerging here?  
 
Best thing is with this new Platinum version they have realised what most people really seem to want: shiny new “things” each month. They’ve cracked it!  Forget making music. Welcome to the shiny new world of app-infused micro-rewards.   
 
I just want a DAW that performs the basic tasks well. Is that too much to ask? I would have been happy with X1 if it worked. Feels like I have been led on a wild goose chase to X3 that still has annoying issues that kills my work flow.   
 
However, don’t get me totally wrong. For the most part I really like Sonar, I like the ProChannel integration and general editing. I’m not going anywhere, I’ve made an investment and I intend to make it work. I’m just frustrated.
 
In hindsight I wish I just stuck with Reaper. I know all DAWs have issues but it would have been a darn sight cheaper lesson.   
 
 It just gets me down that as I’m really starting to find my feet creating the sounds I have always wanted to, my long time trusty companion is doing it’s best to stop me.   
 
I’ve even recently tried putting the PC on the internet so I could update win 7 completely as well as all other drivers/patches. Has made no difference. Just made my machine slower.   
 
Any thoughts guys?  

I can't speak to specific features that are glitchy because I haven't really used them - for instance I hear about loop recording issues from time to time but I almost never do that.
 
My system has otherwise been very stable, with multiple instances of Melodyne seeming to add some instability (so I avoid that if I can). I don't use any 32-bit plugins anymore (only OPX-ProII which I've ported using JBridge, and I don't really use it a whole lot).
 
Does the importing audio thing happen on every project or a specific one? I've never encountered it and I use it a lot.
 
 

Hi mate, 
 
yes, the "importing audio message" it seems to be all projects. Although I use a template but will check later. I'm sure it's all. 
 
Even just starting a new "BLANK" (no template) project gives me crashes. 

One thing that I see, is that you have 6GB of RAM in your setup. Can you tell us how this is configured? Do you have 3 x 2GB sticks, or 1 x 2GB and 1 x 4GB, or 1 x 6GB? Usually RAM will perform much more stably if it is configured in pairs of the same size and type. In most instances I would expect to see 4, 8, 16 or 32GB of RAM in any recently built computers.
It's just a thought, and something that stood out immediately in your specs. It may or may not have anything to do with these issues but it is something I would try as it's usually fairly quick and simple to add a stick of RAM.
There may be others here that can be a little more specific than I can be. Good luck and let us know if you have any success.

X3e is a very stable version, but the looping issue still get threads in the new SONAR. With the 64-bit version, I avoid 32-bit plugins anymore.
 
As to the other things (stability related), in addition to the above, here is a quick list off the top of my head to check:

1. Run latency monitor to see what is going on for background processes, some may need to be disabled.
2. Do not allow the machine to ever sleep/hibernate/idle ports.
3. Disabling core parking if enabled.
4. Does the (Windows) Event Viewer specifically give you the cause of the crashes (there should be info in there)?
5. Disable Wi-Fi when working as a DAW.
6. If importing audio is slow, consider defragging the hard drive (if a magnetic HDD).
7. Virus scanning software (as with any background process) can slow things down.
8. What is the resource monitor seeing (both in X3 and Windows) when running normally?
9. As you said a new blank template also crashes, if specific plugs are used these would be something to look at.

I am not sure on the importing audio. I always "copy imported audio" using per-project folders, and once copied that is "it." Never seen anything after that point. Are you perhaps copying from a thumb drive? It has been noted that shifting screensets (that have the browser open in them) will read connected drives again.
 
Sorry for the haphazard reply, but hopefully can give you a few ideas at least. Stability issues like you describe with X3e is not normal.

For the seemingly random crashes ... system chipset and audio drivers are always suspect.  If the drivers are up to date, you can also disable some of the generic audio drivers that are running in a default Windows installation; eg, HD audio.  Anderton did an article on this.
 
Yes, I know ... we hate to have software crashes blamed on hardware and/or drivers.  I was a skeptic as well, but ... my own experience is that Sonar is quite sensitive to its hardware environment.  Along the way I've also had periods of instability that away when I did system hardware upgrades.  Most recently I retired a 12+yo audio interface and am now experiencing greater stability than I ever have in the past.
 
As far as bugs/broken software function goes?  It's the territory for the most part.  We live with work-arounds for broken stuff until a fix is released, then we move on to different broken stuff until the next release.
 
Best of luck getting it sorted out.  I know how frustrating it can be to work on tools instead of using them.

rebel007
One thing that I see, is that you have 6GB of RAM in your setup. Can you tell us how this is configured? Do you have 3 x 2GB sticks, or 1 x 2GB and 1 x 4GB, or 1 x 6GB? Usually RAM will perform much more stably if it is configured in pairs of the same size and type. In most instances I would expect to see 4, 8, 16 or 32GB of RAM in any recently built computers.
It's just a thought, and something that stood out immediately in your specs. It may or may not have anything to do with these issues but it is something I would try as it's usually fairly quick and simple to add a stick of RAM.
There may be others here that can be a little more specific than I can be. Good luck and let us know if you have any success.

 Hi, thanks for you thoughts: the RAM is a Corsair 6GB pack sold on amazon with high reviews rating. http://www.amazon.co.uk/gp/product/B002LZ1FPG?psc=1&redirect=true&ref_=oh_aui_search_detailpage   I don't think that is the issue. 
 
 
 

Sorry to hear you're having some issues.  I'm using X3e and while I occasionally experience something I'm encountering no showstoppers.  But as some have said I'm not using all the functionality in Sonar.  I treat it more like a multi-track tape recorder than anything.  Are you creating a groove clip when you're looping?  I do it all the time and I can't say anything goes out of sync.  This works best when doing it in 4 or 8 bar increments.  

mettelus
X3e is a very stable version, but the looping issue still get threads in the new SONAR. With the 64-bit version, I avoid 32-bit plugins anymore.
 
As to the other things (stability related), in addition to the above, here is a quick list off the top of my head to check:

1. Run latency monitor to see what is going on for background processes, some may need to be disabled. WILL CHECK
2. Do not allow the machine to ever sleep/hibernate/idle ports. WILL CHECK
3. Disabling core parking if enabled. Not sure that is relevant noways? i'm sure I checked this. WILL CHECK
   
4. Does the (Windows) Event Viewer specifically give you the cause of the crashes (there should be info in there)? WILL CHECK
5. Disable Wi-Fi when working as a DAW.  network is hard-wired
6. If importing audio is slow, consider defragging the hard drive (if a magnetic HDD). Win 7 auto- Defrags I think. 
7. Virus scanning software (as with any background process) can slow things down. Was crashing without any virus software on machine (used to be offline) Now using Microsoft Security Essentials. 
8. What is the resource monitor seeing (both in X3 and Windows) when running normally? WILL CHECK
9. As you said a new blank template also crashes, if specific plugs are used these would be something to look at. I meant totally BLANK project not template. 

I am not sure on the importing audio. I always "copy imported audio" using per-project folders, and once copied that is "it." Never seen anything after that point. Are you perhaps copying from a thumb drive? It has been noted that shifting screensets (that have the browser open in them) will read connected drives again.
 
I import audio/mp3 files by dragging files from the browser window (in Sonar) directly into the project. anyone that does that should see the "importing audio" window appear very briefly. this is what I get constantly flashing up for each file. Even when switching screen sets.
 
Sorry for the haphazard reply, but hopefully can give you a few ideas at least. Stability issues like you describe with X3e is not normal.

BobF
For the seemingly random crashes ... system chipset and audio drivers are always suspect.  If the drivers are up to date, you can also disable some of the generic audio drivers that are running in a default Windows installation; eg, HD audio.  Anderton did an article on this.
 
Yes, I know ... we hate to have software crashes blamed on hardware and/or drivers.  I was a skeptic as well, but ... my own experience is that Sonar is quite sensitive to its hardware environment.  Along the way I've also had periods of instability that away when I did system hardware upgrades.  Most recently I retired a 12+yo audio interface and am now experiencing greater stability than I ever have in the past.
 
As far as bugs/broken software function goes?  It's the territory for the most part.  We live with work-arounds for broken stuff until a fix is released, then we move on to different broken stuff until the next release.
 
Best of luck getting it sorted out.  I know how frustrating it can be to work on tools instead of using them.

Thanks, 
 
 I'm using a Roland Cakewalk Interface (VS-100)! drivers fully updated. I have also disabled onboard audio devices. I haven't updated the chipset drivers since first built the DAW machine. i'll look into this.