pwalpwal
so are we seeing a new pattern - monthly releases with intra-monthly patches/bug-fixes? i'm not sure i could keep up with that!

It's really not that hard...    Well, at least some of us like it! 
 
Hey, since it was mentioned previously in a few other posts, isn't this sorta/kinda the methodology "R" follows? 

Attempted to install the updated Splat file:
 
This program can't start because TTSlame.dll is missing from you computer.
 
Guidance, please.

stevec

pwalpwal
so are we seeing a new pattern - monthly releases with intra-monthly patches/bug-fixes? i'm not sure i could keep up with that!

It's really not that hard...

for me it's more about having the time to check stuff out, or learn new features, but then i suppose one doesn't have to install/update the moment new stuff is released

Yes, no problem

Thanks for your response.
 
Traditionally, I have installed ALL sonar versions into folders on the C: disk: C:\Sonar6, C:\SonarX3,...
 
I thought the CCC would obey the established paths.
 
But, I installed all CCC items as the CCC wanted.
 
The registry should be listing where Sonar2015 is.
 
So, why am I getting the error?
 
 

@cparmerlee exactly.. Assuming it continues this way.

YouDontHasToCallMeJohnson
Thanks for your response.
 
Traditionally, I have installed ALL sonar versions into folders on the C: disk: C:\Sonar6, C:\SonarX3,...
 
I thought the CCC would obey the established paths.
 
But, I installed all CCC items as the CCC wanted.
 
The registry should be listing where Sonar2015 is.
 
So, why am I getting the error?
 
 

Are you saying you got this error after updating to Foxboro using CCC? If so, then I have no idea what the problem is.
 
I thought you had updated by copying the interim fix to your computer and I was just suggesting, as the post I found in my search, that perhaps you did not put it in the right place. Maybe you did. In which case, I don't know.
 
Sorry I could not be of more help.

Doktor Avalanche
I've switched to the intermediate release cycle rather than install straght away so it doesn't bother me. If this becomes a regular thing and all the serious release issues get addressed by an intermediate release then then no problems whatsoever..! Happy for all you guys to do the testing!

jb101
A genuine question, Alex:
 
Why are you so hot on updating everything to the latest version - drivers, BIOS, NI updates (even though the update states that it is only aimed at certain issues that do not affect you),  et al.- , but warn against updating to the latest version of Sonar?
 
Maybe I am missing something.

 
Where exactly am I warning people not to download the latest version of Sonar? Quote please...
If there are stability updates I always prefer wait for the stability versions to come out which counteract regression issues in regards to Sonar.


You are assuming I treat all software the same..  wrong... !
 
Note Sonar is on a completely different software development path than all the other products you mention (monthly cycle), it's also clear Cakewalk is relying more on the community feedback and the software still needs to mature more. If BIOS software for instance was going under a similar sort of development methodology I'd be the first not to recommend. BIOS software does not come out every day. I also would never recommend installing any beta software either. I am not running Windows 10 and I certainly will not be installing it until for several months because it's likely to have issues for several months after release regardless (has always been the same).
 
When I recommend people to update to the latest is when I and others are troubleshooting issues.
 
Troubleshooting is generally much easier when people are running on the latest platforms, it's easier to compare notes. Often updating a product straight away resolves issues. Not convinced? Click here.
 
Developers and QA often develop on the latest Windows platform for instance. It makes sense you are running a similar platform that they are using. Software also has dependencies, it is far more likely old software integrating with new software is going to have issues, than new software integrating with new software. I'd write more here but that will be another large post.
 
> NI updates (even though the update states that it is only aimed at certain issues that do not affect you)
 
Err wrong.. You are obviously talking about Replika and clearly didn't read the thread correctly, in that instance I was helping other people (as well as myself) roll back a dodgy update. There's also a Maschine issue I'm currently trying to get to the bottom of it but it looks like a flat out bug (difficult to see if it's Sonar or NI at fault).
 
If an update makes things worse, you can always rollback or restore from backups. If you don't update you will never know if it resolves your issue or not.
 
I write this all in the context of troubleshooting... Please don't mix that up with updating routinely through a monthly development cycle. The one thing I would definitely recommending updating every month is Windows Update, they seem to have their QA in the bag. If they don't you can rollback. The benefits outweigh the risks. 

John
Alex you can rollback with Sonar too. 

Yup you can...  It is NOT risky to update Sonar esp if you make sure to set a restore point and backup first.
 
As I said I'm not telling people they shouldn't download the latest update of Sonar. People should make their own choice.
 
Personally I prefer to monitor the forums and see the feedback first before I install it and wait stability updates to become available..  Nobody can say there hasn't been any issues can they? And like I said earlier, I'm very happy just to wait for stability fixes myself as long as I know they are coming.
 
Comparing Sonar to Windows Update, drivers, NI or BIOS release cycles really is a huge generalisation. They all operate on quite different development release cycles. Again I would talk about this in more detail but I suspect people will go to sleep...

Thanks!!!!
 
Take tomorrow off, you've earned a long weekend.

Hey super thanks Noel.  This interaction with you guys is really cool.  I like this business model.  I hope it works and is profitable for a long, long time.

cparmerlee

Doktor Avalanche
I'll post here and warn people as well. After you update CCC make sure you double check your file path settings as a precaution . Ta.

Is there an update to CCC?  I haven't seen that announced anywhere.  I thought that was coming AFTER all the individual product installers had themselves been through an update cycle.

The individual product updates for compatibility with the new CCC happened with Foxboro. That was the reason for needing to do so many downloads.

cparmerlee
But is the new CCC released?  How do I get it?

Hi Craig-
 
Yes, it's released. When I ran CCC just now it said there was a new version and asked if I wanted to download/install it.
 
-Susan