6/29/2023 0 Comments Autokroma braw![]() If you are in this case, there are options in BRAW Studio (our Autokroma BRAW Plugin) to correct automatically those errors in the XML. When importing the XML in Resolve, it will be impossible to loads the clips with the wrong timecode (because the wrong timecode deduced with PPro will be exported into the XML and Resolve doesn't like when there is a wrong timecode). The problem with XML, is when the BRAW timecode is not good in PPro. ![]() An option for not loosing those change is to export the Settings in a sidecar file (there is a button for that in the Source Settings effect). ![]() You XML is still valid, but the BRAW Settings you changed in PPro will be lost in this XML. So that's totally fine and normal that you have this "error" in the report. In that case, you will see this kind of errors in the report after exporting XML ( Translation issue: Effect on Clip not translated). When you export your XML from PremierePro, the PremierePro effects can't be put inside this XML because they don't have equivalence between all NLEs (video editing softwares). It's a PremierePro effect which is used to change the BRAW Settings of your clip. When you import a BRAW file in Premiere Pro, there is automatically a "Source Settings" effect which is applied to the master tab of your ProjectItem.
0 Comments
Leave a Reply. |