Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
3

SRT subtitle parser bug on import

New Here ,
Sep 30, 2025 Sep 30, 2025

The SRT subtitle parser wrongly aborts on a line containing a sole number as the text of a subtitle. Reproduced on Adobe 25.4.1 and also 24.6.5 LTS, seems independent of OS.

 

A minimal example to reproduce would be the following SRT file:

1
00:00:01,000 --> 00:00:01,500
First subtitle correctly parsed.
Even with two lines.

2
00:00:02,000 --> 00:00:02,500
Only this line parsed. In the year
2025

3
00:00:03,000 --> 00:00:03,500
This subtitle and rest of file ignored.
Due to sole number on the 2nd line above.

See attached screenshot for the results of importing the above SRT.

Bildschirmfoto 2025-09-30 um 16.27.23.png

Just as a theory of what happens: The parser code treats the sole number on a line as an ID for the subtitle (despite not being preceded by a blank line) instead of as a part of the subtitle text. Then it aborts because the sequence of IDs is out of order or more likely because it's in the state of "new subtitle object started" and no timecode follows.

Bug Acknowledged
TOPICS
Import and ingest
79
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Pinned Reply

Adobe Employee , Sep 30, 2025 Sep 30, 2025

Hi @Beat Vontobel, Ringier

Thank you for reporting a problem and for the clear steps provided. I can also reproduce this issue and will file a bug with the team. Thanks for the workaround @Stan Jones.

Sorry for the frustration, 
Dani

Status Acknowledged
Translate
2 Comments
Community Expert ,
Sep 30, 2025 Sep 30, 2025

Upvoted. I can replicate.

 

Workaround: add a space after 2025. But the problem is detecting such errors without them occurring first!

 

Stan

 

Translate
Report
Adobe Employee ,
Sep 30, 2025 Sep 30, 2025
LATEST

Hi @Beat Vontobel, Ringier

Thank you for reporting a problem and for the clear steps provided. I can also reproduce this issue and will file a bug with the team. Thanks for the workaround @Stan Jones.

Sorry for the frustration, 
Dani

Status Acknowledged
Translate
Report