Home
last modified time | relevance | path

Searched refs:APP0 (Results 1 – 10 of 10) sorted by relevance

/third_party/ffmpeg/libavcodec/
Dmjpeg.h79 APP0 = 0xe0, enumerator
Dmjpeg2jpeg_bsf.c101 if (in->data[2] == 0xff && in->data[3] == APP0) { in mjpeg2jpeg_filter()
Dmxpegdec.c212 if (start_code >= APP0 && start_code <= APP15) { in mxpeg_decode_frame()
Dmjpegenc_common.c184 put_marker(p, APP0); in jpeg_put_comments()
Dmjpegdec.c2473 } else if (start_code >= APP0 && start_code <= APP15) { in ff_mjpeg_receive_frame()
/third_party/ffmpeg/libavformat/
Drtpdec_jpeg.c112 jpeg_put_marker(&pbc, APP0); in jpeg_create_header()
Dimg2dec.c795 case APP0: in jpeg_probe()
/third_party/skia/third_party/externals/libjpeg-turbo/
Dchange.log154 than as unknown APP0 markers.
Dlibjpeg.txt1052 If TRUE, a JFIF APP0 marker is emitted. jpeg_set_defaults() and
1194 boolean saw_JFIF_marker TRUE if a JFIF APP0 marker was seen
2501 "APP0" through "APP15" (application) to hold application-specific data.
2504 format spec uses APP0 markers with specified initial strings to hold certain
2518 It's probably best to avoid using APP0 or APP14 for any private markers.
2525 By default, the IJG compression library will write a JFIF APP0 marker if the
2535 the SOI and the JFIF APP0 and Adobe APP14 markers (if written), but before
2589 routine 17 times, for COM and APP0-APP15.) If the incoming marker is longer
2619 Note that the library is internally interested in APP0 and APP14 markers;
2641 If you override the default APP0 or APP14 processors, it is up to you to
/third_party/libexif/
DChangeLog1639 * libexif/exif-loader.c: Fix APP0-bug. Patch by Jan Patera