PixQL: SQL for image processing

#1

Post by GuiA » Tue, Jun 30, 2015, 2:03 AM UTC

PixQL: SQL for image processing
github.com

Re: PixQL: SQL for image processing

#2

Post by hmans » Tue, Jun 30, 2015, 6:52 AM UTC

No.

Re: PixQL: SQL for image processing

#3

Post by mappu » Tue, Jun 30, 2015, 7:05 AM UTC

Interesting! Can you support multiple image buffers? e.g. for xor or morphing operations. I would suggest taking a look at avisynth as an example of a media processing language.

Re: PixQL: SQL for image processing

#4

Post by jitl » Tue, Jun 30, 2015, 7:07 AM UTC

This looks amazing, but it might be easier to express these sorts of ideas with a simple functional language. Does anyone know of a similar library in a lisp or ML?

Re: PixQL: SQL for image processing

#5

Post by ddebernardy » Tue, Jun 30, 2015, 7:10 AM UTC

Does this have any practical use?

It seems like the image equivalent of treating an HTML file as a huge string of characters -- instead of as the representation of a DOM tree. Which makes very little sense.

Plus, you seldom want to do trivial things like selecting red pixels and flipping their color to green. You want to select red eyes and flip those to their correct color.

Re: PixQL: SQL for image processing

#6

Post by kbenson » Tue, Jun 30, 2015, 7:14 AM UTC

If you are going to use SQL select, why use a separate operate statement when you could just use SQL's method for this, update? For that matter, if you are going to use SQL syntax, I would imagine you would want to keep one of the main features, which is joining of datasets. Being able to join an image with itself in some manner (or another image...), would be really useful. Instead of globals, use the images as tables of pixels with those attributes.

Imagine breaking an image down into pixels, actually storing them into a database, performing some queries, and outputting the result. Something equivalent to that (sans database) sounds interesting to me.

Re: PixQL: SQL for image processing

#7

Post by kubiiii » Tue, Jun 30, 2015, 7:19 AM UTC

ddebernardy wrote: post #5

Does this have any practical use? It seems like the image equivalent of treating an HTML file as a huge string of characters -- instead of as the representation of a DOM tree. Which makes very little sense. Plus, you seldom want to do trivial things like selecting red pixels and flipping their color to green. You want to select red eyes and flip those to their correct color.

I find this interesting, but I also would like to see more complex use cases. For example using using some kind of select union on several images to output a synthetic image highlighting differences or similarities?

Re: PixQL: SQL for image processing

#8

Post by joelthelion » Tue, Jun 30, 2015, 7:33 AM UTC

SQL is awesome, but it doesn't mean you have to keep the CAPITAL LETTERS.

Re: PixQL: SQL for image processing

#9

Post by neuro_sys » Tue, Jun 30, 2015, 7:41 AM UTC

I like the part where he mentions why using a traditional GUI tool is more difficult than using an expressive language with basic syntax.

"But in photoshop, I instead am relying on the problem being solved externally ("ok, how can I find the right menu that deals with this kind of operation? what's the word the designers of photoshop used to describe this... I hope if I google it in plain text it might link to a forum post or something of someone with the same problem?")."

This is valid for most cases when GUIs are harder to use than a CLI with syntax.

Re: PixQL: SQL for image processing

#10

Post by creshal » Tue, Jun 30, 2015, 8:20 AM UTC

joelthelion wrote: post #8

SQL is awesome, but it doesn't mean you have to keep the CAPITAL LETTERS.

Aren't SQL keywords case insensitive anyway?