robert:
1.  Was Windows brought up to current maintenance levels prior to your installation of X2?  - I don't remember, probably not.
    
2.  Did you also download and install the X2a maintenance patch?  - yes

3.  If you DID install the X2a patch, did you then follow the instructions for re-scanning plugins and all of that? yes

yes I have service pak 1 now, not sure if I had when x2 & x2a were installed. I updated windows a few days ago. But I checked to see what updates were made, and I do have it.

Thanks  - I do not know the ramifications of installing Service Pack 1 AFTER installing the X2a patch.

I am hoping someone else out there can further guide the poster through this bit of a twist.

If nobody responds to shed further light on this, then you might consider doing a removal and re-installation of X2 and then X2a, now that you are patch current with Windows.  HOPEFULLY that will fix it all for you.  (perhaps though, this could be avoided by someone else from the forum community having a better understanding of the conditions as they are currently existing on your computer).

There are some threads out there with detailed instructions for complete removal of a given release of Sonar from a computer - there are Registry keys to delete, and some roaming data folders and such as well.

Here are the famous Britol_Jonesey removal instructions (I copied them out of a different thread):

1) Completely un-install SONAR from your computer. This is normally done from Start | Programs | Cakewalk. This will not remove any of your project files or audio data.    

2) Open the Run Command 
In Windows Vista and 7 this can be done by holding down the ‘windows’ key and pressing ‘r’    

3) At the prompt type regedit and click OK.   

 ***Backup your Registry before making edits - you do this by clicking the File menu, Export Registry File.   *** 
  
4) Now delete the following Registry keys:   
 HKEY_CURRENT_USER\Software\Cakewalk Music Software\SONAR Producer\X2 
 HKEY_LOCAL_MACHINE\Software\Cakewalk Music Software\SONAR Producer\X2    

NOTE  that this will remove any effects presets and key bindings you may have made in Cakewalk. You can back these up separately if you like, using Options|Key Bindings, Tools|SONAR Plug-in Manager, and Options|Colors. Hit F1 in these views for detailed instructions on how to do this.   

5) Open the 'Run' command again.   

6) Copy and paste the following into the prompt:   %appdata%\Cakewalk    

7) This will open your Cakewalk Application Data folder, right-click on the SONAR folder and choose rename.   


8) Rename this folder SONAR X2 Backup.  

9) Open the 'Run' command again and type msconfig Click OK and then click on the Startup tab at the upper right of the window that opens.  

10) Uncheck all items listed, click OK, then restart your computer. You can always recheck those items again at a later time.  

11) Then reinstall SONAR. Make sure to have any virus scanners disabled on installation. It is not required or recommended to turn off any windows services.  



I did NOT have anything to do with that choice of fonts, by the way :)

Bob Bone

As I posted earlier in the thread, since I did windows update, I have still experienced a couple of minor bugs (nothing that stopped me from working) but x2 has been working really good, I was suprised. LOL.  So now I am wondering if I just installed the service pack, unknowingly, I rescanned the vst, cuz i was trying to clean up my fx menu. Did both last friday. And I worked on it for about 16 hours sat & sun with only 2 issues, 1 I connected a usb drive in the middle of an export, so I believe that was my fault and the 2nd, I changed my asio buffer size and lost the audio ( i have a seperate post for this, not sure its a sonar issue or driver issue). a reboot and no more issues. I was really pleased with how well x2a was working, but then again its only been 2 days, so I am not going to claim success quite yet. :) hmmmmm.....
 
 
Also here is something I just realized. The projects I was working on this weekend were created in x2a recently, within the  month and last week. The projects that were really giving me greif were created in x1 and version 5. However I do have a project created in x2a which was also giving me greif. I will revist that project this week to see if I still experience issues. Anyone know of issues between projects created in differrent versions of sonar?  May be nothing, just coincidental.

 Not sure if you had a look at your IRQ's yet Tracy, but I was reading that FW cards with Ti chips are pretty finicky and pretty much need their own IRQ. I tried 3 Ti cards on my machine and couldn't get any of them to work without problems. Lucky for me I have no issues with my onboard VIA controller. 
 You can check your IRQ by running MSCONFIG by going to the tools tab> system information. Drop the HW resources tree and check out conflicts/sharing. If you think there may be a problem with it you can change the IRQ by trying a different slot if available. If you have an onboard 1394 controller that you are not using I would try that.
 
Glad the updates got you more stability
I do apologize for my bad behavior in this thread and I hope Alex accepts the apology I sent to him. My coffee pudding had a bit to much body that night.
 
 

ohgrant


 Not sure if you had a look at your IRQ's yet Tracy, but I was reading that FW cards with Ti chips are pretty finicky and pretty much need their own IRQ. I tried 3 Ti cards on my machine and couldn't get any of them to work without problems. Lucky for me I have no issues with my onboard VIA controller. 
 You can check your IRQ by running MSCONFIG by going to the tools tab> system information. Drop the HW resources tree and check out conflicts/sharing. If you think there may be a problem with it you can change the IRQ by trying a different slot if available. If you have an onboard 1394 controller that you are not using I would try that.
 
Glad the updates got you more stability
I do apologize for my bad behavior in this thread and I hope Alex accepts the apology I sent to him. My coffee pudding had a bit to much body that night.
 
 

Yes!!!!....this post is important...Thank you.
 
So go to the start menu..select accessories / select system tools/ system information...in the left pain of the now open window..select hardware resources/ sharing and conflicts....and look at your devices IRQs...You can copy and paste em up for a techie to look at.
Before doing any Bios flashing...see what is up with the IRQs....and then maybe it can be resolved...maybe.

ohgrant


 Not sure if you had a look at your IRQ's yet Tracy, but I was reading that FW cards with Ti chips are pretty finicky and pretty much need their own IRQ. I tried 3 Ti cards on my machine and couldn't get any of them to work without problems. Lucky for me I have no issues with my onboard VIA controller. 
 You can check your IRQ by running MSCONFIG by going to the tools tab> system information. Drop the HW resources tree and check out conflicts/sharing. If you think there may be a problem with it you can change the IRQ by trying a different slot if available. If you have an onboard 1394 controller that you are not using I would try that.
 
Glad the updates got you more stability
I do apologize for my bad behavior in this thread and I hope Alex accepts the apology I sent to him. My coffee pudding had a bit to much body that night.
 
 

+1 for that.


Yes thats a good point to bring up. I had a look in the mobo manual, where it said which slot to use for the Firewire card, one without any shared resources.

@TraceyStudios

Please do post back in a bit with an update on how it is all going for you - it is tentatively good that it is tentatively good - hopefully things will remain more stable.

Just a thought - I think I remember seeing that some folks had some issues opening older projects, due to plugins (might have been 32-bit, look-ahead buffering, that kind of stuff).  Perhaps you could try opening one of your problematic projects in Safe mode and not loading the plugins - then load them in one at a time to see if any of those are contributing to any weirdness.  And, if a 64-bit version of any of the plugs exists, try changing those from 32-bit to 64-bit and see if that helps too.

Certain plugins use something called look-ahead processing, or look-ahead buffering, and these can put the whammy on things, from what I understand, depending on how it is used in a project.  Perfect Space is one such plugin. 

For one of your problem projects, can you please detail which plugins are used, and whether or not they are 32 or 64 bit?  That may be helpful to know.

Bob Bone

Well, I have about 30 hours under my belt with almost no issues. I went back to the problematic projects and, still have a couple minor bugs, but sonar is working well.  As per the advise from this post, I did a windows update, made sure I had the correct drivers for my audio device. I did not do the bios update. I took a good look at the services running on the computer and disabled the obvious ones that I didn't need. (iTunes helper, etc). Verified I had the latest version: X2a. So I am please with how the program is running. I have an AMD machine, so it appears that they can run well.

Thanks all who  posted advise!!!

robert_e_bone

<snip>

One of the things it is important to note is that X2a requires at least a maintenance level of Service Pack 1 for Windows 7, for it to run properly.  This is due to certain C++ routines that are expected to be installed in Windows for running X2a, and those routines are part of that Service Pack 1 for Windows 7.

In any case, I hope things are working for you - I am curious on seeing your responses to the above questions,

Bob Bone

It appears your advice helped TraceyStudios, which is great.


Is the part about having Service Pack 1 for Windows 7 installed before installing X2 / patching to X2a documented by Cakewalk anywhere?