Exort-Preset for itt-Subtitles

[michi987654]

Is there a way in Subtitle Edit to always export ITT subtitles with the same formatting? I'm looking for an export menu where I can set the color to #EBEBEB, the language, etc. When I use “Save as ITT,” the result always depends on the source. If the source is ITT with tts:colrcolor="#EBEBEB" and the body style="normal" region="bottom," those settings are carried over. With other source formats, tts:Color=“white” is set, body style="normal" region="bottom," and, in addition, every subtitle in the body still gets region="bottom" or “top.” Is there a way to achieve a consistent export for every ITT file?

[niksedk]

Thanks for the detailed description - you are right, the ITT writer kept whatever header the source file carried and only built its own header for non-TTML sources, so the result depended on where the subtitle came from. And one top-aligned line used to put a region attribute on every line.

This is now in main (#16259) and will be in the next beta. With a subtitle open and iTunes Timed Text chosen as format, go to File > Properties...:

• Header source: choose Template file and pick an .itt (or TTML .xml) that has the header you want - for example one of your existing files with tts:color="#EBEBEB" and <body style="normal" region="bottom">. Its styles, regions and metadata are then used for every saved ITT file, whatever the source format was (SRT, ASSA, another TTML...). The window lists the template's styles and regions, the frame rate follows the current video, and the Language field overrides the template's xml:lang when set.
• Without a template, Default color, Default style and Default region now apply to the built-in header too, so an SRT saved as ITT gets tts:color="#EBEBEB" and <body style="normal" region="bottom"> directly.
• Preset: save the whole setup under a name (the icons next to the preset box) and pick it again later, like the presets in Batch convert.
• A line only gets its own region attribute when it differs from the body's default, so with region="bottom" on the body only top-aligned lines carry region="top".

Let me know if the template approach covers your workflow.

[michi987654]

This approach sounds perfect for my workflow. Thank you very much for quickly resolving my issue.
Best regards!!

[michi987654]

Maybe it would be a good idea to take a look at the batch converter for iTT here as well. When converting frame rates, we always keep the source's values for "drop mode", "frame rate", and "frame rate multiplier", rather than converting them to the new frame rate.

[niksedk]

Good catch, thanks - you are right. Two things were wrong here, both fixed in main now (#16285 and #16287) and will be in the next beta:

• When the ITT writer reused the header from an ITT/TTML source, it kept the source's ttp:frameRate, ttp:frameRateMultiplier and ttp:dropMode, even though the time codes are written as frames at the current frame rate. So after a frame rate change the header and the time codes disagreed. The header now always follows the frame rate the time codes are written at (as the built-in header and the template header already did).
• Batch convert's Change frame rate only rescaled the times, but saved with the source's frame rate. It now saves at the target frame rate, so e.g. 25 -> 23.976 gives ttp:frameRate="24", ttp:frameRateMultiplier="999 1000", ttp:dropMode="nonDrop" (and 29.97 gives 30 / 999 1000 / dropNTSC). This also applies to the other frame-based formats like EBU STL, SCC and D-Cinema.

[michi987654]

Thank you very much. I hope I’m not bothering you too much. I need to reorganize the subtitle editing process at our company. Until now, Annotation Edit was the tool we used on Macs, but we’re running out of older Macs on which it still works. It’s quite possible that I’ll have other requests for you down the line. You’re doing a great job. I’ll also make sure my boss makes a donation to support your great work.