[FFmpeg-user] Subtitle filter and filename with quotes and spaces

[Ramit Bhalla]

Okay will try it. But then help me understand a simple quotes around the path and file works fine for the -i parameter. No escaping etc. 

How is that?

On Jan 20, 2014, at 1:23 PM, Pavel Koshevoy <pkoshevoy at gmail.com> wrote:

> On 01/20/2014 08:41 AM, Ramit Bhalla wrote:
>> I've even tried this:
>> 
>> -vf subtitles='D'\:\\'MCEBuddy'\\'MCEBuddy
>> 2.x'\\'MCEBuddy.ServiceCMD'\\'bin'\\'x86'\\'Debug'\\'working0'\\'HD
>> Small'\''.srt'
>> 
>> and it still throws an error:
>> 
>> [NULL @ 04596620] Unable to find a suitable output format for
>> '2.x'\\'MCEBuddy.ServiceCMD'\\'bin'\\'x86'\\'Debug'\\'working0'\\'HD'
>> 2.x'\\'MCEBuddy.ServiceCMD'\\'bin'\\'x86'\\'Debug'\\'working0'\\'HD:
>> Invalid argument
> 
> Again, this has nothing to do with ffmpeg.
> 
> If you tried this command it would similarly fail:
> 
> dir 'D'\:\\'MCEBuddy'\\'MCEBuddy 2.x'\\'MCEBuddy.ServiceCMD'\\'bin'\\'x86'\\'Debug'\\'working0'\\'HD Small'\''.srt'
> 
> 
> It should become obvious to you by now, that windows command shell does not interpret the quotes.  If you have a space in the file path that you wish to pass as a parameter via windows command shell, then you have to prefix the space with an escape character.  On UNIX systems the escape character is \, on windows it's ^.  So, try that:
> 
> dir D:\MCEBuddy\MCEBuddy^ 2.x\MCEBuddy.ServiceCMD\bin\x86\Debug\working0\HD^ Small'.srt
> 
> and make sure the path is actually correct, that you didn't misspell it somewhere
> 
> Once you get the dir command to accept the properly escaped file path, then you can pass that file path to ffmpeg.
> 
> _______________________________________________
> ffmpeg-user mailing list
> ffmpeg-user at ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-user