Forum Discussion
Short closed caption are not being recognized by Storyline 360
rachelatkaiser I'm using Premiere Pro to generate the caption files off of the instructional video, so my generated .srt have real timings - Premiere Pro captures them according to the timing of the video's audio. But good catch on these two particular examples having unrealistically short durations - I took a further look and it looks like I had artificially shortened these two .srt timing markers to make the issue more obvious for investigation.
To see something with no alterations, please see the below .srt excerpt (which is taken from the actual instructional video file). I can't post the entire .srt file in this public forum but the excerpt below has the actual original timings. This shows that it takes roughly 1.4 seconds to read through "To give / us a specific goal", which makes more sense.
1_Sequence_excerpt.srt
15
00:00:46,346 --> 00:00:46,713
To give
16
00:00:46,713 --> 00:00:47,747
us a specific goal
17
00:00:47,747 --> 00:00:51,117
as to what to include in our baker report
we're creating from scratch,
To see what happens when imported, I've attached a Storyline file showing what happens when you import this .srt to a video. You'll see that it drops the initial "To give" caption. (To observe, click on the video, and in Video Tools Options click Manage Captions).
This is just one example, but I found other random drops throughout my instructional videos. The only common thread I could see between the dropped captions were that they were on the short side.
Gotcha. I see what you mean in this new file you shared. I think james598patton is right and this seems to be a Storyline-specific problem. I think it would be worth reporting it to them (even if it is a known issue, it's good to add to the pile). James's suggestion sounds good. I'm really sorry if you do have to adjust all these captions.
Thank you rachelatkaiser for the follow up, and I think that's a good idea. EricSantos , could you please add this to the discussion thread/ticket that already exists for this known issue? Also, could you share a link to the original thread/ticket so I can follow it for updates?
My understanding of Articulate's values is that you make users' time and productivity a priority, which is why you're putting a lot of effort into AI features. Given that, I'd like to make an argument to prioritize this fix: getting this captions issue fixed will have exponential effect on productivity for accessible courses and shouldn't take nearly as many engineering resources as a new AI feature. With this current issue, my workflow for getting closed captions added to a single course takes hours. When fixed, the workflow will take minutes.
Hi StevenBenassi LucianaPiazza , I wanted to follow up on this and ask if you could help with: 1) adding this to the discussion thread/ticket that already exists for this known issue? and 2) share a link to the original thread/ticket so I can follow it for updates? james598patton mentioned it's a known issue so wanted to be able to follow its progress.
