2021.04 Feedback

[chris.r]

5 hours ago, msmcleod said:

A node is put at the end so you can use the shelf tool.  It would appear that it thinks that the end of the project is later than it is.  It could be something like an automation envelope later in the project ?

For me, when using Clear All or Reset Tempo Map, it adds the last node at the end correctly, not past the end. All I really wanted to point out was that when designing a DAW feature and having to choose between evil and evil, that is letting Cakewalk create an extra event at the far end of the project (for some: an inadvertent change to the project) or leaving user without the shelf tool for that part until he decides to create the node intentionally, I would suggest to choose the latter every day of the week - that would be definitely lesser evil. Creating the node 'automatically' with some users not even noticing it can potentially lead to confusion at best, in this case if he decides to shorten the arrangement not knowing there's a node much later at the end then one can wonder why is the Export Audio taking ages, for example.

Alternatively you may let the shelf tool work on the dotted envelope by just allowing to change just the existing node's value without having to automatically create the extra node.

Here's an example of a ghost node being created when I first use the shelf tool then click ESC while still dragging. I can't see that there's extra node appearing on the tempo list in inspector but I can definitely drag it out from under the existing one and I can delete it without deleting the existing one. To me it's confusing, or I'm totally wrong and would need some explication to understand : 

[msmcleod]

@chris.r / @Skyline_UK / @Terry Kelley - thanks for your feedback on the "end of project" tempo nodes.

The official 2021.04 Update 1 release will no longer create tempo nodes at the end of the project when importing an older project or using the "Clear All" context menu command.

It shouldn't be much longer before this is released.

[Hopital]

2 problems with the new tempo map:
1) the offset tempo map ignore the selection=> only global changes are possible
2) process fit to time no longer works

[msmcleod]

1 hour ago, Hopital said:

2 problems with the new tempo map:
1) the offset tempo map ignore the selection=> only global changes are possible
2) process fit to time no longer works

Thanks @Hopital - both of those issues have been fixed for the main release.

[u-u-u]

Concerning the bandlab integration: I've just come back to Sonar (Edit: haha, sorry: Cakewalk :D) to see whether this now provides a good workflow for sharing simple projects with my band mates.

Looks very cool!

For now I just tried opening one of my existing bandlab projects... seems to work fine. Also seems to be a quick way for extracting MIDI and wave stems from bandlab.

On question though: It seemed to me as there is only the possibility to upload Cakewalk projects as new bandlab projects, not as revision of existing ones. That would be really great! Or does it work already and I just didn't find it?

Edited May 14, 2021 by u-u-u

[Jonathan Sasor]

7 hours ago, u-u-u said:

Concerning the bandlab integration: I've just come back to Sonar (Edit: haha, sorry: Cakewalk :D) to see whether this now provides a good workflow for sharing simple projects with my band mates.

Looks very cool!

For now I just tried opening one of my existing bandlab projects... seems to work fine. Also seems to be a quick way for extracting MIDI and wave stems from bandlab.

On question though: It seemed to me as there is only the possibility to upload Cakewalk projects as new bandlab projects, not as revision of existing ones. That would be really great! Or does it work already and I just didn't find it?

If you publish the same project more than once, it uploads as a new revision.

[Noel Borthwick]

9 hours ago, u-u-u said:

Concerning the bandlab integration: I've just come back to Sonar (Edit: haha, sorry: Cakewalk :D) to see whether this now provides a good workflow for sharing simple projects with my band mates.

Looks very cool!

For now I just tried opening one of my existing bandlab projects... seems to work fine. Also seems to be a quick way for extracting MIDI and wave stems from bandlab.

On question though: It seemed to me as there is only the possibility to upload Cakewalk projects as new bandlab projects, not as revision of existing ones. That would be really great! Or does it work already and I just didn't find it?

@u-u-u You can upload as a revision to an existing project. Here are two ways to do it:

 

1. Upload a new project from Cakewalk. Once you have done that any subsequent updates to the SAME project will upload as revisions to the BandLab project. 
i.e. The Cakewalk project will store a reference to the uploaded BandLab project and tracks changes from that point on.

2. Download a project created on BandLab to create a NEW Cakewalk project. Once you do this any changes to this project will upload as revisions to the ORIGINAL BandLab project. Similar to 1 the Cakewalk project stores a reference to the BandLab project and tracks changes from that point on.

[Brian Lawler]

On 5/11/2021 at 10:48 AM, Milton Sica said:

I'm using Cakewalk on a DELL Inspiron 14 notebook. Whenever I leave the application, the machine's sound is completely muted / muted. I can't hear anything from other applications anymore. I can only do this after rebooting the machine. Any ideas on how to solve this problem?

This probably isn't the solution, based on your symptoms,  but you might try it:

https://solidstatelogic.zendesk.com/hc/en-us/articles/360007770037-Hear-your-DAW-and-apps-at-the-same-time

[Noel Borthwick]

Cakewalk 2021.04 Update 1 Release Candidate [build 170] is now available! 
Please sanity check this. It contains several new fixes and improvements for recording. Thanks for your assistance so far in helping us make it a stable release. It will go live early next week.

[janek.goralczyk@gmail.com]

Hello Guys,

Is it possible to somehow move back to the previous version, i.e. 2021.01? The latest one doesn't work well on my PC...

Thanks,

Jan

[Andres Medina]

3 hours ago, janek.goralczyk@gmail.com said:

Hello Guys,

Is it possible to somehow move back to the previous version, i.e. 2021.01? The latest one doesn't work well on my PC...

Thanks,

Jan

Hi -

Yes: you con revert using the link in the main page of this update, under "Should you need to revert to the 2021.01 release, you can download the Cakewalk 2021.01 Rollback installer" -

https://discuss.cakewalk.com/index.php?/topic/29141-cakewalk-202104-update-1-release-candidate-updated-to-build-170/

 

[billp]

Please see this topic

Delete hole messed up the tempo track and didn't move the markers, even though they were selected.

I think this has been mentioned, but I've also noticed that the Aim Assist is not always aligned correctly when mousing over the time ruler with snap enabled, while it aligns correctly when over the piano roll.

[msmcleod]

2 hours ago, billp said:

Please see this topic

Delete hole messed up the tempo track and didn't move the markers, even though they were selected.

I think this has been mentioned, but I've also noticed that the Aim Assist is not always aligned correctly when mousing over the time ruler with snap enabled, while it aligns correctly when over the piano roll.

@billp - I replied in the other thread, but just for everyone else's benefit,  this has now been fixed and will be included in the official release.

[Adam Biser]

2021.04 Update 1 RC1  (build 27.04.0.170) fixes everything that I had reported about the articulation track.  It works beautifully now from what I've tried.

Thanks so much for the update.

[Anders Madsen]

Finally I can just restart CW after a chrash without rebooting PC!
Old-ish Roland Octa-capture never gets driver update.

[Andres Medina]

Hi,

Just got a weird crash, doing the following, when rewriting the music in a project:

1. Select All
2. Wipe
3. Crash

Weird part: the tempo of the project was changed to 8 bps prior to the crash. Before this update, when you selected all and then wiped, the tempo remained unchanged. Am I missing something?

Enclosed the minidump.

TyC 0209 Videojuego v2 3-2_05182021_135122.zip

[Noel Borthwick]

@Andres Medina thanks we'll investigate it. did you hit the delete key after selecting all? If you can share the project file before the crash.
 

[Andres Medina]

1 hour ago, Noel Borthwick said:

@Andres Medina thanks we'll investigate it. did you hit the delete key after selecting all? If you can share the project file before the crash.
 

Thanks Noel -

No, I used a shortcut for "wipe tracks", not delete.

I'll send you a copy of the project as soon as I can.

[gmp]

I'm using the latest build 175. Since 2021.04 the Tempo change box defaults have changed. I prefer the previous way it's been done for decades. First go to any bar from bar 2 on up and hit stop. Go to Project  - insert tempo change. Hit the mouse on "click here to tap tempo". I do that then quickly start tapping the spacebar which is far more accurate. 

In the past the default selection was "Change the most recent tempo". Now the selection is "Insert a new tempo". If I leave the default like I used to and  I hit Ok and go back to bar 1. The new tempo won't kick in until I get to the bar I was at when I did the tempo change.

Most of the time when I need to change the tempo it's because I'm trying to match the tempo of a prerecorded rough demo track that I imported into CbB. Many times I go to near the middle of the track, since if the writer was playing with no click track they may speed up. 

So I listen there and then bring up the tempo change box and change the tempo. Since I'm not at bar 1 the tempo change is inserted at whatever bar I'm at. Whereas in the past I didn't have to change the selection to "Change the most recent tempo", I just hit ok.

Are there any others out there like me that prefer the old default in this box? I don't change tempos every day otherwise I'd remember this change. I hope we can return to the old default selection. I've been using Cakewalk since 1992 and it's always been like this even back then - why change?

 

[Toy]

There was a bug in the tempo track that included a crash.
*Cakewalk 2021.04 Update 1 (build 27.04.0.175)

It was deleted when "Change the Most Recent Tempo." was set to the same value as the tempo immediately after.

If there is an envelope setting, "Insert a New Tempo" will be executed instead of "Change the Most Recent Tempo.".
* In this case, it is linear.

If the two situations overlap, double registration will result and the tempo will be out of order.


If the same tempo continues, the "Change the Most Recent Tempo." is not selected and the "farthest tempo" is changed.


First, move the "default tempo (1:01: 000)" and it will be duplicated.
I was able to change it by continuously editing the "default tempo".
Erases tempos other than "default tempo".
It crashed when I edited the tempo before the "default tempo".

 

Edited May 19, 2021 by Toy