Tom & stevec, ok tnx, I leave it as it is for now... I hope there is a way to not have all versions, imagine after 12 updates later, ca 17GB on my c: drive, could be a diskspace issue on my laptop :)

btw, its orhan project, not orphan :)

Edit : With all versions, I mean all previous update versions installed, specially if all fututre updates will be that big its gonna eat my laptop c drive pretty fast

Just use the CCC to redirect (the little gear icon in the top right corner) where your files are downloaded so they aren't on your c: drive

mudgel
Just use the CCC to redirect (the little gear icon in the top right corner) where your files are downloaded so they aren't on your c: drive

Im talking about the installed updates, not install files, those I keep on external drive

stevec

Tom Riggs
OrphanProject I would not uninstall anything listed as "Sonar Platinum"!!!!!!!

+1   Those two entries are likely two versions of SPlat, allowing rollback from the current to the previous version.

this is the kind of question that really needs clarification from a baker...

Orphanproject You will find that the size of the program is not the cumulative size of what is reported in the windows programs control panel.
 
Each install shares files or replaces them from the previous update. This is why you should not uninstall the previous versions.

Tom Riggs
Orphanproject You will find that the size of the program is not the cumulative size of what is reported in the windows programs control panel.
 
Each install shares files or replaces them from the previous update. This is why you should not uninstall the previous versions.

Ok Thom, tnx :)

Ok There seems to be a serious bug with one of the encoder formats. This just started after I installed the Cambridge update. When I export to wav 16 bit and I choose WAV (microsoft) I generally get another window that pops up and says that it will encode in microsoft 16bit. Now with Cambridge that window is gone and when it is done encoding I get this error message
 
Warning:The External Encoder returned an error code. The file may not have encoded properly
 
When I look for the file it is not even there which tells me it did not finish the encoding process. Another error is happening too. When I hit the export button the directory that I want the file to go into goes into a random sub folder for some reason. I hit export again and then the file starts and gets to the end then throws up that error message. It does not create a sub folder it just goes into an existing one.
 
So in conclusion The WAV (microsoft) encoder no longer works on my machine. It worked fine before I installed Cambridge. I used it a day before the Cambridge install with no problems
 
The real problem for me is this encoder is the only one I use. If it does not work for me then Sonar has lost its use for me. Is there anyway to roll back on an install without uninstalling the entire program and re-installing again? Even if I did uninstal how could I avoid installing the Cambridge addition?
 
What is the difference between the WAV (microsoft) Export and the WAVEX (microsoft) export? That is something new that was not there before. Is that conflicting with the 16 bit WAV (microsoft) export format?
 
Any help would be appreciated. I have projects ready to export and this conflict is holding up the process. 

I can confirm the issue with the "Microsoft WAV" export. However, the main WAV export (the top item on the export list) works fine.
 
I usually don't export as WAV anyway but as Broadcast WAV. Broadcast WAV has the advantage of being fully compatible with WAV files but includes additional time-stamping information that places the file at the timestamp where it was recorded. (If you don't want this, you can choose to have SONAR ignore time-stamping during import.) Media players and similar devices ignore time-stamping anyway but with projects, time-stamped files can make life much easier.
 
WaveX is a wav extension that as far as I know is used mostly for surround projects and wouldn't apply to what you're doing.
 
 

There is not much reason to use the Microsoft Wave option. In fact we thought of removing the option to avoid confusion. SONAR's normal Export to wave function writes the same format and is actually more powerful since it will handle auto switching to wave64 when the file is too big. I think the only difference is that the MS format will write 24 bit waves as Waveformat extensible.
 
I'll look into why the encoder is failing if the problem is on our end.

OK you can fix this problem yourself :) 
 
Open C:\ProgramData\Cakewalk\SONAR Platinum\libsndfile-exclude.txt


You will see two lines formatted like this:
 
AIFF (Apple/SGI)|IMA ADPCM
W64 (SoundFoundry WAVE 64)|IMA ADPCM|Microsoft ADPCM
 
Just change them as below by adding a # and resave the file:
 
#AIFF (Apple/SGI)|IMA ADPCM
#W64 (SoundFoundry WAVE 64)|IMA ADPCM|Microsoft ADPCM
 
This should fix your problem. The issue is that we shouldn't be counting excluded subformats. Commenting out the line will fix it for now. In the next update I'll address the counting issue.