On Fri, Sep 06, 2019 at 05:00:14PM -0700, Niki Bowe wrote:
> As it turns out the last patch still lets a lot of jpegs get misidentified.
>
> This new version avoids the problem by checking for jpeg magic at the start.
>
> I also added a FATE test, and attached the jpeg for the test.
>
>
>
> On
As it turns out the last patch still lets a lot of jpegs get misidentified.
This new version avoids the problem by checking for jpeg magic at the start.
I also added a FATE test, and attached the jpeg for the test.
On Tue, Aug 27, 2019 at 6:30 PM Niki Bowe wrote:
>
>
> On Sun, Aug 25, 2019 a
On Sun, Aug 25, 2019 at 11:39 AM Michael Niedermayer
wrote:
> On Fri, Aug 23, 2019 at 04:03:10PM -0700, Niki Bowe wrote:
> > On Thu, Aug 22, 2019 at 2:30 AM Paul B Mahol wrote:
> >
> > > On Thu, Aug 22, 2019 at 11:19 AM Carl Eugen Hoyos
> > > wrote:
> > >
> > > > Am Mi., 21. Aug. 2019 um 23:05
On Fri, Aug 23, 2019 at 04:03:10PM -0700, Niki Bowe wrote:
> On Thu, Aug 22, 2019 at 2:30 AM Paul B Mahol wrote:
>
> > On Thu, Aug 22, 2019 at 11:19 AM Carl Eugen Hoyos
> > wrote:
> >
> > > Am Mi., 21. Aug. 2019 um 23:05 Uhr schrieb Niki Bowe
> > > :
> > > >
> > > > On Mon, Aug 19, 2019 at 7:22
On Thu, Aug 22, 2019 at 2:30 AM Paul B Mahol wrote:
> On Thu, Aug 22, 2019 at 11:19 AM Carl Eugen Hoyos
> wrote:
>
> > Am Mi., 21. Aug. 2019 um 23:05 Uhr schrieb Niki Bowe
> > :
> > >
> > > On Mon, Aug 19, 2019 at 7:22 PM Carl Eugen Hoyos
> > wrote:
> > >
> > > >
> > > > This score would mean t
On Thu, Aug 22, 2019 at 11:19 AM Carl Eugen Hoyos
wrote:
> Am Mi., 21. Aug. 2019 um 23:05 Uhr schrieb Niki Bowe
> :
> >
> > On Mon, Aug 19, 2019 at 7:22 PM Carl Eugen Hoyos
> wrote:
> >
> > >
> > > This score would mean that mjpeg can never be detected.
> > > I suspect you have to reduce one of
Am Mi., 21. Aug. 2019 um 23:05 Uhr schrieb Niki Bowe
:
>
> On Mon, Aug 19, 2019 at 7:22 PM Carl Eugen Hoyos wrote:
>
> >
> > This score would mean that mjpeg can never be detected.
> > I suspect you have to reduce one of the demuxers to "- 1".
> >
> >
> Thanks Carl.
> Attached patch to reduce mpeg
On Wed, Aug 21, 2019 at 01:58:52PM -0700, Niki Bowe wrote:
> On Mon, Aug 19, 2019 at 7:22 PM Carl Eugen Hoyos wrote:
>
> >
> > This score would mean that mjpeg can never be detected.
> > I suspect you have to reduce one of the demuxers to "- 1".
> >
> >
> Thanks Carl.
> Attached patch to reduce m
On Mon, Aug 19, 2019 at 7:22 PM Carl Eugen Hoyos wrote:
>
> This score would mean that mjpeg can never be detected.
> I suspect you have to reduce one of the demuxers to "- 1".
>
>
Thanks Carl.
Attached patch to reduce mpeg probe by -1, which also fixes the issue.
Alternatively I could bump both
Am Di., 20. Aug. 2019 um 03:37 Uhr schrieb Nikolas Bowe
:
>
> Fixes "Invalid data found when processing input" on some JPEGs.
>
> Some large extensionless JPEGs can get probe score collisions.
> eg
> $ ffprobe -loglevel trace /tmp/foo
> [NULL @ 0x55c130ab04c0] Opening '/tmp/foo' for reading
> [fil
Fixes "Invalid data found when processing input" on some JPEGs.
Some large extensionless JPEGs can get probe score collisions.
eg
$ ffprobe -loglevel trace /tmp/foo
[NULL @ 0x55c130ab04c0] Opening '/tmp/foo' for reading
[file @ 0x55c130ab0f40] Setting default whitelist 'file,crypto'
Probing jpeg_
11 matches
Mail list logo
