Patrick Goudriaan

33 minutes ago, msmcleod said:

The Set/Measure Beat At Now functionality has not changed in any way.  It still modifies the underlying tempo map in the same way as it did before.

The only difference is that now the tempo track envelope is reconstructed from the underlying tempo map after the Set/Measure Beat at Now command.

Do not confuse the Tempo List in the Tempo Inspector with the old tempo map. It may look the same, but it isn't. 

The Tempo Inspector shows a list representation of the envelope nodes, not the tempo map.

@msmcleod
Yes, but it also overwrites the tempo node I set before.
I changed the tempo from bar 1 to bar 15,
if I set a new "beat at now" at bar 18, it starts recreating the tempo from bar 1 to bar 18. And before it used to change only the tempo between bar 15 and 18.
I think this happens because the created tempo before and after beat 15 is the same after setting "Beat at now".
Because when I change the tempo in the tempo view BEHIND beat 15, then I can set beat at now anywhere behind and THEN it creates a new node without overwriting the excisting node.
<edit 2> It happens randomly, I just tried it on another track and from 18 new nodes, it created 16 new nodes and 2 overwrites.</edit2>

1 minute ago, David Baay said:

I know SM/BAN inside and out, but do not understand what either the documentation or you mean by "create" or "add" new bars or beats. The sentence after the one you highlighted more accurately describes what it does. Nothing is created except tempo changes, and those changes result in existing bar and beat lines moving relative the absolute timing of audio transients or MIDI events to align the timeline to the performance.

The same dialog does let you change the time signature of a measure, which can effectively 'add' beats  to a measure, but that's a separate operation from 'Setting' a measure or beat to Now. And so far as i know, that also works as it always has.

If this isn't just a misunderstanding of the awkwardly-worded documentation, I'll need a specific example of what you're trying to accomplish in order to understand whether something is not working as it always has.

If I want to move bar 18, bar 18 should move.  The system is not supposed to overwrite the location of bar 15 I have earlier moved.

Set beat at now, should create a new tempo behind bar 15 up to bar 18 and not change the tempo before bar 15.

Note: I have used this before and it changed after the new tempo view was released.

 

2 hours ago, David Baay said:

I don't really understand what you're saying here, but what you showed in your original post is working as designed, and as it always has. Cakewalk modifies the most recent tempo to make the specified beat land on the current Now cursor position, and inserts a matching tempo at the point to serve as a reference point for the next Set.

It used to be possible to add a new beat without deleting the previous.

Quote

5 minutes ago, Patrick Goudriaan said:

I have an old track that has tempo changes, to get a click track I insert a lot of "Beat at now"  markers , but now it overwrites the previous one(seen that in the tempo view)  , but not always, sometimes it creates a new one as I want it to do.

I just found out, that if I change the tempo of the last section first, I can insert a new "Beat at now". 

 

I have an issue with inserting beat at now feature. I'm not sure it is from the latest version, but it used to work with the version that had the old tempoi view.
Description:
I have an old track that has tempo changes, to get a click track I insert a lot of "Beat at now"  markers , but now it overwrites the previous one(seen that in the tempo view)  , but not always, sometimes it creates a new one as I want it to do. 

.