![]() They'd be able to cherry pick parts into the master and there can be a notation system for suggestions. If someone wants to check out an alternative edit, they can switch to that branch and play the timeline. There can be a master edit stored in this format and there can be a version control system where multiple people can branch and commit changes into the master edit. The quickest way to design a format would be for each major NLE developer to have an ascii project format and a group can find a way to express everything that's needed in an open timeline format. A program's specific settings could be stored in an auxiliary data portion but probably wouldn't be needed. It shouldn't be an exchange format like EDL, AAF but a project format. This would save file paths relative to a library root and each machine would set the root, which can be a shared library or local. If 3D apps can use complex formats like FBX, USD etc, there can be a standard timeline format in JSON or XML that FCP can save and Da Vinci, Premiere can open/sync the same timeline directly. There's no reason that editing apps can't all have a shared timeline description format. ![]() There's also a request for collaboration features, FCPX has a single-user library and they'd like to have shared libraries. The requests include a beta program for 3rd party tools to test them before updates come out. The only way this could feasibly be done is by open sourcing it but this would show how much active work is being done on it. ![]() The letter notes some of the requests, the original FCP wasn't cross-platform and isn't expected. "Industry-standard workflows" means totally cross-platform.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |