If I’m understanding the conversation correctly, this Python script here will add the name of the current selected clip to the clip’s tags, so you can confidently rename it without losing the original name. If I understand everything correctly, in order to actually use these tags on export, we will need another python script (not attached here just yet) that finds the tags and uses them for the file name on export.
Just to take this one step further, it’d be cool to be able to inject the tags into the metadata for QTs.
I realize that’s more of a feature request but if one were to have two tags: internal_name:xxx_30_wip01_1203 and client_name:AD1234567 those could be dumped into com.apple.quicktime.comment and, at least for your master ProRes, it’d contain the needed information to be able to track the connection.
If the dev team agreed that com.apple.quicktime.comment would be the right place for that, then it could also be used when reading a file so anything within that metadata field is then translated into tags.
Finally, one could automate all of this via a CSV file…although, depending on your workflow, you might need a couple of steps due the your internal name. Once both of those are set, you could use another hook to rename the sequences to either name or, as Jef mentioned, rename on export but for that you’d need to export via a hook and not using the media panel.
I’ll make a feature request if others think this could be useful.
Yeah, the whole metadata discussion is obviously a much larger one.
For now, here’s FI-03653 to dump the tags into com.apple.quicktime.comment so we can keep track and/or do whatever with them. Lower hanging fruit I’d argue.
Totally possible using tags as well. A wee python hook could easily sort that out.
audio:xxx_30_FINAL_FINAL_02_SOFTAPPROVAL.wav
Then you could read that later. I sort of see using the idea of tagging + comment field as a dumping ground for whatever we want to be either referenced/used later on.
but then how can i write that out of flame automatically?
currently i am doing some “shazam style” matching against delivered audio files and I am injecting that into the h264 metadata that we auto-create from the exported prores files, objvipusly beign able to dump the data straight from flame would be better, is there a post render hook i could use maybe oO?
Right now you can’t. If the devs accept the idea of dumping whatever tag(s) you have set on a sequence into that metadata field, then one could write a hook that will put whatever audio file you have on the sequence into the tags.
So yeah, not possible yet. Just toying with some other ideas of how to leverage the tags outside the initial scope.
