Daemon404

FFmpeg would seem to already have this: http://git.videolan.org/?p=ffmpeg.git;a=blob;f=libavformat/a...

I cannot imagine it truly is - it uses a variation of CABAC, which sure has patents related to it.

I wonder if they had a real legal person OK that claim.

Nothing bad ever happens to proprietary database software... nope.

Dang, I always figured that would be unsafe eventually.

I wonder, does this make stuff like this unsafe:

var thing C.thing; C.somefunc(&thing)

i.e. can stack address change now?

Sure, but that requires knowledge of how LLVM works. Some dude checking out the language probably doesn't.

Perhaps I scanned too quickly. I probably missed since there is no actual mention of ABI (or e.g. which calling conventions it supports on what platforms). The page is confusing - it seems to discuss ABI and syntax and stuff, which isn't exactly related to "compatability" afaict.

I digress... just the usual problems with wiki-type sites.

I can't find any mention of if they provide a C-compatible ABI. Kinda useless as a systems language if they don't - you can't call it from anything else.

> It is not difficult to get some kind of honorary position with a research institute when you work in industry.

I think this statement is uh... a tad misleading. This depends a lot on your particular field of interest/research and companies you work for. Also, notoriety.

Hey, I'm 'Daemon404' on FreeNode and Mozilla IRC, or you can grab my FOSS email from my GitHub account or FFmpeg/Libav's git repo.

mozjpeg has such a bug opened too: https://github.com/mozilla/mozjpeg/issues/8

This isn't exactly new ground beign covered here, nor is it tied to one image format, so I wish people would be a little less NIH-y sometimes...

You ought to take a look at jpeg-archive: https://github.com/danielgtaylor/jpeg-archive (the bbcq-like is similar to jpegmini's weighting).

I agree, and as stated in my other comment, I believe it needs downstream support to be adopted properly.

To that end I plan to add support to ImageMagick, and perhaps write a PS plugin.

I am waiting until 3.0 when they roll out their plan for ABI compatibility (it currently masquerades as jpeg62 but is not compatible), and decide on a defacto way to detect if you are building against vanilla libjpeg(-turbo) or mozjpeg (currently you can check for some of their struct members, but they have not stated if they will be going away or not when ABI compatibility is addressed).

At that point I plan to submit a patch to ImageMagick to detect it and enable the user options if mozjpeg is being used. I believe downstream support in libraries like ImageMagick is key to adoption, rather than adding makeup to a pig (input support for N formats in cjpeg).

You can 'optimize' encode-time by using better chroma downsampling, but really the issue is usually on the client side upsampling (a lot of libs use terrible nearest neighbor for 'speed').

As for trellis, you should play with the different metrics available (MS-SSIM etc), but I agree I have not been wowed yet.

It should be noted, since it is nowhere to be seen in this post, it breaks API and ABI while still presenting itself as libjpeg version 6 to the system, which is very evil.

Open Issues:

https://github.com/mozilla/mozjpeg/issues/67 https://github.com/mozilla/mozjpeg/issues/21