• SONAR
  • Cakewalk Announcement (p.172)
2018/01/12 23:03:44
CakeAlexSHere
Funny when things go wrong there is almost always nothing or nobody to point to for being "responsible".. Or maybe it's right in front of our noses but it's too politically sensitive. Not that it ultimately matters in the end... for Sonar. I hope other DAW companies make Sonar a case study on what not to do.
2018/01/12 23:15:41
sharke
Grem
I was finding that towards the end of Sonar development, the older, longer, and more complicated a project got, the more weird things went wrong. And went wrong that could not be fixed. No work around. Project was either scrapped, or started over again.


This was absolutely my experience as well, and I too had to scrap and reconstruct numerous projects that had become too problematic.

Noel earlier said that this absolutely wasn't the case and that my problems were caused by plugins, but the weirdness I experienced had nothing to do with plugins. Crashes and hangs weren't the problem (although I certainly have my fair share of those) - it was always stuff to do with Sonar itself. Things like MIDI ending up in places it wasn't supposed to reach, automation acting weirdly (or sometimes disappearing for no reason), editing functions behaving strangely etc. The problem I have with plugins not saving their settings only happens in projects after I've worked on them for some time. Sometimes I will attempt to automate a plugin that I have in a ProChannel FX chain and I'll click on the edit filter to find that the plugins aren't even showing in it. And I also end up with phantom nodes in weird places like 5 minutes after the end of the song, which means "fit project to screen" will include 5 minutes of blank space at the end. And I cannot find these nodes anywhere to delete them. It gets to the point where working on such projects is such a PITA that I can't face them. I have numerous huge projects that I've been fiddling with on and off for years and am nowhere near completing them because I can only stand 10-15 minutes of dealing with the weirdness before I get sick of it.
2018/01/12 23:18:16
Anderton
Earwax
iRelevant
Software is immortal. It's only users, programmers, management and owners that die. Sonar will "live" forever.
 
I'm surprised how hard some people here are on Gibson, when gratefulness would be more appropriate. 
It's thanks to Gibson, which at a financial loss; have provided us with the latest version of Sonar. A great work of art.
 
It seems there is truth in the old saying : "Ungratefulness is the salary of the world". 




Bingo!! Nice to see someone (besides Craig Anderton) view Gibson's place in this with a clear head.

 
I'm just trying to be objective. I do think Gibson could have handled it better in terms of getting the word out, and I would be surprised if in retrospect, people at Gibson itself didn't agree. But if it hadn't been for Gibson, it's almost certain that Cakewalk would not have had four additional years to try and get it right.
 
2018/01/12 23:20:02
Anderton
sharke
And I also end up with phantom nodes in weird places like 5 minutes after the end of the song, which means "fit project to screen" will include 5 minutes of blank space at the end. And I cannot find these nodes anywhere to delete them. 



FWIW I haven't experienced this problem since using Ripple Editing to delete everything past the end of the project.
2018/01/12 23:40:49
CakeAlexSHere
Yes a lot of people from Gibson could have handled it a lot better. Of course I'm just trying to be objective...
2018/01/13 01:58:44
sharke
Anderton
sharke
And I also end up with phantom nodes in weird places like 5 minutes after the end of the song, which means "fit project to screen" will include 5 minutes of blank space at the end. And I cannot find these nodes anywhere to delete them. 



FWIW I haven't experienced this problem since using Ripple Editing to delete everything past the end of the project.




Good idea, I hadn't thought of that!
2018/01/13 02:42:24
michael diemer
sharke
Grem
I was finding that towards the end of Sonar development, the older, longer, and more complicated a project got, the more weird things went wrong. And went wrong that could not be fixed. No work around. Project was either scrapped, or started over again.


This was absolutely my experience as well, and I too had to scrap and reconstruct numerous projects that had become too problematic.

Noel earlier said that this absolutely wasn't the case and that my problems were caused by plugins, but the weirdness I experienced had nothing to do with plugins. Crashes and hangs weren't the problem (although I certainly have my fair share of those) - it was always stuff to do with Sonar itself. Things like MIDI ending up in places it wasn't supposed to reach, automation acting weirdly (or sometimes disappearing for no reason), editing functions behaving strangely etc. The problem I have with plugins not saving their settings only happens in projects after I've worked on them for some time. Sometimes I will attempt to automate a plugin that I have in a ProChannel FX chain and I'll click on the edit filter to find that the plugins aren't even showing in it. And I also end up with phantom nodes in weird places like 5 minutes after the end of the song, which means "fit project to screen" will include 5 minutes of blank space at the end. And I cannot find these nodes anywhere to delete them. It gets to the point where working on such projects is such a PITA that I can't face them. I have numerous huge projects that I've been fiddling with on and off for years and am nowhere near completing them because I can only stand 10-15 minutes of dealing with the weirdness before I get sick of it.

For what it's worth, weird things were happening to my Reaper projects, toward the end, just like you had in Sonar. It would kick back to the beginning every time I copied something. Also there were other things, some of which cost me days to fix. 
 
Still, Reaper is a fine program. It may be that these problems only happen with long projects (over 5 minutes), but all my projects are long. I'm working faster now that I'm back in Sonar. Takeaway? All programs have bugs and weirdness. The hit or miss nature of some of them may be due to an unusual workflow, idiosyncratic ways of doing things that the developers did not anticipate. 
2018/01/13 03:11:33
CakeAlexSHere
michael diemer

For what it's worth, weird things were happening to my Reaper projects, toward the end, just like you had in Sonar. It would kick back to the beginning every time I copied something. Also there were other things, some of which cost me days to fix. 
 
Still, Reaper is a fine program. It may be that these problems only happen with long projects (over 5 minutes), but all my projects are long. I'm working faster now that I'm back in Sonar. Takeaway? All programs have bugs and weirdness. The hit or miss nature of some of them may be due to an unusual workflow, idiosyncratic ways of doing things that the developers did not anticipate. 



^^ These sort of statements are exactly what make Sonar what it is today... the DAW Sonar fans deserve, accepting everything coming to them.

I have Studio One now and luckly I don't have to worry much about these sort of bugs any more. If they do happen (because as many say over and over again like a parrot in these forums that all software has bugs in a bid to make it acceptable over and over and over again for years and years like repeating passages from religious texts) I have no doubt whatsoever the bugs will be fixed in S1 far faster than when Sonar was in development. Regardless no bugs will be fixed in Sonar now as it's not in development. Bye for now.
2018/01/13 04:18:58
EnriqueLab
Paso por mi cabeza algo realmente enfermo... ¿y si google adquiriera Sonar?
 

Something really sick is going through my head ... what if Google acquired Sonar?
2018/01/13 04:51:25
michaelhanson
sharke
Bob4u
When GIBSON bought CAKEWALK I thought "very well, now they are under strong arms and Gibson will make Sonar greater than ever.
Now I see.
I swear: I will not buy a GIBSON product anymore.
= Bob Axx =


Give it a few days. Like most of the rest of us, you'll eventually calm down and concede that it wasn't Gibson's fault. There may be many good reasons not to buy a Gibson guitar, but Cakewalk going out of business isn't one of them.


I couldn't think of any good reasons and bought a new Les Paul Traditional the week of Christmas. Ice Tea in color and the best made LP of the 4 I have owned in my lifetime. I'm recording it on both Sonar and Studio One. Life and music live on.
© 2024 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account