…or
the write node could extract the sequence folder name from the metadata of an imported clip that had been imported using a custom pattern browsing “sequence” token.
…or
the write node could extract the sequence folder name from the metadata of an imported clip that had been imported using a custom pattern browsing “sequence” token.
I find it so confusing that you’re able to generate these custom tokens but cannot recall them anywhere.
@knhn If there was a bit of python that could grab this token and use it in the write node path, that would be amazing!
Thanks! Though the Python part is not really an issue for us. It’s more that we’d like to see more advanced tokening built into the software before we tackle things like openclip.
Ah sorry… this thread is some black belt level publishing for sure. I can barely follow it.
I would approach it w a regex. You would right click a selected clip and launch the script, extract the details from the clip name, then create a new Write node based on it. I assume you would still use the <batch iteration>
token.
100%