Case 1
Fluent-ffmpeg : works everytime, but impossible to fine tune HTTP headers
spawned command + FFmpeg : works if you add quotes to input options and source
The mp4 output file should be produced in each case.
Observed results
case 1 : the mp4 output file is produced.
case 2 (as I mentioned, implementing a small fix in /lib/options/custom.js produces the output file):
[NULL @ 0x559f0021c040] Unable to find a suitable output format for 'https://video.hosting.com/'
https://video.hosting.com/: Invalid argument
Error: ffmpeg exited with code 1: https://video.hosting.com/: Invalid argument
case 3 :
Unrecognized option 'headers User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.159 Safari/537.36'.
Error splitting the argument list: Option not found
Error: ffmpeg exited with code 1: Unrecognized option 'headers User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.159 Safari/537.36'.
Error splitting the argument list: Option not found
I know that I use FFmpeg 4.1 (can't update for now unfortunately), but I suspect this issue can be reproduced with FFmpeg 4.4 as well.
[x] I tried the same with command line ffmpeg and it works correctly (hint: if the problem also happens this way, this is an ffmpeg problem and you're not reporting it to the right place)
[x] I have included full stderr/stdout output from ffmpeg
Version information
Code to reproduce
Case 1 Fluent-ffmpeg : works everytime, but impossible to fine tune HTTP headers spawned command + FFmpeg : works if you add quotes to input options and source
Case 2 Fluent-ffmpeg : works with a small fix in /lib/options/custom.js spawned command + FFmpeg : works if you add quotes to input options and source
Case 3 Fluent-ffmpeg : never works spawned command + FFmpeg : works if you add quotes to input options and source
Expected results
The mp4 output file should be produced in each case.
Observed results
case 1 : the mp4 output file is produced.
case 2 (as I mentioned, implementing a small fix in /lib/options/custom.js produces the output file):
case 3 :
I know that I use FFmpeg 4.1 (can't update for now unfortunately), but I suspect this issue can be reproduced with FFmpeg 4.4 as well.
Checklist