2 Replies
Bob O'Donnell

At first glance of the file, the timing looks off to me. Did you alter the original? Usually YouTube is good with generating timing and bad with language (spelling). Make sure you read any files generated from YouTube carefully.

You can set the timing yourself using the time code in a video player or Storyline itself, the video editor will show you time code.

The time where one caption ends and the other begins can't overlap. If you look at the current time code for line 1 and line 2, line 2's timing falls in the middle of line 1. On a basic level, the end time of line 1 should match the beginning time of line 2. In this case, if line 2 actually starts at the stated time of 02,820 then the end time for line 1 (04,740) should actually be 02, 820.

1
00:00:00,079 --> 00:00:04,740
the model of team effectiveness is based

2
00:00:02,820 --> 00:00:07,259
on research that has been conducted on

The time text is up on screen can't overlap. It will give you the exact error you are seeing. In the example below, lines 1, 2 and 3 will show up back to back with no missing text. The end time of one line matches the start time of the next.

1
00:00:00,079 --> 00:00:02,820
the model of team effectiveness is based

2
00:00:02,820 --> 00:00:07,259
on research that has been conducted on

3
00:00:07,259 --> 00:00:09,780
teams to determine major factors that

You can watch your clip and get a rough time as to when your audio starts/ends and then reset the end times and start times in your SRT file. Fortunately, your clip isn't too long.

Katie (Gokhshteyn) Riggio

Hi there, Arthur!

It looks like you got some solid community advice – and great call to also open a support case. I took a peek at your conversation with my teammate, Cleo, where he logged this behavior as a possible bug: When importing .SRT files for Closed Captions (CC), if the CC line duration overlaps with other lines, it will not display.

For now, the workaround will be to go to the Video Tools tab and use the Closed Captions: Import option.

Import

I'm going to tag this discussion, so we can keep you updated with any new information here, too. Thank you for bringing this oddity to our attention!