2021.04 Feedback

[Noel Borthwick]

A tempo track is a standard feature in most modern DAW's. Can you explain what you are trying to do?
The tempo inspector allows you to work in pretty much the same way as you would in the old tempo view. 

14 minutes ago, willard cottrell said:

I find the new tempo track less suited to my needs.  It interrupts my work flow.  Is there any way to remove that part of the programming?  OR, is there a way to incorporate the old AND the new view?  OR - - - do I have to accept it as the new gospel and re-adjust my attitude?

 

Willard

 

[Panu Pentikäinen]

4 hours ago, Noel Borthwick said:

A few:
It looks nice (to some)
It’s optional

It looks nice (to some).
It don't have to be optional. 

 

 

[gustabo]

8 hours ago, Bassfaceus said:

hello all..i notice this was asked earlier but no response yet...

what is the usefulness of waveform outline?

thanks

For me, it's desirable eye-candy!

[David Baay]

55 minutes ago, Patrick Goudriaan said:

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

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.

[User 905133]

59 minutes ago, willard cottrell said:

I find the new tempo track less suited to my needs.  It interrupts my work flow.  Is there any way to remove that part of the programming?  OR, is there a way to incorporate the old AND the new view?  OR - - - do I have to accept it as the new gospel and re-adjust my attitude?

Would customizing a Workspace help with this?  Here are the factory Tempo Workspace and the same Workspace slightly tweaked.

   

Edited May 3, 2021 by User 905133
Name Correction: "Track" removed from "Tempo Track Workspace" since its just called "Tempo."

[Herbert Zio]

2 hours ago, Morten Saether said:

O atalho padrão é ALT + T.

ALT + SHIFT + 5 mostra / oculta a trilha Tempo e o inspetor Tempo.

Thanks for informing! ?

[Herbert Zio]

I am very happy with the improvements and features made available on Cakewalk, congratulations to the whole team! ??

[Štefan Gorej]

@Noel Borthwick
I can confirm, that with the provided Cakewalk build 27.04.0.145 and ExceptionHandlingSeverity set to 5,
Project with VST3 version of Presswek loads successfully, so no exception caught by Cakewalk.

I'll also try beta builds of u-he VST3 plugins without ExceptionHandlingSeverity and confirm (also to u-he) if the've fixed this issue on their side or not yet.

Thanks for your assistance,
Stefan

EDIT: I also tried loading a Cakewalk project with VST3 version of Press werk after updated to Presswek latest beta 1.1.4.11152.
When ExceptionHandlingSeverity is not set the Presswerk still causes Cakewalk to crash. So new build of their VST3 doesn't solve this issue.
Minidump file attached.

 

_05032021_201459.zip

Edited May 3, 2021 by Štefan Gorej
Added more info

[jackson white]

1 hour ago, Noel Borthwick said:

The tempo inspector allows you to work in pretty much the same way as you would in the old tempo view.

Only -way- better. I am most grateful for the reworking of this feature and the improvement in (my) productivity. 

[Patrick Goudriaan]

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.

Edited May 3, 2021 by Patrick Goudriaan

[Jan van Schalkwyk]

17 hours ago, Noel Borthwick said:

Are you sure this is related to the Cakewalk update? i.e have you verified by rolling back that this problem doesnt occur? Its more likely system related since we aren't seeing this problem. 

Hey Noel,

I've seen this happen intermittently between releases. TTS-1 does not seem to get registered (every time)
My only resolve is to run CbB as Aministrator permanently and this solves the problem.
My DAW is dedicated to CbB and no changes are made to the system except Win 10 updates

My 64c

[David Baay]

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.

[msmcleod]

1 hour ago, Patrick Goudriaan said:

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

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.

[Patrick Goudriaan]

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.

 

[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>

Edited May 3, 2021 by Patrick Goudriaan

[sjoens]

New File Menu Issue

When using CbB on a 2nd monitor, the Insert Softsynth dropdown File menu floats on the 1st monitor. It doesn't stay with the program.

Edited May 3, 2021 by sjoens

[David Baay]

26 minutes ago, Patrick Goudriaan said:

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.

Thanks for the clarification. i see the problem now. I had not noticed there was a tempo at 15:04 before you set 18:01. I have not seen this issue - possibly because I've only been setting whole measures recently. I'll have to try setting some beats around measures and see if I can reproduce it.

[Noel Borthwick]

48 minutes ago, Jan van Schalkwyk said:

Hey Noel,

I've seen this happen intermittently between releases. TTS-1 does not seem to get registered (every time)
My only resolve is to run CbB as Aministrator permanently and this solves the problem.
My DAW is dedicated to CbB and no changes are made to the system except Win 10 updates

My 64c

The thin installer doesn't touch registration of the instruments so its very unlikely. Esp if the OP upgraded from 2021.01

[David Baay]

43 minutes ago, msmcleod said:

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.

Hi Mark, can you expand on this? How exactly do they differ? In particular, I would expect the lists to be the same, and the envelope to be the same as the old 'chart' view - at least so long as the changes are all jumps.

[Base 57]

Regarding the (experimental) Win10DPIAwareness setting. The only problem I have seen so far is in the PC Concrete Limiter. The numerical db display at the top of the meters is screwed up. Everything else I've tried looks good.