25p footage imported as 25i in version 13.1.0

Report · Apr 11, 2019

Hello!

As the titles says, my 25p AVCHD footage, shot with a Sony FDR-AX53, started getting imported as 25i since the PP 13.1 update. It still imports correctly as 25 into PP 12.1.2.

I tried submitting a bug report, but, as far as I can see, unless a crowd of people encounters the bug and upvotes my report, nobody is even going to notice it.

Any ideas why this is happening and how I could fix it?

Thanks in advance!

Report · Apr 11, 2019

A bug doesn't necessarily need votes to be seen. To the best of my knowledge, every submission is reviewed by someone on staff.

Report · May 06, 2019

Jim_Simon wrote
A bug doesn't necessarily need votes to be seen. To the best of my knowledge, every submission is reviewed by someone on staff.

It seems you are wrong: after emailing back and forth with Adobe Support, until they finally understood what the bug is (as far as I can see, their support people are not at all familiar with their products), they recommended me to "please write us on the below wish form

https://www.adobe.com/products/wishform.html", meaning my bug report has not been even noticed.

Report · May 06, 2019

Please write your bug here.

Premiere Pro: Hot (1864 ideas) – Adobe video & audio apps

Report · May 06, 2019

https://forums.adobe.com/people/Ann+Bens wrote
Please write your bug here.
Premiere Pro: Hot (1864 ideas) – Adobe video & audio apps

OK, I posted again.

Is the idea that double posting means double chances to be noticed? Or that the reports will say 2 bugs have been fixed instead of one?

Report · May 06, 2019

The latter is monitored by Adobe engineers.

Still be one bug.

Report · May 08, 2019

Thank you for the information and posting a sample clip. I have also confirmed that Premiere Pro 13.0.x and earlier versions report the supplied clip as being progressive, but 13.1.x reports it as interlaced, yet MediaInfo does report it as being interlaced. I have logged this issue for further investigation from our Developers.

When you imported the AVCHD clips, did you import them from the Media Browser and from within the camera generated structured folders? There is often metadata that Premiere Pro reads from these folders that determines how they are imported. If so, would it also be possible to supply us with a sample structured folder that was created by the camera? (copied straight from camera, not modified at all) This will help us with our investigation.

I also saw your post in User Voice and replied there as well. The added information and sample clip in this post was very helpful.

Thank you.

Report · May 09, 2019

I copy all the files from the camera connected by USB to my Windows 10 PC, the connection being in MTP mode. In this mode all files are structured in folders by date, and their names reflect shooting date and time; also, files can be bigger than 2 GB. In mass storage mode (or if I just take the SD card out and plug it into a card reader) the files are all in one folder, named something like 00001.MTS, and longer clips are cut into 2 GB files (one of the main reasons I don't use this mode).

Anyway, I pulled the SD card out and copied the same clip directly from it, and the result is the same, the file is still interpreted as interlaced by Premiere Pro 2019, so I don't think the way I import them changes anything.

Report · May 09, 2019

Thank you for verifying all of this.I wanted to make sure this wasn't an issue with importing a loose clip versus importing clip from within the structured folders produced by the camera.

Would it be possible for you to provide us with a sample structured folders as it was created on the camera? Doesn't have to be multiple clips or anything long, just a short sample file within the structured folders provided by the camera. This will help our Developers with the investigation and make sure we are comparing apples to apples with your experience.

Thank you, again.

Report · May 10, 2019

I don't understand exactly what you are asking for, could you give me a guide how to do it?

In the meantime, I just wanted to post a response from Adobe Customer Care regarding this issue:

"This email is in reference to your open case premiere pro file interpretation. As discussed with you we have escalated the case to our Senior expert team and they researched on your case and we have found the root cause of the issue.

We would like to inform you that why application is interpreting the footage as Interlaced, because Mediainfo says the video is marked as:

Scan type : Interlaced

Scan type, store method : Interleaved fields

Scan order : Top Field First

And the camera is putting the metadata incorrect as it is showing in metadata details and premiere pro referring the same metadata from source and responding according to that.

We request you to please get in touch with manufacturer of the camera from which the clips are shot to inform the same to them, to check the metadata writing issue. "

Basically, they are blaming it on Sony, practically declaring that all previous versions of Premiere Pro, as also other editing software (I have only checked with Resolve, but it does open the file correctly, both versions 15 and 16 beta) are wrong, PP 2019.1 is the only software that sees the truth behind metadata.

Report · May 10, 2019

Trent wants you to film a couple of takes and send him the top folder from the camera.

Report · May 10, 2019

https://forums.adobe.com/people/Ann+Bens wrote
Trent wants you to film a couple of takes and send him the top folder from the camera.

In MTP or Mass Storage mode? Because in MTP mode the only folders are for each day in the format of YYYY-MM-DD, no sub or parent folders.

Anyway, I think I found the issue here: according to Resolve, the files are 1080PsF 25; it would seem PP 2019 does not interpret PsF correctly and treats it is regular interlaced.

Report · May 10, 2019

Ah Jim mentioned that in post 21.

PostVideoCoallition had a good article on PsF but its gone now.

Report · May 10, 2019

Yes, he has, but I only now found a way to see that the files are indeed PsF; unfortunately the tool I relied on for this (MediaInfo) proved to be unreliable, as it also shows my files as interlaced.

Report · May 10, 2019

Mediainfo does not understand PsF so it interpreted it correct as being interlaced (with both fields containing the same information)

In short you need to set up a 25p timeline and interpret the footage to progressive.

Report · May 10, 2019

https://forums.adobe.com/people/Ann+Bens wrote

Mediainfo does not understand PsF so it interpreted it correct as being interlaced (with both fields containing the same information).

I'm sorry, but when has MediaInfo become a standard; since when if MediaInfo does not recognize something - that something is wrong? PsF is recognized by Rec. 709, it is a valid transport scheme, used by multiple manufacturers of video recording equipment. The problem is in MediaInfo, not everyone else.

Saying that that "Mediainfo does not understand PsF so it interpreted it correct as being interlaced" is like saying that Trump does not understand climate and is stating correctly that global warming is not happening.

Report · Apr 11, 2019

Any ideas why this is happening and how I could fix it?

To fix it, right click on the clip/s in the Project panel and choose Modify > Interpret Footage and under Field Order, select "Conform to:" No Fields (Progressive Scan) and click OK.

Report · Apr 11, 2019

Of course this is an option, but when you're editing maybe tens of videos (separately or as part of a clip) - then this is not a good option. It is a workaround, but I would prefer a fix.

Report · Apr 11, 2019

Until Adobe fixes it you can manually edit the Interpretation Rules.txt located in C:\Program Files\Adobe\Adobe Premiere Pro CC 2019\Plug-Ins\en_US. Instructions can be found in the file

It is easy to set this wrong in the camera so before you change this for Premiere Pro, make sure that the camera indeed is set to 25i.

Report · Apr 11, 2019

Thanks for the tip, I will check what I can do with that file.

As for the camera: it doesn't even have a 25i mode (I never even thought this is usable); and the same file imported in PP 2018 is interpreted as 25p, but in PP 2019 13.1.0 is interpreted as 25i.

Report · Apr 12, 2019

As for the camera: it doesn't even have a 25i mode (I never even thought this is usable); and the same file imported in PP 2018 is interpreted as 25p, but in PP 2019 13.1.0 is interpreted as 25i.

According to Sony´s homepage it does have 50i. (25i and 50i is the same)

Report · Apr 13, 2019

Yes, it has a 50i mode, but not 25i.

Back to the solution though: I haven't been able to make it work. After several failed attempts I ended up with the most general rule *, *, 25, *, * = *, F, *, *, but the files still are interpreted as 25i. What am I doing wrong?

Report · Apr 13, 2019

Post screenshot of a clip analyzed by Mediainfo in treeview.

Report · Apr 13, 2019

https://forums.adobe.com/people/Ann+Bens wrote
Post screenshot of a clip analyzed by Mediainfo in treeview.

The weird thing is MediaInfo also reports the files is 25i, and I am almost sure it used to see them as 25p when PP saw them as 25p too (older versions of PP still do). On the other hand, exporting the file edited as 25i (as interpreted by PP 13.1.0) results in a visible loss of video quality, it looks like it was upscaled from a much smaller resolution, which again confirms that the file is indeed 25p (forcing PP to interpret it as 25p generates the expected normal result).

Report · Apr 13, 2019

Please post screenshot.