Adjusting the origin time in pool changes the "modified time" value of the wave file

Hi! In an audio recording file, “created time” and “modified time” parameters represent the start and, respectively, the end of the recording. Right? Because of this, if a wave file is imported into Cubase from an external location, that file should not change its parameters. At least not the “modified time” parameter. I’m saying this because, usually, the “created time” is embedded in thename.

image

What happens is that when you modify the origin time in the pool, the “modified time” parameter of the file changes to the time and date of your origin time adjustment (which is different from the time when the recording ended). This is a problem.

Another problem is that you don’t get any kind of warning (that the external file is being modified).

If it’s possible, please change this behavior. Thanks!


Issue repro

  1. Import an external wave file into an empty project (and make sure the file is not copied to the project folder).
  2. Make a note of the “modified time” parameter of the file.
  3. Change the origin time of the file you just imported (in pool)
  4. Compare the note you’ve taken with the “modified time” parameter of the same file.

Result 1: the two pieces of information don’t match.
Result 2: you don’t get any warning that the external file is being modified.

No, these fields represent the creation time of the file and the last modification of the file, respectively. They just mirror this data from the file system (MS File Explorer, MacOS Finder). So, whenever you modify the file, the modified time is set to the current time. There is no field that would represent the end time of the recording. Yes, the recording end time can be seen in the modified time field as soon as recording has ended, but this is only valid until you change the file.
When you edit the origin time, you effectively modify the given file (its metadata), so the last modification time has to change.

Hi! I appreciate you taking the time to reply to my post. It’s a very well written reply. Good job! But, the problem is that Cubase changes the file! Not me. And this is what I’d like Cubase not to do.

The only reason I’m modifying the origin time in the Pool, is because I need to move every audio event [that I import] to the correct day in the timeline. It’s very nice that Cubase has the ability to change parameters in files. Don’t get me wrong! I like this! But I think Cubase should do this only if the file is inside the project fodler.

P.S. I’m not clicking the heart icon because, though the reply is gramatically correct, the text has nothing valuable to the issue I’m having, or the feature request I’m making. Not that I owe anyone any explanation :innocent:

Okay, I missed this part. Yes, you are right, there should be a warning when you are going to modify an external file.

It seems Cubase writes the “origin time” into the file itself. As this is a modification of the file the OS updates the “modified time” and Cubase shows that.
Working as intended.
Leave it up as a feature request though, I just wanted to add some info.

True.

Cubase shows what exactly?

“Some info” that would downgrade the importance of my issue? Thanks. That’s so nice of you! :sunglasses: (hope you get my joke)
Even if it’s working as intended, this is a bad behavior, and I will tell you why.

I produce wave files with my Zoom H1N and H5 recorders. I then take the SD cards out and plug them into my computer. Then, I import the files directly into Cubase (without copying them to the project folder).

I’m doing this because I need to join (bounce) them in a certain manner. Why bother copying them if they’ll eventually get deleted (after new files are created)? So, these wave files are copied during the bounce process.

Before bouncing though, I need to make sure they are all placed correctly in the timeline. Zoom® missed the fact that some people might want to make recordings spanning more than one day, so they didn’t make 100% sure that the time stamps would be 100% accurate (that’s another story—bear with me). Sometimes, even though the date of some file is not correct, I can still position the audio events correctly by figuring out if the recording is meant to continuous or not. This is where the “created” and “modified” time values come in handy. Just now, I wanted to give you a screenshot example, but Cubase modified all of my external wave files (on three SD cards). They all have the date of today as the “modified” time stamp.


Anyway, I hope you get the gist of what I’d like my workflow to be. The point is that external files should not be modified. At least not without a warning.

The “file modification date” that the OS reports.

Look, you are dead wrong in this assumption:

…but you have the right to post your request, of course. It’s just you started it based on a wrong assumption.

Thanks for clarifying that for me. I’ll say though that I find this a little bit odd, since the “date modified” value is displayed in the Pool by default, not as a consequence of me editing the origin time. In other words, I don’t understand why you had to also say that. Maybe it was unintended…

I would say “wrong”. Yes. But not “dead wrong”! Until you further modify the file, the “modified time” parameter represents the end of the recording. Do you still say otherwise?

I don’t think I did.
…but you have the right to post your counterargument. :sunglasses:
:innocent: