New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Batch replace clips in a timeline #3295
Comments
I wonder if we could make a FxPlug for VFX versioning? Basically just have a “VFX Generator” in the timeline which you then set up some logic to always grab latest version? For example, rather than having a clip in the timeline, you'd just have a FCPX Generator. In the Inspector for the Generator, you would define the path to the folder which contains the VFX shot, and also the file naming logic. It would then grab the latest version of the clip in the folder, or you could override it with a specific version number, etc. When it comes times to "bake in" these generators, we could make a Workflow Extension to replace the Generators with whatever clip was set in the Generator. This could be a standalone app, or a CommandPost tool. |
Sounds like a very interesting approach. Ideally I'd want to have the clip in the timeline immediately as sometimes you'd need to go back to a previous version or need to check which version is cut in. "Finalizing" the generator after each new batch would take away the automation purpose. Maybe the generator approach is a good way, would need to test it. Defining one folder probably wouldn't cut it as we receive them in batches and I need to keep them in subfolders ("date-delivery#") as I receive them from the vendor. Not sure what's possible, but here's some other ideas:
|
Batch replace clips in a timeline for new VFX Submissions. When I receive new versions I'd like to replace the old ones (matches beginning of the Name "SPA_001_0010_v001", version v001 should be replaced by any higher version count). Similar to "Relink to open bins" in Avid - https://www.youtube.com/watch?v=gbReqyofLLE&list=PLlCB-pOMnhtWfurh_EA9qyHgt7Cm4SbUL&index=38&t=1503s
The text was updated successfully, but these errors were encountered: