So I suppose there's no problem if you never got around to installing Braintree, right?  Updates are cumulative?  I can't afford the bandwidth to update every month with my studio's cell phone G3 network, by the end of the year my $99 version of Professional would have cost me another $200. So I will download this update off site and see if that works this time. 

Anderton
Just curious, though...if you install manually and are not using the CCC to install files, does it really matter what the CCC shows? If each release shows which elements to download for the release, then you'll know what needs to be installed.

That's good to know.  Where exactly do I find that info?

After I got rid of IObit Ulitmate as a virus program - and other stuff - I'm now able to update Plt via CC...so it's starting to get cool now and my confidence with Plt's stability is increasing. Nice one;

Are we going to have to do a VST reset for every release?
Some of us like to rename the NI VSTs so we know what they are (default, 8 out, 16 out). Forcing a VST reset for every release is a PITA.

scook
Run a VST reset for the 32bit version of Cambridge.

Renaming plug-ins using the Plug-in manager has not been recommended for this very reason. There may come a time when renaming is handled differently but resets have become more common starting with X3. For now, consider using custom plug-in layouts or change the VSTPlugInNameFormat value in Cakewalk.ini http://www.cakewalk.com/Documentation?product=SONAR&language=3&help=INI_Files.4.html. Otherwise, I suppose one could create a .reg file to merge after every reset.
 

Anderton

mettelus
The CCC still needs love (particularly to manually installed products). Installing manually and then running CCC merely changed SONAR status from Green to Yellow. All others remained red from manual install previously. This will get out of hand rapidly in coming months.

Just curious, though...if you install manually and are not using the CCC to install files, does it really matter what the CCC shows? If each release shows which elements to download for the release, then you'll know what needs to be installed.

The real issue with this is that the CCC should be an accurate visual indicator of what it loaded on a computer. Pretty straightforward. The onus for this should not go onto the users to do what CCC should be doing on its own. Another concern this opens is that most customers do not frequent this forum, so updates/issues are apt to be identified/addressed via the CCC (only). The CCC is sort of the "front end" to SONAR now, so should be an impeccable utility, yet I just spent my time with "Cambridge" editing XML files to tell CCC what is should already know (i.e. zero work in SONAR this evening other than X3e).

Ok, so there is a complicated workaround, maybe. The problem is, it should just work, period. Software vendors cannot rely on their users being gurus in either their applications or the operating systems they run on. It's not a user issue, it's a vendor issue. Sorry, I don't buy into the notion that everyone has to be an expert to get something to work correctly. Why should anyone need to know how to register anything or fiddle with VSTPluginNameFormat in cakewalk.ini? Yeah, we're all idiots, but knowing that doesn't really help us much. After years of working with Sonar, I know enough about all the fiddly bits to be dangerous, in other environments things just work.

scook
Renaming plug-ins using the Plug-in manager has not been recommended for this very reason. There may come a time when renaming is handled differently but resets have become more common starting with X3. For now, consider using custom plug-in layouts or change the VSTPlugInNameFormat value in Cakewalk.ini http://www.cakewalk.com/Documentation?product=SONAR&language=3&help=INI_Files.4.html. Otherwise, I suppose one could create a .reg file to merge after every reset.
 

Hi Gang!

I'm downloading from my online account, not CCC...

OK... I managed to download Cambridge, but mine was described as 21.2.xxx? I can't try running it until tomorrow... Will this need to be re activated even though I've got the full year paid for? Issues with getting that machine online...

But i am not finding the Les Paul Goltop.. I clicked on the Anderson Collection. It doesn't mention it and shows as 1.0.13 or some such... Is this what I must get? Must I download the the entire collection to get the addition?

Same with the Boz (sp?) pan device for PC. No mention of it when I click on the collection icon.. It generates a download link for another 1.0.13 type of version number and no mention of the pan device... Sorry, senior moment I'm forgetting the names and numbers right now and don't have access tonight anymore... ;-)

Keni

TomHelvey
Why should anyone need to
.....

fiddle with VSTPluginNameFormat in cakewalk.ini? Yeah, we're all idiots, but knowing that doesn't really help us much.

..
because it's the perfect one time solution that actually works. If easy solutions aren't helpful to you maybe try acupuncture?

TomHelvey
Ok, so there is a complicated workaround, maybe. The problem is, it should just work, period. Software vendors cannot rely on their users being gurus in either their applications or the operating systems they run on. It's not a user issue, it's a vendor issue. Sorry, I don't buy into the notion that everyone has to be an expert to get something to work correctly. Why should anyone need to know how to register anything or fiddle with VSTPluginNameFormat in cakewalk.ini? Yeah, we're all idiots, but knowing that doesn't really help us much. After years of working with Sonar, I know enough about all the fiddly bits to be dangerous, in other environments things just work.

I did not realize this

TomHelvey
Are we going to have to do a VST reset for every release?
Some of us like to rename the NI VSTs so we know what they are (default, 8 out, 16 out). Forcing a VST reset for every release is a PITA.

was a rhetorical question. I now know better. Although, I would think changing a config parameter is not that complicated but everyone has their own idea of what is complex.