Bristol_Jonesey

FastBikerBoy
As a NCFC fan I find the name offensive. 

I just knew you'd say this!!
 
Nice trip to Anfield lined up for Sunday?

I have a fiver says we're gonna win, does that count?

Just did a quick install and test on my laptop nstallation...

So far all is well...

Z-hold returns to smarttool as promised! <whew> Very grateful!

The one knob PC plugins do sound nice... I think these will be handy for lots of quickie things if not more...

As I do most of my synth/midi work with programmed movements or midi recorded envelopes. I don't personally have a need for the live v-synth recording. I freeze tracks as needed... ...and I don't have any problem doing this with external synths to begin with... So I haven't tried it... But nice to know its there...

I guess the same applies to the new clip export? I didn't look at it though I will... Eventually...

Thanks Bakers...

I look forward to the same clean/easy on my DAW later today....

Doktor Avalanche
Looks good. Nice fixes. Thanks.
 
Two disappointments..Both regression problems I believe.
No mention about the obvious start screen performance issues.
Keni's zoom bug still not fixed.
 
Of course I would not let a month go by without begging for a new drum maps UI.
 

I believe the update to the Drum Map UI is presently slated for the Yarmouth edition.
 

Tom Riggs
Sadly this update does not correct the problem with the new start screen being unable to find a project if there is an apostrophe in the file name.
 
Back to the bug report again. Unfortunately I use this character in file names often which makes the start screen useless for me.
 
Otherwise seems like a really good update.  

I would resave the project before saying it's still not working.  The names may not have been encoded properly for the Start Page in Hopkinton.  Ipswich was tested with many different languages, character sets, even Norwegian vowels.  We're now using W3C compliant code for the character encoding/decoding.
 
Keith

If I create a project (with a name like "I'll be darned") using the start screen it does open. Once it is saved it will no longer open from the start screen.
 
edit: this was just tested with IPswitch.
 
The error I get is that "d:\audio\cakewalk projects\I" was not found. So at this point it is evaluating the path to the file not just the file name.
 
Opening and saving the file in Ipswitch does not correct this issue.
 
edit2:
 
I renamed the folder that the project it in and now get the error that "d:\audio\cakewalk projects\ill be darned\i" can't be found.
 
And this is a file created using the start screen.
 
Edit3:
 
Ok. just for grins I disabled the firewall rule I have blocking sonar for internet access. I tested again and it indeed does open the projects and does not truncate the file name.
 
I am not inclined to leave the firewall rule turned off because it increases the start time of sonar from the 3-5 second range to 20-25 second range.
 
I hope this helps narrow down where the problem is.

Okay, I am totally baffled on the internet requirement to make the apostrophe work.

I figured the bug is in the new code in the start screen, not in the Internet data exchange per se.
 
Are you saying that if you unplug or disable the network, the Start Screen works with the apostrophe'd filenames?
 
If so, Huh.
 

it implies that the parsing is happening on the server rather than "in the start screen" - maybe it was a quicker/easier "fix" to do it there?

Love the realtime synth recording addition. I recorded over 48 addictive drums outputs from 3 instances in total, without a hitch (SSD). I love this, since I like to old skool cut and flip audio clips, over midi often. Performance seems superb.

stickman393
I figured the bug is in the new code in the start screen, not in the Internet data exchange per se.
 
Are you saying that if you unplug or disable the network, the Start Screen works with the apostrophe'd filenames?
 
If so, Huh.
 

Mattelus has it right except I don't unplug the cable I have a firewall rule that blocks the sonar executable from the internet. When access is blocked the new start screen will not open files that have the apostrophe in the path or file name. When the internet access is restored it works.
 
Just to test it I disabled my firewall rule and then disconnected the network cable and I get the same failure to open the file. Reconnect the network and it works again.
 
While I was looking at the firewall rules I noticed that there was a rule created to allow internet access to the start menu executable. Changing this rule to block access just makes the start menu fail completely with our without a network connection. I have set everything back to its initial state and the start menu works again. 
 
For performance reasons I prefer to have the internet access for sonar blocked.
 
So if there is no interest from cake to "FIX" this I will just have to disable the start menu completely as it is not useful to me in it's current state.

Did everyone get emails from Cakewalk announcing the update? I didn't (and yes I checked spam), although I'm a fully-paid up Platinum subscriber, and I know CW knows my email because I confirmed it with tech support by phone recently. I only heard about the update because I chanced to visit this forum. Seems subscribers should be notified, yeah?

I don't even use the start menu at all. I always have it disabled. When I click on the File dropdown it has all the latest projects listed and if I need to start a new one I just click "New".  Is there some advantage to the start menu I'm missing? I've been working this way in Sonar for about 8 years so the new start menu is a non-issure for me.

southpaw3473
I don't even use the start menu at all. I always have it disabled. When I click on the File dropdown it has all the latest projects listed and if I need to start a new one I just click "New".  Is there some advantage to the start menu I'm missing? I've been working this way in Sonar for about 8 years so the new start menu is a non-issure for me.

I'm with you... It's easier for me to simply see a list with no pictures and select from current projects... I see no value to the start screen for me. I don't want to automatically check for updates or spend time trying to make screenshots that might identify a song...?

Am I missing something? What is the benefit?

As to the apostrophe issue? I wonder... If you disable the update testing feature for the start screen, does that affect the outcome?

Paul P
The best solution seems to be to do something like a yearly update during which you learn all the new features and the new bugs and then go back to making music for another year.  Just like the old way of doing things.

 
You can do that with the present system; you choose when to update. The only potential difference is if you wait a year to update, more bugs will have been fixed because they would have been fixed shortly after their introduction, as opposed to being introduced all at once with a big update.
 

The current way is just alpha and beta testing.  Nothing wrong with that, if it was presented as such.

 
If you look at the bugs introduced each month and multiply by 12, I suspect you'd have about the same number of bugs introduced with a yearly update. However, bugs get fixed faster with the current model. What it really boils down to is whether you want immediate access to a feature like Drum Replacer or real-time synth recording, or are willing to wait for a period of time after it's introduced so that any bugs unearthed from heavy use are fixed. But, you have that choice, whereas you didn't before. 
 

I would like to add that for us regular forum participants all this is well known.  But think of a new hobbyist/musician/user who puchases SONAR.  I imagine many wouldn't even be aware that this forum exists, let alone the necessity to read it obsessively.

 
In theory, that's what the notifications option is about - to inform people of SONAR-specific things without requiring sending an email or going to the forum. But as to reading the forums obsessively, bear in mind that some of the issues found are a) pilot error or exposing a system incompatibility, and b) relevant only to specific situations. For example someone has posted that exports don't work post-Ipswich, yet I've done lots of exports, including the new multiple clips option, without problems. So reading the forum and finding out someone thinks there's a problem doesn't affect me.
 
A good example of a reproducible bug is the Arpeggiator not bouncing the arpeggiated notes. But I rarely use the arpeggiator, so by the time I do, it will probably be fixed. Meanwhile, there's the arpeggiator plug-in. Again, I wouldn't have known about this without reading the forum, but it wouldn't have mattered.
 
I don't think it's necessary to obsess about things. You download the update, you read about how to use the new features, done. If you encounter a deal-breaker problem, you roll back. Or, you just wait and update every few months or every year or whatever.
 
The new system is all about choices; if anyone wants the system to work as it did before, that's one of the choices. Perhaps Cakewalk's mistake in rolling out the membership thing was not offering only two options: get monthly updates, or buy a yearly version. That wouldn't have affected anything Cakewalk did, except that once a year they'd take the most recent download (which would contain all the features and bug fixes from the previous 12 months), give it a version number, and offer it for sale as "SONAR X4" or whatever. Basically it's the same thing as a current member downloading once a year instead of once a month, except that you'd pay at the end of the 12 months to get the updates that happened, instead of at the beginning to get the updates that will happen.
 

Adq
I think this update system is very good. And definitely more rare updates would be much worse. The only thing I see that could be added is more intensive beta-testing, but it could be a problem from business and marketing point of view.

More beta testing translates to longer release times...

I don't code anymore, but from my experience there will always be unexpected issues regardless of how much testing is performed... I think they're doing a great job keeping up with things (all considered)... New features are quickly fixed even if the implementation isn't optimized yet... We really have it pretty good right now and I'm hoping it continues and builds!

Not to say that we don't each have our pet issues... So there's always room for "improvement"...

It feels like I've got a staff constantly fixing and upgrading my studio while I stay focused on the use of the studio. There have always been limitations to get beyond and I suspect there always will be...? I don't ever remember feeling any studio was finished... Just ready for use...

I gotta admit as an old man in the music field, I never dreamed recording and "album" creation would ever be this easy and widespread... The cost of a roll of recording tape alone made the process expensive beyond even the cost of gear...

Just a few of my thoughts on this...