External subtitles (.srt) on transport stream (.ts) files produces "Video Error"

[gdegough 0]

Using Server for Windows: Version 3.0.5597.1

 

This seems like it should be a simple bug to fix. My library is configured to use UNC paths. (e.g., \\Leanangle\D_Public\Videos\ArgusTV\...) When using the webclient, transport streams (.ts) play fine until I enable external subtitles (stored in same folder as .ts in .srt format). Then, I get a "Video Error: There was an error playing the video" popup.

 

Transcode logs say the ffmpeg cannot find the .srt file. The problem seems to be that the ffmpeg command is using forward slashes for the .srt file UNC path, but uses backslashes for the .ts UNC path name. The latter works, but the former fails, not finding the file.

 

I haven't tried yet, but I believe I can work around this behavior by changing back to absolute paths instead of UNC, but I thought someone might want to know.

 

Transcode logs attached.

 

transcode-139c11b3-f78d-4142-bf14-0a12509693ac.txt

transcode-2290a564-16a2-4277-945f-b5da324f6a81.txt

server-63566421178.txt

 

Thanks in advance!

 

-greg

[gdegough 0]

OK, the problem is not about forward slashes and back slashes (apologies for my assumption) and is about a single quote in the filename (part of the episode title). Still feels like an edge case that should be accounted for in command parsing, doesn't it.

 

-greg

[Luke 42080]

we'll have to figure out what the escape is that ffmpeg wants for that

[thefirstofthe300 292]

Ugh. That is kind of an ugly ffmpeg command to attempt building.

 

A simple backslash should fix this problem (at least on a *nix system it will).