Origin time in Pool is not the same as the one in the Project Window

Hi!

When telling the audio clip “Move > Events to Origin”, the clip’s start position will be moved to a position that starts with 1, not 2.


Repro:

  1. Import an audio file.
  2. Set it’s Origin Time in the Pool to: 2 2:32:24.000
  3. In the Project Window, select the audio event of the file, open the Context menu, then choose “Move > Events to Origin”.
  4. Make sure the main ruler and PTD (Primary Time Display) is set to “Seconds”, press “L” to move the Project Cursor to the beginning of the audio event, then see what the PTD readout is.

Result: First digit of the Origin Time in the Pool is not the same as the first digit of the Origin Time in the PTD.

Confirmed, and on my end (using C13.0.41 / Windows 10 22H2), after reproducing exactly your steps, it’s even worse than that :

1 Like

Thanks, but I think you forgot to execute “Locate Selection Start” by pressing the “L” key. This is why the rest of the Time information doesn’t match with the PTD. Also, thanks for emphasizing the relevant parts of the screenshot with markup elements. My head began to spin when I started to look at your screenshot. Not used at all with the C13 interface.

1 Like

No, I perfectly remember having used the L key : my posted screenshot has been taken directly after that.

1 Like

OTOH, if I use directly from the pool window the Insert into Project > At Origin command, at least, the resulting event is inserted at the right place (hh:mm:ss), but the ‘day’ digit remains wrong, this, event after having extended the project duration to 3 days, in the Project Setup window.

1 Like

Change tempo value in the pool, it has to be the same of the project.
The project tempo is 120 according to the pool and the highlighted file is a way different.
Let me know.

Hi, @Puli

Thanks for the suggestion : I haven’t thought of the audio file tempo, I admit.

Sadly, nope : the issue remains with the audio file origin still defined as 2 2:32:24:000 in the Pool window, even after having changed its tempo to 120.00 :

1 Like

I think that might happened during the import from project procedure.
See this post:
https://forums.steinberg.net/t/musical-mode-file-tempo-issues

Try this:
get rid of that track from the pool then re- import using that “tempo definition”.

@Martin.Jirsak, can you please report this to Steinberg? I need this so badly…
:pensive:

This persists in Cubase 14 as well.

Repro:

  1. Go to Project Setup and set your Project Duration to at least 2 days. Make sure the Time Offset is 0.
  2. Record some audio at 1 0:00:00.000 and make sure you don’t move the event after the record process stops.
  3. With the audio event selected, execute the Move > Events to Origin command.
    Result: the event is moved at 0 0:00:00.000.

Hi!

Shouldn’t the origin time of bounced files be the same as the time where the events were before bouncing?
Here, everything moves 1 day earlier…
:pensive:
after bouncing

Until Steinberg fixes this, the workaround is to just move the events one day ahead before bouncing, then execute “Events to Origin” on the new events (to bring them back at the original position). It’s a little bit of a hassle, but at least the job gets done. I’m curious if Nuendo folks have the same issue…