Rocksolid Light - comp.compression - Re: Is this a valid LZO compressed byte string?

Re: Is this a valid LZO compressed byte string?

<bed20e91-27da-4eb5-8ee7-d21f7e840e9fn@googlegroups.com>

https://news.novabbs.org/devel/article-flat.php?id=1119&group=comp.compression#1119

copy link Newsgroups: comp.compression

X-Received: by 2002:ac8:4e51:0:b0:31b:efe0:aa24 with SMTP id e17-20020ac84e51000000b0031befe0aa24mr26519851qtw.635.1657006548606;
Tue, 05 Jul 2022 00:35:48 -0700 (PDT)
X-Received: by 2002:a05:620a:15cd:b0:6af:2bef:2f69 with SMTP id
o13-20020a05620a15cd00b006af2bef2f69mr22101413qkm.374.1657006548332; Tue, 05
Jul 2022 00:35:48 -0700 (PDT)
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!feed1.usenet.blueworldhosting.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.compression
Date: Tue, 5 Jul 2022 00:35:48 -0700 (PDT)
In-Reply-To: <04352f0c-4ff3-4c61-9514-7f983ad20588@j5g2000vbg.googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=49.205.173.68; posting-account=HXcKQwoAAAABxAtTFHWe7EYPN9HpkQ8P
NNTP-Posting-Host: 49.205.173.68
References: <45816859-09f0-49c4-b096-df64a67281cd@z25g2000vbn.googlegroups.com>
<a2b31e69-256e-4c13-afa4-e19a66e58e9d@c21g2000vba.googlegroups.com>
<e33ede80-1cce-443a-beac-0a6a2b50b575@c21g2000vba.googlegroups.com> <04352f0c-4ff3-4c61-9514-7f983ad20588@j5g2000vbg.googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <bed20e91-27da-4eb5-8ee7-d21f7e840e9fn@googlegroups.com>
Subject: Re: Is this a valid LZO compressed byte string?
From: mr.jat2310@gmail.com (Mukesh Jat)
Injection-Date: Tue, 05 Jul 2022 07:35:48 +0000
Content-Type: text/plain; charset="UTF-8"
X-Received-Bytes: 2481

by: Mukesh Jat - Tue, 5 Jul 2022 07:35 UTC

On Friday, September 10, 2010 at 6:53:48 PM UTC+5:30, Slaunger wrote:
> Although I am just having a dialogue with myself here, I finally
> figured out what the problem is:-) (I cannot solve my problem, but now
> I at least know what it is)
> The lzo python bindings does not return the exact same array of bytes
> as the C-library functions. They add a header, where the first byte is
> 0xF= for LZO-1X compr lvl 1, and then an uint 32 representing the
> number of bytes in the *uncompressed* byet array. Apparently, this
> convenience information is used in the Python binding uncompress
> function, to allocate the right sized buffer for the output prior to
> calling the lzo library uncompress function. Really crap binding code
> if you ask me as it measn that I have to know *in advance* how many
> bytes a compressed array of bytes will unpack into *prior* to calling
> lzo.uncompress. And if it is compressed data from another data source,
> it is really not possible to know that final data size beforehand,
> which is...crap.
Just use lzo.decompress(data,False,out_len,alogrithm="XYZ")

And on the seventh day, He exited from append mode.

devel / comp.compression / Re: Is this a valid LZO compressed byte string?

Subject	Author
Re: Is this a valid LZO compressed byte string?	Mukesh Jat