If it's a 4% speed conversion, then you will need to retime each one. My subtile company charges extra, and will not convert it any possbile way.
If its a same time conversion, you might be able to cut and paste them in a final cut pro sequence. (confused by this?) It's a long story, but possible.
Encore will import a subtitle file. I would use Excel to convert the codes and export a new file. I see numerous references to convertors, but few if any were just converting timecodes themselves. I'd explore that.
I had hoped that only the subtitles that didn't begin at frame 00 would need adjusting (because they are in the vast minority).
But even the subtitles that start at 00 are about half a second off. Darn.
I hadn't thought about it that way. I wonder why they are off?
So a subtitle that starts at fps 29.97 00;00;02;00 should still start at 25fps 00;00;02;00. So why doesn't it?
Don't know, but I worked it out.
It seems like every 27 seconds, my subtitles are out of sync by +1 frames.
So at the beginning, they are in sync. But by the end they are 253 frames out of sync.
ie: at the start = synced
00:00:27 = 1 frame out
00:00:54 = 2 frames out
It would be nice if there was a subtitle tool out there to adjust my subtitles for me.
PAL is non-drop timecode, right?
It is important that your script files correctly specify the timecode for your project. The timecode you use depends on the television standard of the project:
- NTSC projects use drop-frame timecode, which separates the numbers with semicolons, as in hh;mm;ss;ff (hours; minutes; seconds; frames).
- PAL projects use timecode that separates the numbers with colons, as in hh:mm:ss:ff (hours: minutes: seconds: frames).
It was a DROPFRAME issue. Final Cut Pro X didn't export my NTSC version in DROPFRAME. Now it lines up.