Quote ffmpeg filter file names with spaces
A file name with spaces in subtitles=, movie= or fontfile= now reads the way ffmpeg reads it. A failed download names the input as you wrote it.
An ffmpeg command that burned subtitles from a file with spaces in its name, like -vf "subtitles='storage://media/My Show.mkv':si=0", stopped reading the name at the first space. The job downloaded storage://media/My instead and failed with a 404.
A filter option that opens a file now reads its value the way ffmpeg does. A space is part of the name. Only an unquoted :, ,, ;, [ or ] ends it. Each of these opens the same file, and a file named in both -i and the filter still downloads once:
subtitles='storage://media/My Show.mkv':si=0subtitles=storage://media/My Show.mkv:si=0subtitles=storage\://media/My\ Show.mkv:si=0
A failed download also reads better, in the dashboard and in the API response. It names the input as you wrote it, says what the server answered and what to check next, and no longer shows an internal placeholder or a long signed link:
Could not download input "storage://media/My": your storage answered 404 Not Found. The command splits this file name at a space, so ffmpeg was given only its first part. Quote the whole name once inside the filter: -vf "subtitles='storage://media/My Show.mkv':si=0"