> On 14 Apr 2021, at 16:14, adam smith via ffmpeg-user
> wrote:
>
> I will test again with the quotes through the script so it will fit in one
> command and get back to you.
Double quotes has saved the day. That is a nice easy fix.
Thank you Moritz you lovely man.
> On 14 Apr 2021, at 16:12, adam smith via ffmpeg-user
> wrote:
>
> I have included the quotes on the subtitle file path.
> If I use the url in a browser the SRT file is downloaded so I know the
> credentials are ok.
> Thanks for your help.
Looking at what I just did the test was rubbish as
>
>> You should show us the complete, uncut console output, without the
>> access key of course.
>
I have included the quotes on the subtitle file path.
If I use the url in a browser the SRT file is downloaded so I know the
credentials are ok.
Thanks for your help.
>
ffmpeg -y -ss 00:00.00 -to
> You should show us the complete, uncut console output, without the
> access key of course.
I will try again splitting up the command line so it fits in the command line
so I can get a proper output.
>
> It looks like you may be using Unix/Linux and your shell is
> interpreting '&'. You may
Hi Adam,
On Wed, Apr 14, 2021 at 14:15:48 +0100, FFmpeg user discussions wrote:
> [https @ 0x7f40de879b40] HTTP error 403
> Forbiddenhttps://some_domain.com/subtitles/18217/bf4130a3-64f8-40cb-aae8-720da75797a7.srt?AWSAccessKeyId=A*Z:
> Server returned 403 Forbidden (access
Hi group, hope you are all good.
I am trying to embed subtitles onto an mp4 and everything is working very
nicely thank you; except that the source location for the subtitle file is
going to change.
It was previously an open http url and the command looked like this…
ffmpeg -y -ss 00:00.00 -to
