stuff like that … I just never came across anyone using this for figuring out what audio file wasnused when encoding the video .
I just would love it so much to have that info… using whatever tool just want to hear ideas, renaming files isnt a option as our clients often demand their custom file naming on delivery
maybe kicking out a seperate metadata file like a xml/edl from flame as a sidecar file could work? misuse the srt or dolbyvision functions?
I usually put our job number and/or a version ID in the Comments for the whole file so when a client inevitably renames the file and sends it back to us 2 years later (“Can we revise this vid?”) I can figure out what project it’s in… but I’ve not done it at a track level like that.
You could potentially name each channel in the audio metadata with the original filename of the source. Unless named when the file was output though, there wouldn’t be a way to find it out.
@finnjaeger -
Consider exporting an aaf or xml file.
From here strip out relevant filename metadata.
Consider using some tool like ffmpeg to inject <comment> or <description> on a per track basis.
(This is just based on an idea of metadata tagging for .mp4)
i like the aaf idea, actually yea that could work, misus if the publish function to just render the timeline as one clip with fx (flatten all track) and a aaf or even just a edl should carry the metadata then use ffmpeg or whatever to inject the name of the audio track item to someplace in the exported prores
