![]() ![]() It is entirely possible to bring down a site if you’re not careful. But that is not recommended for the faint of heart. You can import and export a full database or just specific tables. One way to handle this is via backend software like phpMyAdmin. But when we want to access and take that information with us (and potentially import it into another site), it’s not always a simple task. Our posts, users, eCommerce orders, etc., live happily in a database. FCP XML (.Data portability is something that we don’t often think about until we need it. ![]() fcpxml (.xml seems to not work well for either multicam or sync-clips). The most reliable way I have found is avoid sync-clips in your workflow and to instead use multicam to sync audio & export. Some Resolve features such as using sync-clips to sync audio to camera footage result in the wrong audio being referenced in the XML. *Davinci Resolve XML exports have some limitations & can be quite buggy in terms of including the correct audio & channel metadata. See instructions for best Resolve AAF export and Vordio import settings. The correct export/import settings to use in Resolve and Vordio are important for good results. This is now the recommended format for transfer from Resolve to Reaper.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |