Am Sa., 6. Juni 2020 um 21:05 Uhr schrieb Kieran O Leary
:
> I was doing some tests with libaom and lossness encoding and with synthetic
> files and some real world files, I kept finding that the framemd5s for the
> first frame was different than the source, but every other libaom encoded
> frame
On Sun, Jun 7, 2020 at 10:08 PM Kieran O Leary
wrote:
>
>
> On Sun, Jun 7, 2020 at 10:06 PM pdr0 wrote:
>
>> Intra only compression , using -g 1 makes it lossless . Maybe a clue there
>>
>
> Aye - I can confirm that -g 1 produces matching framemd5s.
>
Just checking in on this issue - any ideas?
On Sun, Jun 7, 2020 at 10:06 PM pdr0 wrote:
> Intra only compression , using -g 1 makes it lossless . Maybe a clue there
>
Aye - I can confirm that -g 1 produces matching framemd5s.
K
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.
Intra only compression , using -g 1 makes it lossless . Maybe a clue there
Not sure why there is a discrepancy between aomenc, and ffmpeg libaom-av1
--
Sent from: http://www.ffmpeg-archive.org/
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http
Hi Carl,
On Sun, Jun 7, 2020 at 9:18 PM Carl Eugen Hoyos wrote:
> Am So., 7. Juni 2020 um 19:16 Uhr schrieb Kieran O Leary
> :
>
> > On Sun 7 Jun 2020, 17:56 pdr0, wrote:
> >
> > > Kieran O Leary wrote
> > > > Any idea what's happening? Will I get the libx264-style answer:
> 'this is
> > > > g
Carl Eugen Hoyos-2 wrote
> Could it be the number of cores in your system / is the issue reproducible
> with -threads 1 ?
Issue is still present with -threads 1
Does not appear to be related to pixel format (eg. affects yuv420p source
test as well)
--
Sent from: http://www.ffmpeg-archive.org/
Am So., 7. Juni 2020 um 19:16 Uhr schrieb Kieran O Leary
:
> On Sun 7 Jun 2020, 17:56 pdr0, wrote:
>
> > Kieran O Leary wrote
> > > Any idea what's happening? Will I get the libx264-style answer: 'this is
> > > googles issue,
> >
> > I can replicate the ffmpeg issue (and with other sources), but
Hi
On Sun 7 Jun 2020, 17:56 pdr0, wrote:
> Kieran O Leary wrote
> > Any idea what's happening? Will I get the libx264-style answer: 'this is
> > googles issue,
>
> I can replicate the ffmpeg issue (and with other sources), but I don't know
> what the problem is
>
> It's not a "google" issue, be
Kieran O Leary wrote
> Any idea what's happening? Will I get the libx264-style answer: 'this is
> googles issue,
I can replicate the ffmpeg issue (and with other sources), but I don't know
what the problem is
It's not a "google" issue, because AOM aomenc.exe works, and produces
lossless output
Hi,
I was doing some tests with libaom and lossness encoding and with synthetic
files and some real world files, I kept finding that the framemd5s for the
first frame was different than the source, but every other libaom encoded
frame produced matching framemd5s for source and output.
I then tried
10 matches
Mail list logo