cool...

I think we all need to read a lot in the 3000 pages PDF manual to get the full potential out of Sonar X1 ....



...no kidding on that one...

I never had the path to the "Internal" folder in the VST Scanner path listed in Plugin Manager > VST configuration > Options. Never having seen it I didn't know it was missing.

 
That implies that this key was missing on your setup:
HKEY_CURRENT_USER\Software\Cakewalk Music Software\SONAR Producer\Cakewalk VST X64\VSTInternalPath
 
That key is copied from a similar location under HKEY_LOCAL_MACHINE which is placed there by the installer itself.
 
The reason your problem could happen is if somehow SONAR's personalization didn't go through, or you had some anti-spyway type app that prevented a registry key from being written. It could also be caused by a failure to write a registry key for some reason on your system. Its rare but it can happen and if so that would be caused by a system failure not a bug in the installer or SONAR.
If that was the case, normally doing a "restore load" of SONAR by holding down the shift key while launching SONAR would restore that HKEY_CURRENT_USER key and fix your problem.
 
Finally the only other possibility is that the installer itself was unable to write the key:
HKEY_LOCAL_MACHINE\SOFTWARE\Cakewalk Music Software\Sonar Producer\Cakewalk VST\VSTInternalPath
If that happened the restore load step above wouldn't help. The solution for that other than a reinstall would be to add that HKEY_LOCAL_MACHINE key manually.
 
I'll ask TS to add a knowledge base article for this in case someone else runs into it. Either way if someone knows a deterministic way to run into this problem please let us know.
 

Noel Borthwick [Cakewalk
]

can't wrap my mind around why Cakewalk made it like this, but I bet theirs some significance to it.

 
Think of the pro channel as an entire effects bin containing the PC components. The "pre" setting places the entire PC bin in series BEFORE the user effects bin. The "post" setting places the entire PC bin in series AFTER the user effects bin.

Hi Noel:

That's exactly what I was trying to say in my post above. Thanks for clearing that up for me in such a concise comment. :)

Noel Borthwick [Cakewalk
]

I never had the path to the "Internal" folder in the VST Scanner path listed in Plugin Manager > VST configuration > Options. Never having seen it I didn't know it was missing.

 
That implies that this key was missing on your setup:
HKEY_CURRENT_USER\Software\Cakewalk Music Software\SONAR Producer\Cakewalk VST X64\VSTInternalPath
 
That key is copied from a similar location under HKEY_LOCAL_MACHINE which is placed there by the installer itself.
 
The reason your problem could happen is if somehow SONAR's personalization didn't go through, or you had some anti-spyway type app that prevented a registry key from being written. It could also be caused by a failure to write a registry key for some reason on your system. Its rare but it can happen and if so that would be caused by a system failure not a bug in the installer or SONAR.
If that was the case, normally doing a "restore load" of SONAR by holding down the shift key while launching SONAR would restore that HKEY_CURRENT_USER key and fix your problem.
 
Finally the only other possibility is that the installer itself was unable to write the key:
HKEY_LOCAL_MACHINE\SOFTWARE\Cakewalk Music Software\Sonar Producer\Cakewalk VST\VSTInternalPath
If that happened the restore load step above wouldn't help. The solution for that other than a reinstall would be to add that HKEY_LOCAL_MACHINE key manually.
 
I'll ask TS to add a knowledge base article for this in case someone else runs into it. Either way if someone knows a deterministic way to run into this problem please let us know.
 

On my last install where I achieved success in getting everything to install properly I did go into msconfig and disable all sorts of unecessary services to stop. I've found in the past that just disabling things like anti virus software still leaves some behind the scenes services running. Because of the problems I had with the first 2 installations I wanted to make absolutely sure that nothing got in the way.
 
I think there must have been some other unidentified issues created during the installation because of something particular to my environment, that contributed to the other multiple "bugs" evident in X1 all along - until this last reinstallation.
 
It does seem to go back to some glitch during the install process that was not unique to my system because others also reported the same ProChannel symptoms with widespread evidence of the reported bugs being evident on their systems. Perhaps it was as simple as an anti virus program being closed down but still having a service of some sort running in the back ground causing the installer to miss writing some of the necessary registry keys. Mind you this is just conjecture based on Noel's post.
 
Man I hope this helps someone else.

Thanks for the tip.
I built this PC (recommended parts list from Jim roseberry of Studiocat) at the time that VISTA SP2 was coming out. I did a dual boot with WIN XP SP3 x86 buit ended up never going back to XP because my VISTA  x64 experience was so great.

When X1 came out I changed the XP partition over to WIN 7 but didn't use it because all the X1 issues I had didn't seem to make it a worthwhile exercise at that time.

Now that I seem to have uncovered some basic reasons why my X1 problems had been so severe I'm ready to give it a go. Now it's just finding the consistent time to do it in my very own obsessive way.

My current DAW is so stable that X1 has stiff competition to get into my toolbox.