Premiere 13 has incorrect timecode for Sony a7sII clips
Premiere 13 has been exporting broken XMLs that don't work in Premiere 12 or Resolve. I finally figured out why: look at the source window monitor on the left (Premiere 12) and on the right (Premiere 13). 10 seconds and some frames off. Resolve lines up with Premiere 12's timecode.
Thank you for reporting this issue. It is now resolved in Premiere Pro 2019.1. Please let us know if this update does not resolve the issue for you.
-
Devon Stanczyk
commented
Having this issue too with several project files. Most of my clips from the Sony a7s1 are also "slipped" out of the original edit. Very frustrating, and time consuming when making revisions for clients.
-
Anonymous
commented
Having this same problem Dec 12 with a project we created in version 12.1.2. Now working in v 13.0.2 and its an issue with all footage shot with a7sII. Is there any fix other than trying to roll back to version 12.???
-
Benjamin
commented
It is a problem with how Preiere 2019 reads / handles MXF timecode for 23.976 FPS files.
This is a MAJOR bug!!!!!
-
Pruth Shankarappa
commented
Thanks Brandon, for the additional info. Since the frame rate of 23.976 matches a known issue with these files, we are already tracking this issue internally. We will be able to update you once we have a fix for it. Sorry again for the inconvenience with these clips.
-
Wade Dunstan
commented
Having the same issue when opening and attempting to work on many projects that were started in Premiere 12, basically all Sony camera's timecode is being misread which means every clip is mistimed and making projects completely unworkable, but when opened in Premiere 12.1.2 they work fine. Hoping for an update to fix this issue ASAP.
-
Brandon Freeman commented
Note that this issue only happens with Sony XAVC-S clips, and only in Premiere 2019.
-
Note that I've also tested GoPro footage at 23.976, ProRes at 23.976, and even some Lumix .MP4s I've found at 23.976, and none seem to have the problem that every Sony a7sII clip I have exhibits in Premiere 2019. So I think there is something going on with Premiere's handling of Sony's XAVC-S codec, and the issue started in this release (Premiere 2018 is just fine).
-
Hi Pruth,
Here are the properties Premiere reports on this clip. Is that what you're looking for?
File Path: F:\COLLIERS OUTLOOK 2019\AUDIO-VIDEO\Sony A7sII\PRIVATE\M4ROOT\CLIP\C0009.MP4
Type: MPEG Movie
File Size: 17.95 GB
Image Size: 3840 x 2160
Frame Rate: 23.976
Source Audio Format: 48000 Hz - 16 bit - Stereo
Project Audio Format: 48000 Hz - 32 bit floating point - Stereo
Total Duration: 00:27:02:00
Pixel Aspect Ratio: 1.0
Alpha: None
Video Codec Type: MP4/MOV H.264 4:2:0 (Full Range) -
Pruth Shankarappa
commented
Hi Brendan,
Sorry for the inconvenience. Is your source 23.976 FPS? We have seen a similar issue with that frame rate and so want to get more info on your issue to understand it better. If you can share a MediaInfo data on this file that would be helpful as well.
Pruth