BMP is free isn't it????
Free Lossless Image Format
201–210 of 374 posts
Re: Free Lossless Image Format
#202This is an exciting development. I think the concerns about the licensing are a bit premature - honestly, this is currently a research project, not a practical replacement for existing image formats. The licensing is only one of several impediments to adoption. - The format has no spec - The format may change, rendering all previous images unreadable - The format has no javascript implementation, and no way of runnin…
> - No peer-reviewed paper published yet?
While there's no paper there's a full Github repo which I'd actually say is quite impressive.
Re: Free Lossless Image Format
#203Earlier quoted context omitted.
JPEG has something cooler, you can first load a black-white smaller picture, then load more color and more detail.
Thinking back to the old days, are you sure the black and white image you have in mind didn't come from the "lowsrc" attribute of an img tag? Progressive jpeg is typically full colour from the start, and it does offer the progressive enhancement of resolution that you mention.
Interesting, just last week I had a use for lowsrc for the first time in years and tried to use it, only to find out it had been removed from all browsers a while back.
Re: Free Lossless Image Format
#204Earlier quoted context omitted.
No documented format (actually an explicit acknowledgement that the format will likely change). The implementation is the spec, the implementation is GPLv3, so many companies lawyers will prevent engineers even looking at it to write a clean-room implementation.
>so many companies lawyers will prevent engineers even looking at it to write a clean-room implementation. Maybe you should look up what 'clean-room' reverse engineering is. One person looks at the code, writes down how what it does, then gives that description to another person who writes CLEAN-ROOM code based upon the description. There's no difference in doing a clean-room implementation of GPLv3 code than of any…
The difference is that the lawyers for some companies will not sign off on employees even looking at GPLv3 sources. Rightly or wrongly, this really does make a clean-room implementation impossible.
One can reasonably argue that this is stupid and not the fault of the GPL. However, it's also reality, and a real block to adoption of technologies like image formats.
Re: Free Lossless Image Format
#205One of the least interesting parts of this is that it is GPL. Someone should reimplement it with a BSD license so it can be used more widely. AFAIK & IANAL, but I don't think you could integrate this with FF, Chrome, Safari or IE.
It is an issue on the GitHub Project:
https://github.com/jonsneyers/FLIF/issues/3
The title incorrectly suggests Creative Commons (which is inappropriate for code), but the discussion does suggest better alternatives.
Re: Free Lossless Image Format
#206Why all the hate for GPLv3?
Sharing code is no longer cool if people have to share back. Or at least so it seems. The GPL-hate in here really is quite immense, even though time and time again, RMS has been shown to be right about his stance on freedom. Should we attribute it to people's desire for a quick ("free") fix over long term considerations? It's hard to tell, but I suspect the silicon valley influence here doesn't help. There everyone w…
What's to stop someone from reimplementing this with some other license?
Re: Free Lossless Image Format
#207Earlier quoted context omitted.
Progressive JPEG has supported this for decades. Anyone over 25 should remember them from dial-up years.
I think the suggestion is that the client could just stop downloading at a set threshold, maybe taking current bandwidth, cost, etc. into consideration. Judging from the video, something like that could work very well (and much better than with progressive jpegs).
It's an interesting concept. But I'm not sure how it could work. Resizing introduces artifacts so best quality is always going to be achieved by reencoding for different resolutions. Also, how would the client know when to stop downloading?
Re: Free Lossless Image Format
#208Earlier quoted context omitted.
So you're saying that for example the FreeBSD people are money oriented because they prefer a more permissive license over the GPL?
The people here aren't the FreeBSD team--they're wannabe startup founders who'd like to take BSD-licensed code and sell it.
Perhaps, but the GPL licensing of this code isn't a barrier to them doing that, since most of them will be running web services that can use GPL code freely without having to release the rest of their code. If it was AGPL then maybe you would have a point.
The issue in this case is that image formats need widespread support to take off, and picking a license that is incompatible with 4/5 major browsers ensures that won't ever happen.
Re: Free Lossless Image Format
#209Earlier quoted context omitted.
JPEG 2000 has that same feature. FLIF claims it will beat the lossless compression ratio of JPEG 2000
It also claims to beat the lossy version, which cannot even be encoded for the transparent fish image at the tested file sizes: http://flif.info/example.php [ed. image size → file size to emphasize that they had a target byte count for the purpose of comparison]
I'm not picking on FLIF, it may well be better! But the concept of progressively decoding for different quality levels isn't what makes it new.
Re: Free Lossless Image Format
#210This is really interesting. One of the most interesting parts is the progressive decoding/responsive images. http://flif.info/example.php (go to the bottom of the page). Basically, the last example shows that, if you want a scaled version of the image, you can simply stop decompressing. No need for multiple image files. Just create one with very high quality and decompress until you get the quality you want and scale…
If you want to use a similar feature -today-, there's this service called Imgix: https://www.imgix.com/
Basically, it allows you to use responsive images using 1 single master image. Makes for a really snappy user experience, and it's very easy to integrate into any project, new or old.