LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Single file compression using OpenG and with the Gzip header errors out

Solved!
Go to solution

Looking to compress a single string of data with Gzip, a single file compression format.
Using the OpenG gives me the following error:

Spoiler

ZLIB Inflate Extended__ogtk.vi<APPEND>

<b>Complete call chain:</b>
ZLIB Inflate Extended__ogtk.vi
Simple Text Compression Gzip.vi

Furthermore, I cannot open the file with 7zip even after saving it. What metadata am I missing for this compression to work correctly?

Screenshot 2024-10-11 093603.png

0 Kudos
Message 1 of 5
(222 Views)

Are you sure to use the latest version 5.0.5 of the OpenG ZIP library?

 

And how? Would you mind donwnconverting the VI to 2020 or earlier?

Rolf Kalbermatter
My Blog
0 Kudos
Message 2 of 5
(208 Views)

Yes,
v5.0.5-1
I am simply passing in a string. Since Gzip is single file compression, shouldn't it be enough to just save the compressed string as a file?

Screenshot 2024-10-11 104123.png

Attached is the VI saved as 20.0

0 Kudos
Message 3 of 5
(195 Views)
Solution
Accepted by eli.barber

Two remarks:

 

1) The "detect" seems to somehow stumble. If you select explicitly "gzip" for the Inflate that one will work.

 

2) gzip is a binary stream. This means you should use the Write Binary File function, not the Write Text File function!

Rolf Kalbermatter
My Blog
0 Kudos
Message 4 of 5
(154 Views)

I looked at it over the weekend. I had misunderstood something about how the code worked when I naively added the detect selection to the VI interface. Basically you can select zlib + gzip if you want the code to detect what type of header is present. But there is no fail proof way to detect if there is a header or not. This is because the two header standards have guaranteed different values in the first two bytes. But there is no way to guarantee that a headerless deflate stream couldn't contain values in the two bytes that might not be recognized as valid gzip or zlib header. It's unlikely to happen but not impossible. So I'll have to remove that detect option in the next release. I rather don't have that option than letting users believe there would be a safe way to detect what sort of deflate stream is passed to the function.

Rolf Kalbermatter
My Blog
0 Kudos
Message 5 of 5
(108 Views)