Jump to content

Recommended Posts

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.

Before Delete Hole.PNG

Delete Hole Options.PNG

After Delete Hole.PNG

  • Thanks 1

Share this post


Link to post
Share on other sites
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.

  • Thanks 1

Share this post


Link to post
Share on other sites

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.

  • Like 1
  • Thanks 1

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites
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.

Share this post


Link to post
Share on other sites

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?

 

  • Like 1

Share this post


Link to post
Share on other sites
Posted (edited)

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.

bug2.gif.d1c81703cdbc4d013719a99745cbc943.gif

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.

bug1.gif.2a04841c214633a63ac324584ea88310.gif

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

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

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".
CrashBug.gif.8256024ef93e68836f14017033603079.gif
 

Edited by Toy

Share this post


Link to post
Share on other sites

Akai Mpc beats keeps crashing  version after version and I don't know if it's a Cakewalk or Akai problem it's really frustrating.

Share this post


Link to post
Share on other sites
Posted (edited)

I am still at the early stages of exploring how the new Browse Bandlab (Load and Import) and Publish to Bandlab features might fit into my musical goals. (I have been looking forward to them since I saw early versions in The Reference Guide as forthcoming features.)

In another thread related to using Bandlab resources in Cakewalk specifically on the issue of resource having a timing issue in Cakewalk, Noel Borthwick wrote:

2 hours ago, Noel Borthwick said:

I think it has to do with conversion from M4A when importing . . . .

I seem to have verified that the Bandlab resources do indeed have gaps at the beginning. However, a personal *.wav loop I tested previously doesn't have a gap. For some reason though, when I published a new test project (consisting of just tracks 1 and 2 below) and imported the project, my *.wav was changed. (See below.)

I am interested in what might have happened (user error? bug?) because I very much want to develop a collaborative workflow using the new features.      UPDATE:  Solved  🙂  User inexperience with the Mix feature. 😞   (See immediately below.) 

image.thumb.png.882567fe3be1e7aa5ef64903b828428b.png

Edited by User 905133
(2) to mark is specific post solved; (1) replaced and reduced image

Share this post


Link to post
Share on other sites

In this version I started to verify that in some projects after exporting some synthesizers are silenced in the MIX.

  • Thanks 1

Share this post


Link to post
Share on other sites
3 minutes ago, Milton Sica said:

In this version I started to verify that in some projects after exporting some synthesizers are silenced in the MIX.

THANKS!!!!!  I reset the Mix using Mix Recall:

image.png.a6be79a60d6032f7f1583141d16d37c2.png

I never intentionally use different mix settings, but evidently one time I tested it.

Share this post


Link to post
Share on other sites

@User 905133 are you sure that you don't have the gaps in your original project on Bandlab? The gaps applied only to MP3/M4a files. Wave files wouldnt have this problem. We already fixed issues related to MP3 files last year.

Regarding track 4 is it possible that you uploaded with the track hard panned? Does it sound stereo in the bandlab project?

 

  • Thanks 1

Share this post


Link to post
Share on other sites
1 hour ago, Carlos Iglesias said:

Akai Mpc beats keeps crashing  version after version and I don't know if it's a Cakewalk or Akai problem it's really frustrating.

MPC beats has a problem that we reported to AKAI months ago. You can forward the crash dump and we can verify if its the same issue.

Share this post


Link to post
Share on other sites
Posted (edited)
19 minutes ago, Noel Borthwick said:

@User 905133 are you sure that you don't have the gaps in your original project on Bandlab? The gaps applied only to MP3/M4a files. Wave files wouldnt have this problem. We already fixed issues related to MP3 files last year.

Regarding track 4 is it possible that you uploaded with the track hard panned? Does it sound stereo in the bandlab project?

Good points; thanks. I will try to double check the gap in the track 1/track 3 Bandlab resource  from the 2020 test and give the Bandlab version of track 4 a listen. 

UPDATE: image.png.a8df0b3d768ab6fd59901eea02f1f7db.png

Edited by User 905133
to add an update re: track 4 in the first post I did

Share this post


Link to post
Share on other sites
22 minutes ago, Milton Sica said:

In this version I started to verify that in some projects after exporting some synthesizers are silenced in the MIX.

The problem was that when you double-click on a track to select everything, you only select up to track 11

Share this post


Link to post
Share on other sites
5 hours ago, Toy said:

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.


 

Hey Toy, I'm unsure from your post if this Tempo crash bug and quirky behavior you outlined was fixed in build 175 or is it still being worked on. I haven't been having any crashes with the tiny amount o tempo change work I do. I very rarely ever have more than 1 tempo in a song and never have a series of tempo changes like a ritard. 

The only problem, which is more of an inconvenience is that the default setting has changed in the tempo box and I have to retrain myself to remember that. It sounds like the whole Tempo box and Tempo view were broken and got buggy. I hope they fix the default behavior too, if they're still working on it. Let me know if the problem you wee having is fixed and if this is all again working the way it was for you.

Share this post


Link to post
Share on other sites

We had early access on for over two weeks and non of this was reported. It will now be addressed in the next release.

Share this post


Link to post
Share on other sites
9 minutes ago, Noel Borthwick said:

We had early access on for over two weeks and non of this was reported. It will now be addressed in the next release.

Who's post are you referring to?

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

×
×
  • Create New...