[Bug] DVR 19 imports xml are crazy

As you can see on figure, xml is 25p. (text_xml.png)
DVR Import xml offers 50p. (figure import_xml.png)
After import Timeline Settings is 25i. (timeline_settings.png)

For comparison, Baselight imports it correctly 25p.

If the incoming footage is interlaced, DR will de-interlace it into 50p to keep the temporal resolution while avoiding artifacts when scaling.

If the incoming footage is interlaced, DR will de-interlace it into 50p to keep the temporal resolution while avoiding artifacts when scaling.

As you can see in the first and second figures, the DVR imports 25p as 25i. The automatic deinterlacing how the project settings is that the DVR added in the last or the previous version has nothing to do with the problem with the subject. But thanks for trying to help.

If 25p is treated like interlaced, there’s something wrong with the flags.
Check your Clip Attributes and your timeline settings.

If 25p is treated like interlaced, there’s something wrong with the flags.
Check your Clip Attributes and your timeline settings.

Clip Attributes are for clips. You can see incorrect reading of parameters in xml already when importing xml. There are situations when you import in the first step without media and link them after importing xml. This gives you more options to choose conforming parameters. Believe me, sometimes even several xml/aaf per day.

My main concern is that someone from Blackmagic notices this bug and fixes it.

Which program is generating the XML files? Sometimes XML data does not state if it's progressive or interlaced so may be mis-interpreted by Resolve. XML interchange is not a defined standard and each company can implement custom versions if they wish. FCPXML is an example of a custom XML format.

You can manually edit the XML to "none" for interlacing which helps. I have also found that the 50p change also affects the ability to re-link as well.
Premiere 24 & Resolve 18 seemed to be more consistent in my exp.
In an adjacent issue -I'm having problems with Multi-channel audio in Premiere / XML /Resolve - having incorrect channel assignments. Easily fixed by manually re-assigning in the sequence BUT not keen to do that for a large sequence....

Which program is generating the XML files? Sometimes XML data does not state if it's progressive or interlaced so may be mis-interpreted by Resolve. XML interchange is not a defined standard and each company can implement custom versions if they wish. FCPXML is an example of a custom XML format.

We get xml from many sources. Mainly from NLEs but also from Autodesk, Baselight, Assimilate Scratch, Apple and others. The biggest problems we have now are from Adobe. In the past it wasn't this crazy.

You can manually edit the XML to "none" for interlacing which helps. I have also found that the 50p change also affects the ability to re-link as well.

This solution is not applicable to our work, but out of curiosity I will try it and let you know the result.

Premiere 24 & Resolve 18 seemed to be more consistent in my exp.

I very agree.

You can manually edit the XML to "none" for interlacing which helps. I have also found that the 50p change also affects the ability to re-link as well.

So I don't find word like Interlacing, Interlaced etc. inside xml.

Its not a resolve bug, it's a recent premiere bug.

Its been fixed in the latest beta version I believe, not sure if a stable release has the fix yet

A work around is to request AAFs from premiere.

Its not a resolve bug, it's a recent premiere bug.

We thought so too, but over time it turned out to be a bug on both sides.

A work around is to request AAFs from premiere.

This is not always possible in our practice.