site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com Hi Helena, My 2 cents, Rainer for full control, on both existing and non-existing TC tracks, there should be a flag that you can turn on and off and that decides if file or XML wins. This could work like the updatebehaviour flag for QT metadata. In the latter case the actual Quicktime files should be changed/overwritten. I don't see the use or benefit of a situation where you have one TC assigned to a clip in the QT file, and another one in FCP. That is bound to become a problem later on in people's workflows. In other words, I would like to see an optional behaviour where the TC in the Quicktime does get overwritten. That flag should off course default to off, or file wins, and maybe there should be a warning in the user interface upon import. P.S. What should I expect to see when I import clips with all 3 timecodes and have them batch capatured? Will the aux TCs from the XML migrate into the Quicktime file? _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.ap... This email sent to site_archiver@lists.apple.com