Install only SONAR X1 x64 and don't open any old projects that are not made in X1.

I agree with most of your post Freddie but I open and edit mainly old projects created in V8.x and much before in some cases with no issues of note. I do always do a "save as" and save an X1 version first though just in case but haven't needed the original project yet.

Biggest pain for me is importing my screensets from my template but only needs doing once per project and well worth the trouble.

StarTekh


JonBouy: in responce to your post: What planet did you learn to troubleshoot on again.

That would a a 286 voyetra time code and a 2in 24 track tape unit

Now i runn 0error here.. know what that means No Errors not 99.
>0< good luck !!

StarTekh

I do apologize for my unruly outburst, I know you are a well meaning sort that tries to help out.

ProjectM

Brandon Ryan [Cakewalk
]


FWIW: I can say that I (and a fair number of other Cakewalkers) would not run XP at this point. Not on a new-ish machine.

Hah, I wouldn't even run it on an old-ish machine either! I almost went to Mac because I was so sick of XP!

But like Sven says, a fresh install of everything is like changing to clean underwear and I did that 3-4 times a year when on XP. Haven't had the same needs with Win7 so I figure once a year is ok. However, my current install is remakably smooth.

So I agree with everyone who recomend a clean install of your system when facinging problems like those described in the OP. there's something messing with your system. Whether you choose to go for Win 7 (which I highly recomend) or not is up to you. Tidying up your machine is always healthy

Totally agree. But I think the OP has the gear to go Win 7 ( not sure about his graphic card though) and he should do a clean install of Win 7.  It will be and amazing upgrade to his system.

Nuts I also have to agree again.

But I used an upgrade for Vista Ultimate and did a clean install by simply installing it twice. That gave me a full clean install without having to purchase the full price version of Vista.  I did this with a new HD. 

I didn't want any thing from XP to be on the Vista install.  Saved me a lot of cash. But don't tell anyone.

None the less your point is a good one.

Take care project.

I was so reluctant to move to W7 for a long time. I was just very happy with XP.

I made the change a few months ago.

Wow. It's amazing! I never really had stability issues so can't comment on that, and cpu was never an issue either, so also can't comment there, but have not seen anything worse in W7. Have not checked to see if it's better either. Probably is. My computer definitely loads much faster than XP ever did. XP would be pretty quick on a fresh install, but very rapidly got bad. W7 has been faster, and has not slowed down yet after a few months of general PC usage. And all the extra little features are so nice. Especially the maximising windows when you drag to the top of the screen and the fact that you can drag a maximised window from one monitor to the next. So much nicer.

FYI, a nice little trick to move windows around in W7, hold the 'windows' key and press your arrow keys. It moves the active app or folder window around the screen and across dual monitors. Very handy little feature.

W7 rules - I would never go back

Hi Chauncey,
 
 
First, take a deep breath...
 
X1 has had some problems... but (in general) if you're having major stability issues, I'd say the odds are likely the issue is outside of Sonar itself.
 
IIRC, X1 is making heavier use of the GPU (under Win7).  That alone opens the possibility that other (older) apps could run fine... yet X1 could have issues (running on the same exact hardware).  Craig mentioned video being a potential culprit in a previous post.  I realize you're running WinXP, but don't rule out video without testing.
 
If I was having major stability issues, the very first thing I'd do is strip the DAW (machine) down to the very basics... make sure all is well... and progress from there.  Start with a solid foundation... and build outward/upward.
 

• Backup the system using Acronis True Image.  This way you can always get back to where you are today.
• Next, test the RAM using Memtest.  Assuming this test passes without errors, I'd do a clean re-install of the OS.
• Apply OS updates and latest drivers for components.  Keep hardware to the bare minimum (ie:  No UAD-1/etc).
• Install your audio interface (just the MOTU unit - using the latest driver).
• Install Sonar X1 and apply the C patch.
• Load one of the demo projects into X1... and check the behavior. 
• If the project is running stable, create an up-to-date (interim) backup image file.
• If the project is completely unstable, I'd run a stress-test on the system as a whole (to verify the core hardware is OK)

My guess is that the project will run stable.  If so, I'd proceed to installing plugins.
 
A couple of pieces of hardware pop out at me... as potential culprits.

• FireOne - Tascam Firewire units are particularly fussy about the Firewire controller
• PCI version of the 424 - Check to make sure it's not sharing an IRQ with a major peripheral
• UAD-1 - The UAD1 had memory address issues with some P35 motherboards... and was created prior to multi-core CPUs

 
A complete reinstall is a major undertaking... but weigh that against the time/effort of being frustrated.
If you can establish the machine/Sonar X1 (at a simple level) is working fine, you can build from there.
Once things are squared away, create a finished up-to-date backup image file. 
That'll ensure you don't have to go thru this type of scenario again. 
If you go step-by-step (methodically) thru this process, I'm confident you'll find the culprit.
 
As was mentioned, 'rogue' plugins are also common causes of problems.
 
Start simple, establish a base level of performance, and build from there...

Jim Roseberry


Hi Chauncey,
 
 
First, take a deep breath...
 
X1 has had some problems... but (in general) if you're having major stability issues, I'd say the odds are likely the issue is outside of Sonar itself.
 
IIRC, X1 is making heavier use of the GPU (under Win7).  That alone opens the possibility that other (older) apps could run fine... yet X1 could have issues (running on the same exact hardware).  Craig mentioned video being a potential culprit in a previous post.  I realize you're running WinXP, but don't rule out video without testing.
 
If I was having major stability issues, the very first thing I'd do is strip the DAW (machine) down to the very basics... make sure all is well... and progress from there.  Start with a solid foundation... and build outward/upward.
 

• Backup the system using Acronis True Image.  This way you can always get back to where you are today.
• Next, test the RAM using Memtest.  Assuming this test passes without errors, I'd do a clean re-install of the OS.
• Apply OS updates and latest drivers for components.  Keep hardware to the bare minimum (ie:  No UAD-1/etc).
• Install your audio interface (just the MOTU unit - using the latest driver).
• Install Sonar X1 and apply the C patch.
• Load one of the demo projects into X1... and check the behavior. 
• If the project is running stable, create an up-to-date (interim) backup image file.
• If the project is completely unstable, I'd run a stress-test on the system as a whole (to verify the core hardware is OK)

My guess is that the project will run stable.  If so, I'd proceed to installing plugins.
 
A couple of pieces of hardware pop out at me... as potential culprits.

• FireOne - Tascam Firewire units are particularly fussy about the Firewire controller
• PCI version of the 424 - Check to make sure it's not sharing an IRQ with a major peripheral
• UAD-1 - The UAD1 had memory address issues with some P35 motherboards... and was created prior to multi-core CPUs

 
A complete reinstall is a major undertaking... but weigh that against the time/effort of being frustrated.
If you can establish the machine/Sonar X1 (at a simple level) is working fine, you can build from there.
Once things are squared away, create a finished up-to-date backup image file. 
That'll ensure you don't have to go thru this type of scenario again. 
If you go step-by-step (methodically) thru this process, I'm confident you'll find the culprit.
 
As was mentioned, 'rogue' plugins are also common causes of problems.
 
Start simple, establish a base level of performance, and build from there...

Now there's a trouble shooting plan I could work with...

+1 - Move to Windows 7 64-bit. 

Annual XP install? What a waste of human life. 
Install W7. Get your drivers and primary apps installed and running. Then make a disc image of the fresh installation using the W7 backup utility. If you really, really, really feel the need, then reinstall your image once every year or so. Or not at all.  
Spend the time saved in the pub.

Annual XP Re-install?

I've been running with XP SP3 since 2007, without it needing a single re-install.

I'm not looking forward to doing it ONCE when I finally jump onto Windows 7

The new CPUs are not fully supported by XP now. So its not in the future its right now.

All are 64 bit that alone is reason to junk XP.

Bristol_Jonesey


Annual XP Re-install?

I've been running with XP SP3 since 2007, without it needing a single re-install.

I've seldom needed to do a reinstall, but I've never once regretted doing it. Unless you're very meticulous at keeping the register clean, vigilant when using the internet and conservative regarding what goes on your harddrive (I'm talking legal, unfilthy stuff here), chances are your PC could be running with just three cylinders.
 
That being said, I'm probably going W7 64 later this year.
Sven

@n0rd

Well - why should people not give the suggestion to upgrade to Windows 7? It might not be the only solution, or a solution at all, but I think they are allowed to give there opinion here. What is wrong with that?

And yes- Sonar X1 is supported on XP. But keep in mind Sonar is not the ONLY software running on the computer. Some plug-ins, drivers, and 3th-party software can be optimised for Windows 7 (and increasingly will be in the next future). Sonar uses and/or depends (in case of drivers etc.) on that software. If that software or drivers do not run stable on XP, it "pulls-down" Sonar too, and there is nothing Cakewalk can do about that...

So it's not the case X1 is supported on X1 soley. That's not the question. The question is if the complete environment X1 is running in (with all 3th party software in it) is stable in, or adapted to, XP.

That said - one of the suggestions was re-installing XP. As all XP users have learned, the brand new "fresh" install seems to suffer from increasing bit-rot after some time (just joking), and needs an "re-fresh-up" after a year or so. Also - older software that is installed and -after that- removed or modified can make your system "dirty", especially if it is a lot of it. It is fully possible that this is the case here.

Unfortunately a clean fresh install (if you do not have a image) is a lengthy process, because you have to do all updates from the latest fixed CD standard disc image. I think that are about 90 or more updates. However - it can be done.

However - If you are going to install XP "fresh", and you have hardware that is supporting Windows 7, why not take the "jump" to Windows 7? It takes far less time, and you are ensured your system will be supported by hardware and software suppliers. Do not forget XP is to be phased out (update-wise by Microsoft) around 2014.

Still - the choice is with the OP....

[Edit]

Sorry chaunceyc - I was typing this reply while you where posting your reply.

Sorry X1 did not worked out for you at this moment. Just take your time and when you have a new computer, you can take the jump. Do not forget - your 8.5 is still running file, end will be for some time. And the only thing I can say about pre-X1 projects. Most of them are loading fine on my system, and I only have to tweek some little things here and there. You will not be helped by this remark at this time, but I hope this will be encouraging to at least try X1 on a new computer (and maybe OS) some time.

[/Edit]