> It was similar? But not identical?
It was the same exact checksum. They were identical, indistinguishable,
interchangeable, like two peas in a pod
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
To
2018-09-13 8:05 GMT+02:00, Zaid Amir :
>> Every video file or only certain types?
>
> I am only interested in H264 encoded
I don't know if the issue is the file reading or the demuxer,
feel free to test a few different file types like avi, asf, mov,
mpegts.
> files which I have so far tried aroun
> Every video file or only certain types?
I am only interested in H264 encoded files which I have so far tried around 40
of them and they are all failing. Did not try other encodings though as they
are of no interest to me.
>Can you run "md5sum" on the target system?
Lambda does no have md5sum i
2018-09-12 16:27 GMT+02:00, Zaid Amir :
>> What does not work?
>
> If I provide a valid video, it fails with the errors shown in
> the logs from the original email.
(And I assume the output is wrong, no?)
Every video file or only certain types?
Can you run "md5sum" on the target system?
Carl Eu
> Do the jpg files look as expected?
The generated jpegs look identical. Color bars with some scattered pixels and a
diagonal bar going through them
> What does not work?
If I provide a valid video, it fails with the errors shown in the logs from the
original email.
__
2018-09-12 8:01 GMT+02:00, Zaid Amir :
> Running ' ffmpeg -f lavfi -i testsrc2 -vframes 10 out%2d.jpg'
> gives this output:
Do the jpg files look as expected?
What does not work?
(Is it file input that is not working?)
Carl Eugen
___
ffmpeg-user mailin
> Did you use the *identical* input file in both environments (the successfull
> and the failing env)?
Yes I did, and tried multiple files all fails on lambda but succeed on the EC2
instance.
>Did you use the identical ffmpeg binary in both environments? E.g. the
>ffmpeg-4.0.2-static johnvansi
Yes I am testing on the same file both on the EC2 instance and lambda function.
Running ' ffmpeg -f lavfi -i testsrc2 -vframes 10 out%2d.jpg' gives this output:
ffmpeg version N-91639-g85c0064 Copyright (c) 2000-2018 the FFmpeg developers
built with gcc 4.8.5 (GCC) 20150623 (Red Hat 4.8.5-28)
con
On Tue, Sep 11, 2018 at 14:17:37 +, Zaid Amir wrote:
> As I explained I tried both static and dynamic.. of course ldd does not work
> on static binaries.
Going one e-mail further back:
2018-09-10 10:19 GMT+02:00, Zaid Amir :
> Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/home/ec2-user/f1.mp4':
2018-09-11 16:17 GMT+02:00, Zaid Amir :
> As I explained I tried both static and dynamic.. of course ldd
> does not work on static binaries.
ldd works fine on static binaries, it tells you that they are static
binaries.
The point is that in your original mail, you gave the impression
that FFmpeg w
g user questions
Subject: Re: [FFmpeg-user] FFMPEG failing in AWS Lambda
2018-09-10 10:19 GMT+02:00, Zaid Amir :
> Well its very likely I'm afraid.
>
> Below is the output when converting a single frame to jpg on my build
> environment, this fails when run in Lambda.
>
> ff
2018-09-10 10:19 GMT+02:00, Zaid Amir :
> Well its very likely I'm afraid.
>
> Below is the output when converting a single frame to jpg on my build
> environment, this fails when run in Lambda.
>
> ffmpeg version N-91639-g85c0064 Copyright (c) 2000-2018 the FFmpeg
> developers
> built with gcc 4
pient you are notified that disclosing, copying, distributing
or taking any action in reliance on the contents of this information is
strictly prohibited.
-Original Message-
From: ffmpeg-user On Behalf Of Carl Eugen Hoyos
Sent: Tuesday, September 4, 2018 1:41 AM
To: FFmpeg user questions
Su
2018-09-02 7:49 GMT+02:00, Zaid Amir :
> Static builds of FFMPEG are failing in AWS lambda.
This sounds very unlikely.
Please at least provide the console output your binary
produces on your build system and also "ldd ffmpeg"
output.
Carl Eugen
___
ff
Hi,
Static builds of FFMPEG are failing in AWS lambda. I am trying to create a
transcoding function for short videos. The function is hosted on AWS Lambda.
The problem is that AWS lambda seems to be missing something that FFMPEG
requires, at least according to Amazon.
I contacted Amazon ear
15 matches
Mail list logo
