On Mon, Aug 29, 2016 at 09:56:59PM +0100, Simon H wrote:
> thanks Michael,
>
> try the attached file. I assume the corruption came from email word
> wrapping?
likely
> or was there something else wrong?
[...]
> example:
> take 25.mp4 created with:
> ffmpeg -f lavfi -i sine=frequency=1000:beep_
thanks Michael,
try the attached file. I assume the corruption came from email word
wrapping? or was there something else wrong?
simon
On Mon, Aug 29, 2016 at 6:11 PM, Michael Niedermayer wrote:
> On Mon, Aug 29, 2016 at 11:08:36AM +0100, Simon H wrote:
> > crypto allows reading of data which
On Mon, Aug 29, 2016 at 11:08:36AM +0100, Simon H wrote:
> crypto allows reading of data which has been aes-128-cbc encrypted given a
> key and an iv.
> But it did not handle filetypes which require seeking... e.g. it failed on
> an encrypted .mp4 file.
>
> example:
> take 25.mp4 created with:
>
crypto allows reading of data which has been aes-128-cbc encrypted given a
key and an iv.
But it did not handle filetypes which require seeking... e.g. it failed on
an encrypted .mp4 file.
example:
take 25.mp4 created with:
ffmpeg -f lavfi -i sine=frequency=1000:beep_factor=2:r=48000:duration=720
