Search results

Can you send me the original as a png file instead? And what happens if you use ImageMagick to convert the png to pnm?

I would guess that 64-bit architectures tend to consume more memory than 32-bit architectures because of those platform-dependent types, not so much the ints (they don't even need to be bigger) but mostly the size of pointers. Another difference between ARM and x86 is that ARM does not have...

During normal use (screen active, cpu somewhat active), I don't expect there to be a big difference in power consumption between 2GB RAM and 4GB. During standby (lid closed, cpu idle), I expect a quite noticeable difference in power consumption, since RAM is pretty much the only thing that stays...

Right. Using getopt() now so option parsing is more flexible and more standard now. Well, PNM is just uncompressed image data, so if you decode to that (e.g. to a file that is actually in RAM), you can use any viewer. Too bad PNM does not support alpha. You can try the progressive loading by...

Try decoding to .pnm instead of .png... An image looking too black could be because of missing metadata (FLIF only encodes the pixels). E.g. if only the 12 least significant bits out of 16 are used, then without additional info, that looks very dark...

Added support for up to 16-bit color depth (per channel, so up to 64 bit per pixel). I just commited it to github. I didn't really test it much yet, I only tried it on one image, this one: http://www.brucelindbloom.com/index.html?ReferenceImages.html (DeltaE_16bit_gamma2.2.tif) The...

If there are multiple sizes to choose from, why not 1GB? Better standby battery life, cheaper, and still twice as much RAM as the best Pandora. I don't really see the use of huge amounts of RAM. Is anyone planning to do a lot of multitasking and/or big number crunching tasks on the Pyra? Video...

I think you mean ~5MB camera files. If have never seen a camera that produces 5GB files :)

Yes, 65535x65535 is the maximum image resolution. If this ever becomes a problem, then it is easily solved by handling 0x0000 as a special size marker (which would be a 0x0 image, which does not make sense anyway), followed by the actual size as two 32 bit ints, or something like that. At the...

Yes, maybe "aborting the download" is not the correct way to put it, what I really meant was to stop asking for more bytes, however that is implemented in the underlying transfer protocols. This applies not just to HTTP and web browsers, it could also be an image viewer reading bytes from an...

Updated the website with some information on how FLIF could be useful for responsive web design: http://people.cs.kuleuven.be/~jon.sneyers/FLIF/ Also added an example: http://people.cs.kuleuven.be/~jon.sneyers/FLIF/example.html

Fixed the negative progress percentage. Could you send me that source image with 12 bits per pixel? (or a similar image) Usually "flif -ni" produces smaller files, but you lose the progressive interlacing. But those hase sprites are probably rather small, in that case flif will not interlace...

It seems only to be referenced in that one place in your source code, and I've checked the system included png.h and that doesn't define it or anything like it (all its defines seem to begin with PNG_).  In case it is expected to be defined in that file, the version I'm using is libpng version...

Thanks! I used some of your suggestions to improve the site. Anything else I should put on the website?

I'm working on a FLIF website. Comments are welcome! http://people.cs.kuleuven.be/~jon.sneyers/FLIF/

Here are some artificially glitched FLIF files. This is the original image / uncorrupted FLIF file: Here I modified one bit near the beginning of the file: One modified bit somewhat further into the file: Further again: Near the end of the file: The above are with FLIF in...

Corrupted files will be decoded to spectacular glitch art. It's actually quite fun: flip one bit somewhere in the middle of a FLIF file, and you get nice effects. The FLIF decoder will detect corruption (it checks a checksum). Recovery is not possible, for that you need redundancy, which is...

Here is a spreadsheet with an overview of all the sets of images I've tried so far: https://docs.google.com/spreadsheets/d/16ghJEjf_T7TDTOg2WlelnG1SYCsHng6V-1rxdo78YL8/edit?usp=sharing So far, FLIF is still beating (the hell out of) the other lossless image compression algorithms, whatever I...

I prefer PYRA over Pyra. Mostly because lowercase r and a are so much more ambiguous than uppercase R and A. It's a short word, and it's a name, which means it's not a word shape people are used to already. So it's good to avoid letter shapes that are somewhat ambiguous -- the last thing we want...

... and some more: Monochrome icons with alpha: Fractal art: Wallpapers: (originals were jpegs, so we're encoding some jpeg artifacts here) The five images in the lossless WebP gallery: The images in the small Waterloo corpus: Here is a summary plot of everything, except all...