Re: in memory jpeg destination and source managers
- From: chhenning@xxxxxxxxx
- Date: 5 Sep 2006 18:02:23 -0700
OK, I could figure it out. I was calling jpeg_write_tables and this
call was adding the tables to my buffer a bit to early. It's better to
omit jpeg_write_tables and to call jpeg_suppress_tables(&cinfo, FALSE).
Then the first call to jpeg_write_scanlines will add the tables.
Christian
chhenning@xxxxxxxxx wrote:
Hi there, I have a problem with my own jpeg destination and source
managers. My goal is to compressed a jpeg buffer from an rgb buffer.
And also the vice versa. The compressed buffer created by the
destination manager starts with FFDB ( the quantization table ) rather
than with FFD8 ( Start of image ). When I try to get to my rgb buffer
the application crashes when calling jpeg_read_header.
I think the compressed buffer has all the necessary sections, but they
are ordered somehow in a weird way. Is that normal?
If you are interessted in the source code ( C ), let me know.
Thanks ahead,
Christian
.
- References:
- in memory jpeg destination and source managers
- From: chhenning
- in memory jpeg destination and source managers
- Prev by Date: Re: FAQ Maintenance?
- Next by Date: Re: FAQ Maintenance?
- Previous by thread: in memory jpeg destination and source managers
- Index(es):
Relevant Pages
|
|