Changes between Version 4 and Version 5 of HowToConvertYouTubeSBVtoSRT


Ignore:
Timestamp:
May 21, 2019, 9:36:32 PM (7 years ago)
Author:
omniplex
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • HowToConvertYouTubeSBVtoSRT

    v4 v5  
    3030SRT timestamps have the form `hh`'''`:`'''`mm`'''`:`'''`ss`'''`,`'''`nnn`, SBV timestamps use `h`'''`:`'''`mm`'''`:`'''`ss`'''`.`'''`nnn`.
    3131
    32 !YouTube is reasonably smart enough to detect and report simple errors, but you should make sure that timestamps do not overlap, i.e., the earliest ''from'' in the next caption can be the same as the ''to'' end of the last caption. Obviously the duration should be not too short, and it cannot be "negative" with a ''from'' later than its corresponding ''to''.
     32!YouTube is reasonably smart enough to detect and report simple errors, but you should make sure that timestamps do not overlap, i.e., the earliest ''from'' in the next caption can be the same as the ''to'' end of the last caption. Obviously the duration should be not too short, and it cannot be "negative" with a ''from'' later than its corresponding ''to''.
     33
     34The auto-generated SBV example shown above (downloaded from a !YouTube movie trailer) actually uses overlapping timestamps, and ''ffmpeg'' kept them as is in its SRT conversion, if you know more about this please add some info.
     35
     36''SMplayer'' using ''MPlayer'' is unsuited as a syntax check, e.g., it doesn't insists on file extension '''`.srt`''', anything including '''`.txt`''' goes, it accepts missing counters, and simply ignores timestamps greater than the duration of the clip. As of early 2019 !YouTube could not handle the latter, the upload failed without reporting an error.
     37
     38Hint for For ''Windows'' users, if your ''Chrome'' uploads fail with an unclear JSON-error use ''IE11'', or try the ''studio beta'' UI instead of ''classic studio''.