Helpful ReplyRE: SONAR 2016.03 build 71

Author
jb101
Max Output Level: -46 dBFS
  • Total Posts : 2946
  • Joined: 2011/12/04 05:26:10
  • Status: offline
2016/04/01 21:19:03 (permalink)

RE: SONAR 2016.03 build 71

Where is this?
 
Can't find it in CC and Noel's link in Problem Reports takes me to Forum Top enu.
 
Off to bed now (it's twenty past two), but will check in tomorrow.
 
Thanks in advance.

 Sonar Platinum
#1
scook
Forum Host
  • Total Posts : 24146
  • Joined: 2005/07/27 13:43:57
  • Location: TX
  • Status: offline
RE: SONAR 2016.03 build 71 2016/04/01 22:06:39 (permalink)
pretty sure Noel meant to link to http://forum.cakewalk.com/FindPost/3393487
build 71 just replaced build 70 as the early access version
#2
jb101
Max Output Level: -46 dBFS
  • Total Posts : 2946
  • Joined: 2011/12/04 05:26:10
  • Status: offline
RE: SONAR 2016.03 build 71 2016/04/02 05:29:01 (permalink)
Build 71 is now showing in the CC.  Itwasn't last night.
 
Thanks for your post, Scook.

 Sonar Platinum
#3
scook
Forum Host
  • Total Posts : 24146
  • Joined: 2005/07/27 13:43:57
  • Location: TX
  • Status: offline
RE: SONAR 2016.03 build 71 2016/04/02 05:46:45 (permalink) ☄ Helpfulby SteveStrummerUK 2016/04/02 09:40:27
When an update is announced but not visible in the Command Center, try clicking the "Check Now" button to the right of the "Min Update Interval" on the settings page.
#4
ChristopherM
Max Output Level: -56 dBFS
  • Total Posts : 1921
  • Joined: 2006/08/18 14:31:42
  • Location: UK
  • Status: offline
RE: SONAR 2016.03 build 71 2016/04/03 11:08:53 (permalink)
Given that 2016.03 is not yet available in the mainstream (and assuming that 03 is a reference to month three, which is now gone) am I the only one who thinks that Early Access is mis-named?
#5
stickman393
Max Output Level: -60 dBFS
  • Total Posts : 1528
  • Joined: 2003/11/07 18:35:26
  • Status: offline
RE: SONAR 2016.03 build 71 2016/04/03 12:24:30 (permalink) ☄ Helpfulby Vastman 2016/04/03 19:10:54
It is ironic that, having been "on time" or "early" with the district-named releases on a more or less monthly basis, the first time they change the naming convention to what appears to be "YYYY.MM" format, the release slips.
 
There is no reason why feature releases should auto-magically fall into a monthly release cycle, although I get why Cakewalk wants to have monthly releases, given the "subscription" model.
 
Let's just all agree that "2016.03" represents the third release in 2016; it will get here when it's ready; and move on.
 
I totally support Cakewalk's release name change... they were going to have to face this challenge at some point, and I've been using 2015.7 or whatever to refer to the releases for some time.
 
 
#6
Jump to:
© 2025 APG vNext Commercial Version 5.1