Render out multiple languages with subtitles on Export

Flame Flame Questions
, ,
1

I have been playing around with the new subtitle tool in Flame and it works pretty good but i am missing one feature.

So as an example:
On the first subtitle layer I have dutch subtitles (named: NL) and on the second layer I have English subtitles (named: ENG). I have also named these layers like that.
On export I can select either subtitle layer to render out but what I would ideally want is Flame to render out both versions.
I sometimes have loads of deliverables in multiple languages and i would be amazing to hit export and all sequences would be spit out accordingly.

So example could be: brand_project_final_ENG and brand_project_final_NL

Does anyone know a way to do that?

2

I was looking into this about a month ago with no luck. I agree, it would be nice to export all the cc tracks as .srt files in one swoop…instead of exporting them one at a time.

3

What you can do is when you open a sequence and do right click on one subtitle layer is say export all subtitles as srt files. too bad you cant do it from the desktop view.

4

My first clarifying question would be: are you referring to burned in subtitles or the exporting of a .srt file?

It might be because of my comfortability and preference toward connected segments, but I find myself much more frequently duplicating sequences and having explicitly separate timelines for different languages. This not only allows you to export out the multiple language versions at once like you want, but also allows you to keep their versioning separate for changes that might happen to one language and not another.

If this isn’t an option, then you’re probably in feature request territory of submitting an expansion to the Subtitle export feature to allow for the multiple exporting of a single sequence duplicated for each subtitle track, or the exporting of multiple sequences’ .srt’s at once.

There’s also a chance that Python could get you to where you need to go, although there’s also a similar risk where the exact functionality you need may not be completely integrated into Python just yet, which in that case you’d also be in Python feature request terrirory.