Since there is (still) no easier way to change the global tempo of a project in relative terms, I would like to use the Projekt Logical Editor for this.
Here is a simple tempo track with a few events as an example. I want to reduce the tempo of the entire track - let’s say - to 75%.
In the Project Logical Editor I set the following.
All tempo events are adjusted properly except the first one! This is a bug in my opinion.
The tools in the Controller Event Editor will let you scale and otherwise manipulate the values without using the PLE.
Hi @raino, thanks!
With this method I am also familiar, it was also presented at the last YT Cubase Club live stream
However, it is only a workaround and not the best solution for the problem I presented.
My aim is to do the global relative tempo change for the whole project very precisely and quickly and to assign it to a key command.
To experiment with tempo changes of short parts of the project, I also prefer the method you presented.
Unfortunately, this method can only be used on the tempo track and not in the Tempo Editor, which has a better y-resolution. and scale.
Best Regards, Pat
Hi,
Reported to Steinberg. Thank you.
Hi @P.A.T ,
Thank you for the post, I was trying to do this very thing.
I am sure you have discovered this for yourself.
But for the benefit of anyone else, the workaround that I have employed to address the bug you have identified, is to duplicate the initial tempo marking event at the very beginning of the project:
Position 0.1.1.0,
or 1.1.1.0 if your project starts at Bar 1.
The project logical editor will still ignore the greyed out initial tempo marking, but identify the duplicate marking and process all tempo events as per your editor script.
