Jump to content

Introducing Cakewalk Next and our new brand identity


Recommended Posts

53 minutes ago, Mark Morgon-Shaw said:

Exactly.  This is how you should archive tracks and guard against old plugins not working. Run stems or track outs  - then it doesn't matter what happens. You can still reconstruct the track in an editable form.

Example from today's session . Everything the Music Library requests so they have some options when working to picture.  

image.png.735fcd2b25fc68e4b1ab7cd89104d342.png

For those who think that might be a PITA it's much quicker than in the pre-DAW days , we had to make a safety copy of the tape and then write down all the settings for the outboard gear !        

 

And in case you don't want to print the effects in your stems you're gonna have to do the exact same thing you did with a tape setup, so the only real improvement is rendering the audio faster. But the amount of time spent taking note of the settings essentially take away all the time you gained bouncing audio.

Edited by Bruno de Souza Lino
  • Like 1
Link to comment
Share on other sites

My excitement about "4k" and "scalable" UI caused some questions/confusion, so I wanted to elaborate (speculate) based on Jesse's response:

1. It sounds like those who want the existing scale/size of Cakewalk to stay the same will be able to have that. The update will not force your UI to be giant.

2. When I said "scalable" I meant that the UI will scale to match Windows's scaling setting. It already does!  It's just blurry, right now, when scaled. With the vector based update, it will not be blurry. (Depending on how they code it, they could put the scaling % in the preferences so it can be independent of Windows scaling.)

3. If you don't want the scaling -- as with all applications you can set it in the shortcut's "Change high DPI settings" option. This is something they could add in the preferences as well.

4. Other applications have proven that vector based UI doesn't have to be a performance problem. If they encounter performance issues, they can use a process that bakes scaled images based on the resolution needed, at which case performance is identical to bitmap. One of the Cakewalk engineers alluded to this (or something like it) as a solution if necessary. Bottom line? They got it covered!

So there's no reason to panic about the vector update! It's only a good thing... And it will make Cakewalk viable for more users. Understand that right now any 4k laptop is stuck with microscopic UI or very blurry UI. The update will solve that!

And anyone whose vision isn't what it once was, even on a 32 inch 4k monitor Cakewalk is a little small. 125% or 150% is perfect (or will be, once the vector update is released.)

PS. Even if you don't need the vector update, it's represents something very positive from Bandlab: This is the type of update you do when you have long term plans for a product. It bodes well for the future! Let's help the team have a successful launch, and SONAR can grow as the userbase does!

  • Like 4
Link to comment
Share on other sites

7 minutes ago, Cyanide Lovesong said:

PS. Even if you don't need the vector update, it's represents something very positive from Bandlab: This is the type of update you do when you have long term plans for a product. It bodes well for the future! Let's help the team have a successful launch, and SONAR can grow as the userbase does!

Absolutely!   Plus I can relate to the eyesight not being what it use to be and I never had good eyesight to begin with.

  • Like 2
Link to comment
Share on other sites

Thanks @Cyanide Lovesong. We have the ability to turn on/off DPI scaling at the app level and also at the individual plugin level so it's all backwards compatible. See below.
 

image.png

 

image.png

 

Also, to the naysayers, we have decades of experience writing Windows software and worked directly with Microsoft engineers with some of this DPI stuff over the years. Rest assured we know what we're doing, probably more than most others in our industry at least for Windows! 
So far we haven't had any performance issues issues, but as you say dynamically baking bitmaps is a fallback that we discussed a long time ago if it was ever necessary to do.

 

  • Like 13
  • Thanks 3
Link to comment
Share on other sites

13 minutes ago, Noel Borthwick said:

Thanks @Cyanide Lovesong. We have the ability to turn on/off DPI scaling at the app level and also at the individual plugin level so its all backwards compatible.
Also, to the naysayers, we have decades of experience writing Windows software and worked directly with Microsoft engineers with some of this DPI stuff over the years. Rest assured we know what we're doing, probably more than most others in our industry at least for Windows! 
So far we haven't had any performance issues issues, but as you say dynamically baking bitmaps is a fallback that we discussed a long time ago if it was ever necessary to do.

 

It's important to note the amount of people which don't own 4k displays vastly outnumber the amount of people that do. As long as this is kept in mind, rather than making an interface which requires you to have a 4k display in order to have any semblance of screen space, things should be fine. Because examples so far are either an application which doesn't scale properly for 4k displays or an application which only scales properly on 4 k displays.

Edited by Bruno de Souza Lino
Link to comment
Share on other sites

@Bruno de Souza Lino - it's not just 4K and UHD -- it's for any monitor scaling including 2560x1440 which is another common size. They can make the change to vector and you'll still have the size/scale you have now. That's not an issue, and they've made it very clear that's what they intend. You won't be disappointed!

As far as high resolution monitors being a minority -- that's something that can and likely will change over time. This update will make Cakewalk SONAR cutting edge and competitive with other DAWs that have already proven this feature. It's not a crazy change, others have done it and it's becoming standard.

The beautiful thing about a vector based UI is the software is ready for whatever screen size/resolution comes in the future. It's future-proofed.. There is every reason to be excited, and no reason to be concerned. Seriously! ?

Edited by Cyanide Lovesong
  • Like 1
Link to comment
Share on other sites

3 minutes ago, Cyanide Lovesong said:

@Bruno de Souza Lino - it's not just "4K" or UHD (not the same thing) -- it's for any monitor scaling including 2560x1440 which is another common size. They can make the change to vector and you'll still have the size/scale you have now. That's not an issue, and they've made it very clear that's what they intend. You won't be disappointed!

I won't hold my breath for a product I don't even know the price of, as even if it doesn't disappoint me, who knows if I'll be even able to afford it. Plus, I don't even know what the thing looks like. So the only thing I can do atm is raise my concerns about it, because I'm yet to see good results from vector based scalable UIs.

7 minutes ago, Cyanide Lovesong said:

As far as high resolution monitors being a minority -- that's something that can and likely will change over time. This change will make Cakewalk SONAR cutting edge and competitive with other DAWs that already offer this feature. It's not a crazy change, other's have done it and it's becoming standard.

All I care about is not losing my screen space for UI elements. Even if I had a 4k panel, I would still use it in 100% scaling or lower because there's little point in having that many pixels and making everything larger because you can't see jack. You might as well use a monitor with a smaller resolution.

11 minutes ago, Cyanide Lovesong said:

The beautiful thing about a vector based UI is the software is ready for whatever size comes in the future. It's effectively future-proofed, and should look beautiful at any resolution. There is every reason to be excited, and no reason to be concerned. Seriously! ?

But is it backwards compatible? Cause that's my whole point here.

  • Like 1
Link to comment
Share on other sites

I'm old enough to remember when this product was called "Cakewalk" by 12 Tones, not sure why they ever changed it to "Sonar by Cakewalk", and I certainly don't know why Bandlab is now repeating the  same and turning it back into Sonar by Cakewalk.  Is is it the brand or product? Was Sonar more popular than Cakewalk? I haven't been missing the Sonar brand and this seems to be just creating more brand dilution.

  • Like 4
Link to comment
Share on other sites

7 minutes ago, Chris Boshuizen said:

I'm old enough to remember when this product was called "Cakewalk" by 12 Tones, not sure why they ever changed it to "Sonar by Cakewalk", and I certainly don't know why Bandlab is now repeating the  same and turning it back into Sonar by Cakewalk.  Is is it the brand or product? Was Sonar more popular than Cakewalk? I haven't been missing the Sonar brand and this seems to be just creating more brand dilution.

Yeah... I always loved the name and logo they had back then... Twelve Tones and the dancing cake! I remember when they were thinking about new names before chosing Sonar... Long ago...

Link to comment
Share on other sites

2 hours ago, Bruno de Souza Lino said:

Except the question you're responding to was not about pricing.

 

3 hours ago, Misha said:

However, it shouldn't be hard to understand to why I repeatedly insist  that at least  versions sold under Gibson should be permanently unlocked for those who bought them.

@Bruno de Souza Lino is technically right! @Misha apologies for the indirect response. I conflated pricing and granting permanent  unlocks, viewing the latter as a what-if-I-don't-pay scenario, because we don't see a future in which your old projects wouldn't open in Sonar. We've been solid there for decades. But in a catastrophic future scenario, like the company shutting down yielding no ownership of the software, we'd do our best to provide a means of unlocking the core software. Obviously there would be limitations concerning any 3rd party licenses in that scenario. Hope that helps! 

 

  • Like 7
Link to comment
Share on other sites

22 minutes ago, Chris Boshuizen said:

I'm old enough to remember when this product was called "Cakewalk" by 12 Tones, not sure why they ever changed it to "Sonar by Cakewalk", and I certainly don't know why Bandlab is now repeating the  same and turning it back into Sonar by Cakewalk.  Is is it the brand or product? Was Sonar more popular than Cakewalk? I haven't been missing the Sonar brand and this seems to be just creating more brand dilution.

Chris, Cakewalk is a division of BandLab Technologies and a corporate decision was made to have us operate independently under our own brand.
We are now a multi-product company and have two products Sonar and Next with more to come in the future. Calling the product Cakewalk wouldn't make much sense. Cakewalk by Cakewalk? Lol

Also, there were numerous cases in the past where BandLab users were confused with the old branding and thought CbB was the BandLab web DAW (which they have now renamed to BandLab Studio). The new branding will alleviate issues like that.

  • Like 9
Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...