Ever since X3C whenever I open a project I get a message saying the Console Emulator is missing, the CLSID is wrong and that I need to replace it with one of the choices in the drop down menu directly below. In X3C I could choose the new option and the project would go ahead and load fine, no problem, so I went with it.
Now, using X3D, sometimes when I go through the same routine the project won't load and I get a shutdown and the problem reporter pops up. Very annoying.
Anybody else seeing this or do I need to do a reinstall or something?
 
I forgot to say that I did the plug in reset and rescan the was recommended.

Thought I'd try just one bump.
Nobody has any ideas?
As I said, I've done the whole "Reset, rescan" thing, so any ideas would be welcome.
Thanks.

Hi RS,
 
Check to see where your CE folder is installed. For me it resides in the following:
 
32 bit Sonar: C:\Program Files (x86)\Cakewalk\Shared Utilities\Internal/Console Emulator
 
64 bit: C:\Program Files\Cakewalk\Shared Utilities\Internal\Console Emulator
 
You should have two .dll's in each folder. If by chance you do not see these folders where I have them, search and see if by chance they were put somewhere else and then paste them to the directory(s) I have provided above.
 
Then, try doing a plug reset/rescan and see how you fair.
 
If you want, you can check to see if the internal path(s) I have listed are in your registry.
 
32 Bit Sonar: HKEY_CURRENT_USER/Software/Cakewalk Music Software/Sonar Producer/Cakewalk VST/VSTInternal Path
 
64 bit Sonar: HKEY_CURRENT_USER/Software/Cakewalk Music Software/Sonar Producer/Cakewalk VST X64/VSTInternal Path
 
You should see the folder references I've given you listed there. If they are not there, that's where the problem is. Or at least, that would be my best guess on where to start.
 
The only problem close to this that I've had was with the CA2A limiter being installed in a folder that wasn't being scanned. So I cut and pasted it into my Cakewalk directory where it should have gone. I'm thinking maybe something weird happened with your CE folder and it's not being seen or something.
 
Anyway, I hope some of this helps you get to the bottom of it. I'm not sure if you can just re-install the CE from the install program or not, but that may be something to consider also as it may have been a jacked install or update or something. I don't think this will be too hard to remedy though. Tech Support will probably sort it out in seconds if you can give them a call. Good luck....and let me know how you make out with this one.
 
-Danny

Hey Danny, thanks for the reply, I appreciate it.
In the 64 bit folder I have three dlls....
 
Console Channel_64.dll
Console Emulater Bus_64.dll
Console Emulater Channel_64.dll
 
I'm thinking that could be my problem. Do you think I would be safe deleting the first one? It's dated 9/12/2012, which I think would have been when I installed X2.
The others are dated 10/24/2013 which would have been when I installed X3

The Console Channel_64.dll is not in my CE directory. What I usually do, just to be safe, is rather than completely delete something; I move it to another directory, just in case I need to retrieve it. The plug-in would need to be moved to a directory out of the VST scan path. After moving or deleting the dll, take notice if the scanner indicates the plug-ins removal. If the scanner does not post a message about the removal, run the reset/rescan to force it to clean up the registry.

scook
The Console Channel_64.dll is not in my CE directory. What I usually do, just to be safe, is rather than completely delete something; I move it to another directory, just in case I need to retrieve it. The plug-in would need to be moved to a directory out of the VST scan path. After moving or deleting the dll, take notice if the scanner indicates the plug-ins removal. If the scanner does not post a message about the removal, run the reset/rescan to force it to clean up the registry.

RS, the above advice that scook gave is how I'd go about it. Cut and paste it somewhere else without totally deleting just in case. On my end I only see 2 in my folder but the main thing here is, you HAVE to see the internal folder being listed in your registry. It won't be a folder you have scan in your VST settings, but Sonar adds that internal folder to the reg upon installation. So if it's not in the registry, it won't see it.
 
In the event it's NOT in the registry (I had this problem one time now that I think of it and one of the bakers came to my aid) you could TRY adding the internal folder to your vst scan and once it recognizes it, remove the folder from the VST scan. I'll explain...
 
I had an issue like this and decided to point the internal folder to the vst scan. The baker that helped me told me that I shouldn't have done that and the internal folder should auto be recognized during the install and added to the registry where I showed you in my other post. For some reason, mine was not auto added but when I added the folder to my vst scan, it also added it to the registry. The baker told me to remove the folder from the vst scan. When I did that, the CE was still recognized because by then, it is my assumption that it got added to the registry.
 
Neither me nor the baker I worked with understood how this could happen, but that's how it went down and what fixed me. I'm not sure any of this will help you, but it may be something to at least try. Maybe see if anyone else chimes in before you try it though. It didn't hurt anything on my end though. :)

scook
What I usually do, just to be safe, is rather than completely delete something; I move it to another directory, just in case I need to retrieve it.

Sometimes just renaming something will cause it not to be recognized, like calling is XonsoleChannel.dll.

Anderton

scook
What I usually do, just to be safe, is rather than completely delete something; I move it to another directory, just in case I need to retrieve it.

Sometimes just renaming something will cause it not to be recognized, like calling is XonsoleChannel.dll.

I suppose that would work but if the problem persists, there would still need to physically move the file(s) to be sure, so why not move them first place? And in this case, there is a tool which scans and dives down directory structures so the files need to be moved out of the search path.

Danny, scook, and Craig,
Thanks so much for the help guys! I'll try moving the dll and see what happens. I'll let you know.
Thanks again, really appreciate it. It's guys like you that make this forum what it is.

That did it guys. I owe you one. If you're ever around here the beers are on me!