Copy link to clipboard
Copied
I have noticed a very strange occurance with the created date on transcoded ProRes 422 files. I have a batch of 8-bit uncompressed MOV files which I transcoded in Media Encoder 14.3 to both ProRes 422 and MP4 files. The MP4 files transcoded fine with the correct time and date created stamps. The ProRes 422 on the other hand are stamped with incremental date stamps starting with 07-04-2020 and ended with 07-06-2020. I started the batch yesterday afternoon 6-30-2020 and it completed early morning hours of 07-01-2020. It seems every three to four hours as the transcoding chugged along the date would increment for each file created. The time and date on my computer is correct and I'm running windows 10 pro. I have not tried other file formats but I did a test to make sure it was not a fluke with the batch. The file created still gave me 07-06-2020 created stamp. Has anyone else run into this bug on 14.3? I have never had it happen before this update. Thanks.
I am happy to announce that the issue is fixed in Adobe Media Encoder (Beta) since 25.0.0.30.
Copy link to clipboard
Copied
Same issue on AE 16.1.3 Build 5, though I hadn't noticed it was an issue with Prores 422, Thank you.
Copy link to clipboard
Copied
Yep - this is happening to me also. Happening since updating to AME 14.3. Tried encoding on two different workstations and the issue is replicated.
Chris
Copy link to clipboard
Copied
I'm having the same issue here on Windows 10 with 14.3.1. I look forward to Adobe fixing this bug in about 12 years.
Copy link to clipboard
Copied
Have only just noticed this happening as well - normally delivering Mp4 H264 files for clients without an issue, but needed to produce some 4444 and 422 Pro Res files for a client today and yes, they are dated varying dates approximately a week into the future. Windows 10 1909 Build 18363.1082 and latest patch of AME 14.4 Build 35
Copy link to clipboard
Copied
I see it here as well. There are several date options in Explorer and the default, "Date" shows wrong date as well as "Media Created" while "Date created" and "Date modified" shows the correct dates. Insane...
Copy link to clipboard
Copied
Same issu on Mac with Media Encoder 14.5.
Copy link to clipboard
Copied
Is nobody fixing this? This is driving me crazy!
Copy link to clipboard
Copied
I have filed a bug on this. Sorry for your inconveniences.
Copy link to clipboard
Copied
Thank you.
Copy link to clipboard
Copied
I was not able to repro in Adobe Media Encoder (Beta) 24.5.0.10 on Windows 11. I was transcoding a file to QuickTime ProRes 422. Creation date was set correct. What is your workflow?
Copy link to clipboard
Copied
I am using Adobe Media Encoder 24.3 the latest version. My work flow is that I send every project to AME and render it to ProRes 4444 or ProRes 422 and always creates date two days in the future and I also render one version in H264 and thats creates the right date.
Copy link to clipboard
Copied
Can you add your specs (OS, CPU, GPU, memory)? Thanks!
Copy link to clipboard
Copied
Windows 11 latest update, Intel i9-10900k 3,70Ghz, Nvidia Geforce RTX 2080, 64Gb. Everything is updated with latest drivers and Bios update
Copy link to clipboard
Copied
To add to this, using Windows 10 latest update, Intel i7-9700k 3,60Ghz, Nvidia Geforce RTX 4090, 48Gb. Everything is updated with latest drivers and Bios update.
I am using the render queue on After Effects 2022 and noticed (per the attached) that when a prores file is being rendered, the date in windows explorer is correct, BUT as soon as the render completes, the date changes to 2 days in the future. (named ANL_VFX_R1_040_FINAL_V01_TEST.202404291300.mov for reference and rendered on apr 29 at 13:00 PT)
Copy link to clipboard
Copied
I have filed a bug. Will add this thread to the bug sdo that I can notify you once we have news. Thanks for letting us know.
Copy link to clipboard
Copied
I am happy to announce that the issue is fixed in Adobe Media Encoder (Beta) since 25.0.0.30.
Copy link to clipboard
Copied
I am happy to announce that the issue is fixed in Adobe Media Encoder (Beta) since 25.0.0.30.
By @EckiAME
Yes, i did the same test again and now it works as expected! 🙂
Find more inspiration, events, and resources on the new Adobe Community
Explore Now