noynekker
Max Output Level: -66 dBFS
- Total Posts : 1235
- Joined: 2012/01/12 01:09:45
- Location: POCO, by the river, Canada
- Status: offline
The Mysterious Command Center Update
Today when I ran Sonar's Command Center, there was a message saying this version was no longer supported ?
So, of course I clicked to update it. Who want's to remain unsupported ?
It looks the same, tastes the same, acts the same, no email explanation, no blog mention.
I knew there was a murmur about an update coming, but do we get to know what actually is new about it ?
The only clue I found about this update was over on the cclarry forum (aka Software Forum), which was sarcastically entertaining, but everyone over there is also scratching their heads about this update as well.
Guess we'll have to wait until the "I" release next week to get the explanation.
Cakewalk by Bandlab, Cubase, RME Babyface Pro, Intel i7 3770K @3.5Ghz, Asus P8Z77-VPro/Thunderbolt, 32GB DDR3 RAM, GeForce GTX 660 Ti, 250 GB OS SSD, 2TB HDD samples, Win 10 Pro 64 bit, backed up by Macrium Reflect, Novation Impulse 61 Midi Key Controller, Tannoy Active Near Field Monitors, Guitars by Vantage, Gibson, Yamaki and Ovation.
|
teego
Max Output Level: -80 dBFS
- Total Posts : 518
- Joined: 2011/02/04 19:40:55
- Status: offline
Re: The Mysterious Command Center Update
2015/09/17 23:20:39
(permalink)
I just updated and the only difference I see is that I didn't have to tell it to check now, it did it automatically.
Computer: Intel core2 quad q8400 @2.66ghz, 4 gb memory,64 bit Windows 7 Focusrite Saffire Pro 24, Sonar Platinum Ipswich and Update 1
|
Anderton
Max Output Level: 0 dBFS
- Total Posts : 14070
- Joined: 2003/11/06 14:02:03
- Status: offline
Re: The Mysterious Command Center Update
2015/09/17 23:27:35
(permalink)
The differences are described in the next monthly eZine.
|
Re: The Mysterious Command Center Update
2015/09/18 11:19:51
(permalink)
Really small one, but here is the list. For bigger updates (like 1.1), we'll do a post in the F&I forum for feedback before development is finished. We're also working out where to put a C3 change log on our website as well for small changes like this. - Fixed a bug in check for updates interval. We also used to default to 24 hours, we now default to 0 so the user has to decide to change it if they don't want it to check every time on launch. This was causing a fair amount of confusion for first-time users.
- Custom VST3 paths have been removed. This was a VST3 faux-pas. VST3's belong in the common files directory.
- The right-click 'roll-back' menu now displays the friendly names instead of the version #'s. The idea is that this will make it easier in the future if we wanted to let folks 'roll-forward' to an update before QA totally passes it or if we need to put out an emergency hotfix that is available but doesn't advertise itself as 'the latest QA tested and approved update'
- A bunch of really boring behind-scenes schema, object storage and async stuff. These changes are what required us to make the update 'forced'. 1.0 and 1.1 for example were in the field side by side. With this update anyone running a version before 1.1.2 will be required to update.
|
noynekker
Max Output Level: -66 dBFS
- Total Posts : 1235
- Joined: 2012/01/12 01:09:45
- Location: POCO, by the river, Canada
- Status: offline
[SOLVED] The Mysterious Command Center Update
2015/09/18 21:37:51
(permalink)
Thanks for the response Willy . . . mystery solved, I had no idea Ipswich would be delivered the next morning ! It all makes sense now.
post edited by noynekker - 2015/09/18 21:50:47
Cakewalk by Bandlab, Cubase, RME Babyface Pro, Intel i7 3770K @3.5Ghz, Asus P8Z77-VPro/Thunderbolt, 32GB DDR3 RAM, GeForce GTX 660 Ti, 250 GB OS SSD, 2TB HDD samples, Win 10 Pro 64 bit, backed up by Macrium Reflect, Novation Impulse 61 Midi Key Controller, Tannoy Active Near Field Monitors, Guitars by Vantage, Gibson, Yamaki and Ovation.
|