[Libav-user] Dealing with badly formed Headers

Paul Sanderson nannapie at hotmail.co.uk
Thu May 2 20:33:31 EEST 2019

I took your advice and tried the command line tool. It’s giving me the same issue regarding the image size. If there’s not a way to side step badly formed headers then I’ll have to think of another way around it.

I get a RTSP/SDP that contains the information but the headers are badly formed.

[cid:88619122-c96f-4801-ad93-ffe55b1b8475 at eurprd04.prod.outlook.com]

The image above shows the width parameter that’s missing on the higher resolution image stream.

All my best,


(Thank you for your help, it sounds like I may need to contact the manufacturer)

Sent from the top a castle using a moderately sized European swallow

> On 2 May 2019, at 14:13, Carl Eugen Hoyos <ceffmpeg at gmail.com> wrote:
> Am Do., 2. Mai 2019 um 13:54 Uhr schrieb Paul Sanderson
> <nannapie at hotmail.co.uk>:
>> I’m successfully decoding a video stream from a camera that uses h264 and JPEGs.
>> However.. there is a bug in the camera so the JPEG header does not contain the width
>> information. This throws a picture invalid size (which it should).
> Can you "record" what the camera sends and provide a sample file?
> Did you try with ffmpeg, the application?
> You can in general not set fields that a decoder is supposed to fill
> but I wonder how
> the camera provider expects you to decode the stream...
> Carl Eugen
> _______________________________________________
> Libav-user mailing list
> Libav-user at ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/libav-user
> To unsubscribe, visit link above, or email
> libav-user-request at ffmpeg.org with subject "unsubscribe".
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://ffmpeg.org/pipermail/libav-user/attachments/20190502/426d705f/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Type: image/jpeg
Size: 354210 bytes
URL: <http://ffmpeg.org/pipermail/libav-user/attachments/20190502/426d705f/attachment.jpg>

More information about the Libav-user mailing list