Show HN: A little side project, a watercolor art generator (opens in new tab)

Creating a watercolor filter which can be applied to an image dragged into a website <canvas> element is on my list of Fun Things To Do Over The Holidays - but having previously looked at the the mechanics that need to feed into the filter ... well it looks like I'd be jumping down a rabbit hole of complex maths and generative art approaches[1][2]. It's a complex problem space and I'm not sure I have the brain power and tenacity to do a good job of it.

[1] - Tyler Hobbs (2017) - a guide to simulating watercolor paint with generative art - https://tylerxhobbs.com/essays/2017/a-generative-approach-to...

[2] - Curtis|Anderson|Seims|Fleischery|Salesin (undated) - Computer-Generated Watercolor - https://grail.cs.washington.edu/projects/watercolor/paper_sm...

My recommendation: Add examples on the main page, so the new users don't need to overload your site.

Otherwise the process is the following:

I enter the page -> Upload image -> See 4h of queue for getting my result -> I close the tab, leaving there a pending task.

It sounds like your app turns photos into a watercolor style image? You can definitely do this faster with Stable Diffusion (~6s per image before optimization).

Here's how I would approach it: train a dreambooth model on watercolor style images, then run image-to-image using that model.

For examples of what dreambooth models can do see: https://synapticpaint.com/dreambooth/info/ (sample images here generated using a "modern disney" style model).

If you need help getting this set up feel free to email me! This stuff is probably not harder than getting gimp to run in a container.

Sorry all for the long wait times! Was not expecting much interest. At the very least, I need to look into removing photos from the queue when people exit the page.

The example looks cool, but I'm currently in an 11 hour queue :(

Any chance of porting this to the web using WASM? I've used ImageMagick in the browser before, I've never used Gimp, but if there's enough overlap you could use the former. That's of course assuming two things:

1) you have the time

2) you're happy to port the closed source, source code to the client

Both of which are perfectly fine to answer with a "no" :)

Also, I think it would be prudent to terminate the request if the client instance is destroyed. Right now I assume there's a bunch of requests being processed for users who have closed the tab.

The results are pretty cool, though it's a shame it cropped the edges. https://brushify.art/result/aa4e68ae-d9de-4673-830e-f88032ec...

Our watercolor filter produces pretty good results (the Flower Market filter which also happens to be the example shown): https://www.instapainting.com/assets

You can implement with something like this and simply train it against a watercolor image: https://github.com/yusuketomoto/chainer-fast-neuralstyle

Haven’t tried it with stable diffusion but you’d probably have more control and better results with a CNN like the one I linked.

Here's a suggestion, port it to run in the browser. Free parallelism, because every user brings their own hardware :) So it scales infinitely, for free.

Fortunately OP, experience with AI is generally unrelated to success with Stable Diffusion / DALLE.

What you want to gain is experience with prompt engineering for these tools.

Here's a good resource https://openart.ai/promptbook

> I'd like to play around with is swapping the GIMP script for an AI-based process

Dall-e offers an API with some limitations (max 4MB square PNG, content filtering): https://beta.openai.com/docs/guides/images/usage

Photopea.com has a watercolor filter, in JS, all client side. It's not very good ATM so there's certainly room for improvement. Doing it all client side would solve the queue problem.

If you can make it with GIMP, you could probably look into OpenGL shaders to do it directly yourself: the processing could be faster and would provide you with more flexibility and coding fun times. I don't know of server-side libraries for that, but on iOS we have MetalPetal which provides some filtering features like ones in Gimp/Photoshop.

Have fun!

Would you be willing to share some details on the GIMP implementation? Are you actually generating brush strokes and "paint" the image or is it more filter based? The background effect looks like brush strokes to me, but are the details done in the same way?

Nice, this is really cool! I don't see myself waiting for my photo to process as it's a ~4 hour wait but the example image is cool.

Like you said I bet using Stable Diffusion would speed this up dramatically but who knows if you'll get the same effect on your images.

In addition to upload/drop image, you could also provide an option to enter an URL of online image. That will make it easy for users to try the project very quickly. Then provide an ephemeral preview URL to see the output.

This is super cool! Didn't know you could run GIMP in headless mode.

I understand it's a side project but you do have a paid offering. So I am curious what are you doing with the images after they are processed?

Site seems to be down - could you post the example output on some image sharing site?

Seeing example output would be interesting, even if service is hugged to death.

Can't see myself paying $5.99 for one of these, but it's nice. I appreciated the fun messages in the progress bar.

PS: Congrats on the little one. :D

It's not exactly a hug of death, but a wait time of 90m is a bit long. I hope that people that leave the queue won't be processed.

Perhaps put the wait time on the homepage - If I'd known you were running at an 8 hour delay I wouldn't have added to it!

The message on the page:

It's a busy day! There are currently 512 people in front of you. Please keep this tab open!

Estimated wait time: 7 hours, 7 minutes

Super cool! Cnc painter next and make a business making custom cards for people!

Estimated wait time: 6 hours, 33 minutes

Oops, sorry OP for all the traffic :D

There should be a smart phone app for this already, right?

I just loved the messages while it is processing!

Why NextJS for this?

Looks really nice!

14h wait time

Very vool

I'm going to go against the grain here. If this were my project I would try to spin up render machines dynamically in response to load. (Similarly to how gitlab CI runners can be spun up automatically, for instance.) There is no need to replace a working technology stack to make it faster. 1 minute is a reasonable wait time, and if your wait time goes over 5 minutes, then spin up some more workers.

Plus we have to be real and say, is the only reason the queue so long, because you let a bunch of nerds on HN add to the queue for free? I'm guessing the answer is, "probably." No need to engineer a fix for a problem that will typically not exist.

I hope the result is worth the wait!

> There are currently 1069 people in front of you. Please keep this tab open!

> Estimated wait time: 14 hours, 51 minutes

> Estimated wait time: 2 hours, 35 minutes

Bruh moment.

I suppose it would make more sense to WASM the implementation and run it clientside?

Now: Estimated wait time: 9 hours, 49 minutes...

The hug is getting tighter ;-)

Why do we need to know you did this while on paternity leave?