just had my first foray into subtitles on Flame. Is this still in beta or something? seems very buggy. I load a SRT file from the client. go to the first one - make some changes and it doesnt always go across all of the subs in that l changed the size - only this one changed - even though I have all tracks selected. Also If I change the y offset - not only does it not transfer across all of them - but it zeros out - so you have no idea what the offset is if you needed to do it manually. The kerning is still terrible - just like in the text app. If I reboot flame after loading the SRT file then it seems to work across all subs, not everytime though.
I used it once. Now I convert the srt to xml and use a regular text layer.
Not in front of it - there is a dropdown that determines if your change is only for the a single title or the entire trick. Which is what you want. You want to be able to make global changes, and override individual ones.
Isn’t there a learning channel video when this was launched? Maybe worth a watch…
Not in beta anymore. Though the text render quality is a known limitation.
I’ve used it on a few projects and had no issues.
Text quality was my major issue. All I needed on last-looks before shipping was some art director wondering why they looked so bad, then I would need to start from scratch anyway.
Bear in mind, I’m short form, so at most I have about 10 titles in a 30 second spot. The average seems to be about 6, so manually going through each one to refine isn’t a big deal.
No, sadly that video was skipped. I have asked around about retroactively making a video on this subject for this very reason so maybe one day!
like I said in my post - im using the dropdown entire track. which is why I think there is a problem
Edge quality still too aliased. Run the xml or srt through Premier and send a flat QT to Flame. We have a client who obsesses over their subtitles.
I generally do my timeline titles as a BFX (I keep a template in my node bin) at double the final size, then reduce by 50% with EWA filtering. Even thin fonts look fine and the extra work is still much less than having to bounce between applications for revisions.
its such a shame that text in flame is so bad. I mean shockingly bad. and has been as long as I can remember. im going to have to do these subtitles in resolve!
Premiere also has very decent subtitle tools. Actually most robust of all of them at the moment, including when you need to embed subtitles.
We (where I am) do all our subs in Premiere and export as a keyable. This is more for a divide and conquer workflow over other reasons.