topic Re: CRD - dumped footage on external drive - how to preserve date / time metadata in Professional Video

CRD - dumped footage on external drive - how to preserve date / time metadata

coyotegyrl — Mon, 06 Apr 2026 15:45:55 GMT

Good morning,

On a field shoot, I dumped multiple cards onto an external drive (no way to process in the field, currently). If I import those clips from the external drive with CRD, I lose the original date and time stamp on my clips. The info is there, but I think my settings need changed in CRD. What are those settings and where can I find them?

The only other solution I can think of is to put the footage back onto the cards--and that seems like a waste of time.

Thank you!

Re: CRD - dumped footage on external drive - how to preserve date / time metadata

AtticusLake — Tue, 07 Apr 2026 07:52:18 GMT

There may be a solution, but it depends on the file format you're shooting, and on your camera. (I don't have a C500 to experiment with.)

Basically there are two types of meta-data your files may have.

Every file on a computer (which includes cameras etc) has file meta-data stored about it by the operating system. This includes a creation date and a last modified date. The thing to understand is that this meta-data relates to the physical copy of the file, not to the content of the file. When you copy a file from the memory card, does the copy get a new creation date, because it's a new file? Or does the creation date get copied over? It could be either way, depending on exactly how you copy it. Probably this isn't up to CRD. However, once the original creation date is gone, it's gone. Copying the files back to the memory card won't make any difference. Your only hope here is to check both the creation date and the last modified date - one of them may be good.

Media files can have additional meta-data stored inside the file, as part of the media format. What this data is, and whether it even exists, depends on the file format and on the camera. But it could include the date/time that a clip was actually shot, and if so, it's permanent - because it's inside the file, it gets copied as-is along with the rest of the file. So, cross your fingers, and look for a "Date Created" field or some such. In Resolve, for example, you can see this in the media pool, if you customise the headings and include Clip Details / Date Created.

Good luck.

Re: CRD - dumped footage on external drive - how to preserve date / time metadata

coyotegyrl — Tue, 07 Apr 2026 15:23:16 GMT

Hi AtticusLake,

Thanks for the convo. On the external drive, the date and time created is correct on the CRM file. Date modified mathes the time I transferred the files from the card to the hard drive. If I copy the files back to a card from the hard drive, the date and time created are retained on the CRM file, but at the same time it creates a XML file and that created date and time is changed to when it was transferred (to today's date and time). When I then use CRD to import the clip from the card, the date and time are changed to today. Any additional ideas? To me--this means that something is going on in the CRD process because I can see the original date and time shot on the CRM file. Thanks!

Re: CRD - dumped footage on external drive - how to preserve date / time metadata

coyotegyrl — Tue, 07 Apr 2026 15:25:19 GMT

perhaps I should also add that I'm on a Mac platform using CRD.

Re: CRD - dumped footage on external drive - how to preserve date / time metadata

AtticusLake — Tue, 07 Apr 2026 19:21:30 GMT

You're reading too much into the operating system's meta-data. The operating system neither knows nor cares that these files are movies, or when they were shot, or anything like that. All it cares about is keeping track of the data blocks on disk.

So for example when you say "it creates a XML file and that created date and time is changed to when it was transferred"... the date and time weren't changed. The XML file is a completely new file; its OS meta-data has nothing to do with the OS meta-data on the CRM file.

So, again, by far the best approach is to use the media meta-data stored inside the media file; i.e. the "Date Created" field. If there isn't one, then the OS meta-data will be your best hope to get an idea of when the clips were shot, but don't expect it to be resilient to copying the files, and certainly not if you do any kind of processing on the files. Really, if your camera isn't writing a date created inside the files, then the best bet is to look at the creation times of the files on the memory card, and just make a note of them. Like take a screenshot of a directory listing, or something.

Re: CRD - dumped footage on external drive - how to preserve date / time metadata

coyotegyrl — Mon, 04 May 2026 18:33:46 GMT

I'm still having the same issue.

So I'll ask in a different way: where are the settings in Canon Cinema Raw Development that allow me to keep the date and time recorded? Currently, when I import a clip, that information is not retained.

Inside the CRD<Settings ?

And / or in Export<Export configuration.

What needs changed? Thanks!

Re: CRD - dumped footage on external drive - how to preserve date / time metadata

AtticusLake — Tue, 05 May 2026 09:13:51 GMT

I don't have a C500, and I've never used CRD before (I just load RAW files into Resolve), but I've had a go at testing this with my C80, and here are my results.

In CRD, in the menus, check "View -> Clip Information". Select your clip. Under "Recording Date/Time", it shows the date/time the clip was actually recorded. See first screenshot.

Note that the "Recording Date/Time" is 08:51:56, whereas the Window "date modified" for that file (second screenshot) is 08:52. That's when the file was last written to, as opposed to when you pressed record.

The good news here is that this is the recording date/time stored as meta-data inside the file, by the camera, so it isn't fragile like the operating system's meta-data. The bad news is that it's up to the camera to store this, and not all cameras do. Clearly the C80 does; as for the C500, I have no idea. If the camera doesn't save that information, then it's not there, and I don't know what else to tell you.

I know it's frustrating to see the date/time you want on the files on the memory card, but again you need to know that those date/times are about the physical files, not the movies stored inside them. When you copy a file, that copy is a new file, and may be set with its own date/time.

Windows keeps three times for a file: "date created", "date modified", and "date accessed". In my tests, the "date created" is the date/time at which a physical file was created -- i.e. the copy of a file. But the "date modified" generally seems to be kept as when the content of the file was last modified. This is close to what you want (though not identical), but whether it works for you, will depend on your computer and exactly how you copy the files. See second screenshot.

As I said, I generally just load RAW clips into Resolve. Resolve lets you see the date/time recorded for a clip, but not by default; you need to go to the media pool, right click on the column headings, select "headings", and scroll down the huge list of meta-data to "Shots & Scene", and select "Date Recorded". Again, though, whether this is actually there will depend on your camera. See third/fourth screenshots.

Again, I know this is frustrating, but I hope this at least helps a little.

Re: CRD - dumped footage on external drive - how to preserve date / time metadata

coyotegyrl — Tue, 05 May 2026 12:02:40 GMT

Hi again!

Yes the original dates and times are on the media when it is on the camera card. The camera most certainly records date and time. (see 'inside card' attachment, and 'inside CRD'). But when I process the clip in CRD, the resulting file does not have matching dates and times, it is the date and time that I processed the clip (see 'in finder after export).

This is a change from what happened previously on import. I have been shooting with this camera for many years and those dates were always correct in the past. I wish Canon would fix this.