[FFmpeg-devel] [PATCH] CCITT Group 3 and 4 decompression

Michael Niedermayer michaelni
Fri Dec 26 15:06:45 CET 2008


On Fri, Dec 26, 2008 at 08:20:04AM +0200, Kostya wrote:
> On Thu, Dec 25, 2008 at 07:33:35PM +0100, Michael Niedermayer wrote:
> > On Thu, Dec 25, 2008 at 08:19:25AM +0200, Kostya wrote:
> > > On Wed, Dec 24, 2008 at 11:00:08PM +0100, Michael Niedermayer wrote:
> > > > On Wed, Dec 24, 2008 at 08:06:13AM +0200, Kostya wrote:
> > > > > On Tue, Dec 23, 2008 at 08:27:31PM +0100, Michael Niedermayer wrote:
> > > > > > On Tue, Dec 23, 2008 at 09:00:57AM +0200, Kostya wrote:
> > > > > > > On Mon, Dec 22, 2008 at 09:06:37PM +0100, Michael Niedermayer wrote:
> > > > > > > > On Mon, Dec 22, 2008 at 08:15:06PM +0200, Kostya wrote:
> > > > > > > > > On Mon, Dec 22, 2008 at 01:13:53PM +0100, Michael Niedermayer wrote:
> > > > > > > > > > On Mon, Dec 22, 2008 at 08:31:55AM +0200, Kostya wrote:
> > > > > > > > > > > I need that for resolving issue 750 on roundup.
> [...]
> > > Also it does
> > > not matter for decoding if there's EOL right one bit before line end -
> > > there won't be sufficient data to decode that line anyway (for 2d-case
> > > that single bit is read to determine line coding mode and for 1d case
> > > first codeword should have length >= 4 bits).
> > 
> > its imporant to detect errors, for that it is important to find out if
> > a sync marker is missing, this also includes the last sync marker.
> > 
> > i can offer to cleanup, commit and maintain CCITT fax support myself if
> > you dont want to fix the issues?
> 
> Since you show interest in it, why not?
> I've fixed some bugs in the code so CCITT_8.TIF from mphq decodes correctly
> now. Feel free to do anything with it (including adding raw fax images
> support).

the tiffs from mphq are all g4, do you have some g3 too?


>  
> > [...]
> > > > btw, do you have some url where i can find files to test this code?
> > > 
> > > http://samples.mplayerhq.hu/image-samples/tiff/
> > >  
> > 
> > thanks
> > 
> > 
> > > > PS: merry christmas :)
> > > 
> > > Well, I live in a country where church calendar uses incorrect rounding
> > > and was tied to the standard one only in XXth century with 13 days of difference
> > > we have New Year first, then Christmas on Jan 7th and then Old New Year on
> > > Jan 14th (i.e.  New Year in Old calendar). Pretty amusing, eh?
> > 
> > a few days off isnt that bad ...
> > keep in mind that the whole calendar the world is using is a few years off,
> > wiki says something between 2 and 7 years.
> 
> That happens when you set starting point to an arbitrary position.

... an arbitrary position you dont know when it happened exactly

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

If you really think that XML is the answer, then you definitly missunderstood
the question -- Attila Kinali
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://lists.mplayerhq.hu/pipermail/ffmpeg-devel/attachments/20081226/06f91661/attachment.pgp>



More information about the ffmpeg-devel mailing list