I'm experiencing the following issues, and would appreciate any assistance resolving them:
 
1. When attempting to export tracks from Sonar, not all the selected tracks actually get exported. Or perhaps a portion of some selected tracks gets exported. I'm making sure to say "selected" because yes, I have checked to make sure the tracks in question were selected for export. I posted re this problem in an earlier thread, but the issue is intermittently on-going.
 
2. "The required parameters were not supplied." I get this message intermittently upon trying to open Sonar. I read about this in another thread, and the suggested solution was to update all C++ files. I contacted tech support, and they sent me links and instructions to facilitate this. I followed the instructions, but the problem still happens. It might take me 1-3 failed attempts before I succeed in actually opening the program.
 
3. Occasionally Sonar hangs, and although I can then exit the program, the .exe file still shows in the Task Manager, so can't simply restart the program. I then need to shut down and restart the computer. Major crimp in the workflow.
 
4. I have Melodyne Editor, but sometimes Melodyne doesn't allow me to access the additional features which Editor is supposed to provide in addition to those offered in the basic version of Melodyne which comes bundled with Sonar Producer. So for example, when the problem occurs I can't access the polyphonic algorithm. Clips I previously worked (Region Effect clips) on will be greyed out and inaccessible. Then I exit Sonar and re-open, and if I'm lucky, Melodyne will once again be fully functional. This problem has been happening on and off for quite a while. I did re-install Melodyne Editor a while back, to no avail. Also, for some reason almost every time I open Sonar, Melodyne finds it necessary to tell me that Melodyne Editor is registered and active. This doesn't really bother me, but I do wonder if it might be indicative of or somehow related to the problem I'm experiencing.
 
5. Universal Audio: I have a core duo card, and use various UA plug-ins. On my most recent project I got the following message upon export: "The requested buffer size 2048 did not match the other plug-ins. The expected buffer size is 1024." It then goes on the tell me that the buffers should all be the same size for optimal performance. Fine, but what does this mean in practical terms, and how can I resolve this issue? The export still proceeds, but I wonder if the resulting file might be somehow lower quality than it could have been.
 
Thank you.
 
 
 
 

The problems you're experiencing are unusual. I suspect some, if not all, trace back to the problem in (2), which seems like it might be a Windows-related issue. Tracking those kinds of things down can be frustrating...
 
If you have a Creation Station, perhaps Sweetwater could do a remote desktop checkup for you. If not, I know Obedia can (obedia.com), and I have yet to encounter a problem they can't fix. They charge, though, so it might be worth exhausting your Cakewalk and Sweetwater options first.
 
Regarding (2), did you re-install SONAR after getting the C++ libraries squared away? That might help. Aside from that, I'll let the Windows experts take over.
 
One last thought: if you have Windows 7, presumably the installation is several years old. In many cases similar to yours, where there are unexplainable, intractable problems, people have done clean OS and program installs, and reported major performance improvements in addition to fixing the original issue.

I did not re-install Sonar after updating the C++ libraries. I guess I'll try that tonight.
 
Sweetwater tech support, here I come.
 
Thanks for your help, and for clueing me into obedia.com. That would be my last resort, but I don't mind paying if the end result justifies the expense.

Cakewalk will take your call too.

scook
Cakewalk will take your call too.

True. The OP mentioned Cakewalk sending links. Sometimes a phone call is better because support can ask follow-up questions.

Software troubleshooting guide, in order
 
1. Call mfg tech support
2. go to mfg forum/faq/knowledge base
3. search related forums
4. search wider internet
IMO

Problem 1:  Hit Ctrl-All before you export.  If you don't want some tracks included in the export, click on those tracks while holding down Control key.
 
Problems 2 and 3:   Something is rotten in Denmark. 

• Open an "elevated" MS-DOS command prompt (open as Administrator), and type "sfc /verifyonly", and hit return.  This will look for corrupt files.  If you run "sfc /scannow" it will fix any files that are screwed up PROVIDED it can find un-screwed up replacements.  That is why you run it in /verifyonly mode, because you may or may not have to run down those files.  Prayer seems to work.
• Download and run LookinmyPC.  Look for something running that is using a lot of cpu and/or something you don't know what it is.  You can click on the highlighted process name and be taken to an internet page is that tells you what purpose (if any) that process has being on your machine.  Backup and delete those processes.
• Hit Ctrl-Alt-Delete and run Task Manager.  Write down all the suspicious processes that might still be there, and find out what they are, and a good reason not to delete them from the Control Panel.
• With proper caution, as in save a copy of your registry before you decimate it, and download and run Ccleaner and see what it finds in your registry.  There may be crap in there from when you went to those porn sites.  I've always let it get rid of everything it finds, but I also make an Acronis image prior to doing any of this stuff.  The Windows "create system disk" can also be used, as long as you restore the image to the same size drive. 

Problems 4 and 5:  I have a little icon in my tray that allows me to set buffer size OUTSIDE of Sonar.  I then make sure that WITHIN Sonar the same buffer size is being used.  Hit P to check.  I don't know if that is required or not, but it's what I do, man.  When I am tracking I set both to 128, when mixing to 1024.
 

Thanks to all who offered suggestions, but it appears the cure was the very simple one recommended by Cakewalk tech support...uninstall/re-install Sonar. At least that's my preliminary assessment, since the aforementioned problems seem to have vanished one and all.
 
I think updating the C++ files was only the first half of the solution. I needed to then re-install Sonar to make it fire on all cylinders.
 
Cakewalk Command Center makes it incredibly easy to uninstall and re-install Sonar. Many thanks to the bakers for that.
 
I'll refer back to your suggestions if the problems return...after trying another re-install.
 
 

Hangdog Cat
Thanks to all who offered suggestions, but it appears the cure was the very simple one recommended by Cakewalk tech support...uninstall/re-install Sonar. At least that's my preliminary assessment, since the aforementioned problems seem to have vanished one and all.

 
Interesting...you mentioned only that they'd suggested dealing with the libraries, which is why I said "Regarding (2), did you re-install SONAR after getting the C++ libraries squared away? That might help." My hunch was that SONAR wouldn't install properly if there were other system problems. In any event, glad you got it sorted out.
 

And you were right.
 
I'm going to sit in the corner and say that 100 times.
 
Thanks for your help. It's nice to have knowledgeable, friendly people on this forum.