search

CommandPost / FCPCafe

FCP Cafe Website
https://fcp.cafe
MIT License
27 stars 15 forks source link

Final Cut Pro 10.6 won't import FCPXML with certain region settings #62

Open latenitefilms opened 2 years ago

latenitefilms commented 2 years ago

Philip Hodgetts reports:

ALERT: FCP 10.6 XML Import Problem. Don't upgrade if outside USA, UK or Australia. Andreas Kiel discovered that he could not import XML into FCP 10.6 (this week's release). We could not repeat the problem on either M1 or Intel Macs with FCP 10.6. I observed that the problems where happening in Europe. As well as Andreas' issue we had an Intelligent Assistance customer in Italy report. It seemed like it was a ridiculous ideas, but detailed testing by Gregory Clarke tracked it down to Region and Language settings. If Region is set to anything other than USA, UK or Australia, and language is not English (of those three countries) the XML import will fail. Workaround: Before importing XML to FCP 10.6, change Region to USA and language to US English. Import the XML. Revert to your preferred Region and Language. We've been in close contact with Apple sending in our observations and it is in front of engineering for resolution. Given they have to identify the issue, fix it, navigate through Quality Assurance, then get into a release, I would expect it to be a little while before there's an official resolution. Philip

latenitefilms commented 2 years ago

Andreas Kiel writes:

Thanks Philip & Greg! I got a lot of customers complaining xml doesn’t work anymore. One of the reasons seems to be the language/region settings. But it’s not all. Depending on content XML import may seem to work but silently fails without notification- regardless of language and or regions. To me it’s more a kind of XML parser error somewhere deeper. Better stay away from 10.6 if you’re working with XML

latenitefilms commented 2 years ago

Philip Hodgetts writes:

Further to the FCP 10.6 XML Import issue some have found. My incredibly clever husband (and coder of all our apps) has tracked down the problem to the specific Swift interpretation of the XML (in the new Swift XML importer). The reason it is affected by Region (sometimes) is because Swift interprets numbers appropriately for the Region. Regions that use a comma (,) as a decimal indicator in numbers fail, Regions that use a period (.) pass. The seemingly variety of different symptoms or workarounds are all related to Swift interpretation. Or so it seems as of right now. 🙂 All props to Gregory Clarke for discovering this new information after one of our customers reported that the workaround didn't work for them. They had a different specific but still related to the interpretation of the XML by the new parser in 10.6. All information shared with the caveat that none of it is official. We share our findings with Apple and they are working on the problem, but we await the official word and solution from them.

latenitefilms commented 2 years ago

Andreas Kiel writes:

Some update on the 10.6 XML problems. After spending some more hours and reading mails and testing samples from more users: 'Captions' are one of the offending things. Most of the non working XMLs work regardless of language/region settings if the don't include captions. The other 'no-go': XMLs with 'too old' fcpxml versions. I haven't found enough time to test the limit.