Live data from Hacker News

Show HN: Fixing Google Nano Banana Pixel Art with Rust

github.com

11–20 of 36 posts

Re: Show HN: Fixing Google Nano Banana Pixel Art with Rust

#11

Another annoyance of Nano Banana (and its Pro version) is that it cannot generate transparent pixels. When it wants to, it creates a hallucinated checkerboard background that makes it worse.

Yep. Your best bet is to ask for "solid white/black background" and then feed it into something like rembg [1]. It's an extra step but it'll get you partly there.

On the OpenAI side, the gpt-image-1 model has actually had the ability to produce true alpha transparent images for a while now. Too bad quality-wise they're lagging pretty badly behind other models.

[1] - https://github.com/danielgatis/rembg

Re: Show HN: Fixing Google Nano Banana Pixel Art with Rust

#12

Another annoyance of Nano Banana (and its Pro version) is that it cannot generate transparent pixels. When it wants to, it creates a hallucinated checkerboard background that makes it worse.

Ask it for just white background. Works good for both art and to-be-3d-models.

Re: Show HN: Fixing Google Nano Banana Pixel Art with Rust

#13

I can't explain it, but it's like uncanny valley pixel art. Like the artist hasn't done the final polish pass maybe? Maybe it's the inconsistent lights/shadows? Maybe a pixel artist has the proper words to explain the issues

The skeleton has issues, floor tiles are very inconsistent for example. I haven't looked more carefully. We probably notice something wrong subconsciously but it takes time to point those out.

Generated pixel art for now is 80-90% done state. To use them in prod, issues should be fixed which seems to be the palette and some semantic issues. If you only generate small parts of the big picture with AI, it will be perfectly usable.

Re: Show HN: Fixing Google Nano Banana Pixel Art with Rust

#14
post #4

Is it possible that some of the reason pixels are messed up is because of the watermarking? https://deepmind.google/models/synthid/ Or is it purely because the models just don't understand pixel art?

I wonder if this would be a simple (limited) example of defeating the watermarking? Surely there's no way SynthID is persisting in what is now a handful of pixels.

Re: Show HN: Fixing Google Nano Banana Pixel Art with Rust

#20
post #18

How is the "with Rust" part relevant?

this is a site where people discuss programming languages and tools

rust is a programming language

people interested in rust may find a tool written in rust relevant to their interests where they otherwise might not

Post reply on HN