![]() Here are the MLT clip timings at two different frame rates: "in" = 0.000 and "out" = TimeOut - TimeIn Write a MLT "/mlt/playlist/entry" element with TimeOut = Ceiling(FrameOut * 1000 * fpsDen / fpsNum) / 1000 TimeIn = Ceiling(FrameIn * 1000 * fpsDen / fpsNum) / 1000 Write a MLT "/mlt/playlist/blank" element for BlankLength mlt would look something like this: Sort ( Subtitles In SrtFile By TimeIn )įrameIn = Truncate( * fpsNum / fpsDen / 1000)īlankLength = Ceiling((FrameIn - PrevFrameOut - 1) * 1000 * fpsDen / fpsNum) / 1000 The first subtitle with 29.97fps timings.Ĭonversion from. Here’s an example SRT file to illustrate: 1 srt timings to the actual frame boundary timings based on the project’s frame rate, all while not double-booking any frames. ![]() mlt converter is finding the frames that contain the subtitles and then shifting the. For all practical purposes, the XML file could have just as effectively used the frame number instead of milliseconds. The milliseconds used in the XML file are usually exact frame boundary timings, and not some random time in the middle of a frame. While the XML file may look like a milliseconds free-for-all (and technically can be), it really isn’t in practice. Here is another part of the issue: the Project (the xml in the back-end records whats going on) respects the time (like 00:00:04.956 etc.), but the Editor in the front-end respects the frame numbers. ![]() This is standard practice, not Shotcut-specific busywork. This means converting SRT milliseconds to a frame number, making sure that frame isn’t already used, then converting back to milliseconds. All else must be conformed to match it if frame alignment is going to happen. The output format is the authority, and whatever its frame rate is must be the king. srt timings as if they are the authority. ![]() When the math is round-tripped through a frame number, subtitles will remain frame-accurate even at the two-hour mark (which is the furthest I’ve tested them so far). The drift is due to frame math and is not related to Shotcut. (I’m following up on your post in the 25->50fps thread, and figured it would be more relevant over here.) srt importer and wanted to chime in, but didn’t have time to write up an example back then. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |