Jump to content

Terry Kelley

Members
  • Posts

    1,220
  • Joined

  • Last visited

Posts posted by Terry Kelley

  1. Since project files are so small I save constantly and increment the filename with a note in the name of what I was doing (new drums, new lead vocals, etc.) I also run a batch file to copy all new files to a separate drive. I don't depend on autosave.

    At some point I have the option of deleting early projects if I am sure I won't need them but I usually keep all of them until I am done with the song.

    This has saved my butt from jerky and fumble-finger moves many times.

    • Like 1
  2. Once I figured out how to find the offending module in the dump files and when I determine it isn't Cakewalk, I don't send in issues or files. 

    And we have to pay to do any real testing. To do any real testing you have to use it for a long period of time. I'm not going to spend any time digging into it if I can't save my work. Why bother.

  3. I am a huge Cakewalk fan but the competition is just that - competitive. I’ve spent the last month learning a different DAW and it can do everything Cakewalk can and then some. It just looks different. If BL comes out with a standalone price  for a perpetual license (and not a standalone subscription) I can easily switch back and carry on. Cakewalk does have a nice UI.
     

    I think the top of the heap is shared with the competition. 

  4. 1 hour ago, Quinellipe Zorn said:

    If Bandlab isn't watching this forum, that's Bandlab's problem.  
     

    If "the Bakers" are interacting here, it's also their obligation to provide feedback within their company based on those interactions.  A company official cannot transact with customers and then disclaim it isn't their role to provide feedback, or such.  (And I'm not suggesting whatsoever that the engineers are making such disclaiming, and I have full confidence that they provide feedback.  If not, well, that's on the company.)

    While I personally think we are being “strung along” at this point,  I don’t think it’s the developers doing it and I get the impression they would give us everything we want - if they could. We can bitch at them until the cows come home and all they can do is pass it on. Why bother them with that. 

    Talk to Bandlab directly.

    I was a developer and development manager for many years and we had little direct say in the pricing and rollout other than giving an opinion. It was marketing, sales and finance that drove the pricing and rollout. 
     

    • Like 3
    • Great Idea 1
  5. I had no problem opening new Sonar files in CbB or old Sonar 8.02 and vice versa. However, old Sonar didn't like my VST3 plugins.

    That said, I decided to close out anything of importance for when that day arrives. But you can always get a one month subscription to the new Sonar to finish anything up and export it to the new DAW. That's my plan for any "ah crap" moments.

  6. I’m finishing up all of my CbB projects in preparation to move on. I certainly don’t want to get caught without a way to finish them and Old Sonar won’t support various VSTs or Melodyne 5.

    Edit: Added the 5 to Melodyne for clarity. 

  7. I seriously doubt Bandlab will come on this forum to argue. Go to them directly. The developers aren't responsible for representing the marketing plans of Bandlab. Posting about it here is pointless. The developers have plenty to do. Let them do it.

    • Like 4
    • Great Idea 2
  8. 1 hour ago, Resonant Serpent said:

    I finally had a chance to sit down and work with the new interface. 

    I have to say that I'm really, really digging it. It's snappy, easy to read, and unlike Cubase and Studio One, it doesn't seem cluttered or have fonts that are too small.

    Picked up the subscription, and going to give it some heavy use. 

    I must say, CbB/Sonar has one of the best first-look UIs around. I still compare others to it.

    • Like 3
×
×
  • Create New...