This is perfect! I have had such a time with Nano Banana asking it to generate some very simple pixel art. One of the worst things is that it cannot seem to generate transparent backgrounds or even solid ones. It’s always some blotchy cloud of off-white pixels or a simulated fuzzy grid that shows up in some places. I will need to give this a try to clean up some of what I had to try by hand.
Show HN: Fixing Google Nano Banana Pixel Art with Rust
21–30 of 36 posts
Re: Show HN: Fixing Google Nano Banana Pixel Art with Rust
#22How is the "with Rust" part relevant?
For what it's worth, it's what caught my attention. I wouldn't have found it so captivating if it had only said "Fixing Google Nano Banana Pixel Art". To be clear, it's not because of Rust in particular. It would have been the same if it said "with C#", or "with Python", or even just "programmatically". And on that note: I feel disappointed. I thought I would be reading about the development process, and not just a product presentation.
Re: Show HN: Fixing Google Nano Banana Pixel Art with Rust
#23[deleted]
Re: Show HN: Fixing Google Nano Banana Pixel Art with Rust
#24Go Hugo!
Re: Show HN: Fixing Google Nano Banana Pixel Art with Rust
#25I 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 borders of shapes are all wrong. It’s not too complicated. There is a small vocabulary of valid border patterns (e.g. a line rising one pixel up and two pixels right) that none of these generative models adhere to.
Re: Show HN: Fixing Google Nano Banana Pixel Art with Rust
#26At last! I have been dreaming about such a tool for years. I often find pixel art that has been scaled or poorly compressed. So it's a bunch of fuzzy squares. Can't wait to try this.
Re: Show HN: Fixing Google Nano Banana Pixel Art with Rust
#27How is the "with Rust" part relevant?
As a Rust fan I consider this a very valid question. Rust projects should be able to defend their worth without piggybacking onto the love Rust receives from programmers anymore. ‘Not written in js/ts/golang/python’ works for me, too, but it’s a mouthful.
Re: Show HN: Fixing Google Nano Banana Pixel Art with Rust
#28This is perfect! I have had such a time with Nano Banana asking it to generate some very simple pixel art. One of the worst things is that it cannot seem to generate transparent backgrounds or even solid ones. It’s always some blotchy cloud of off-white pixels or a simulated fuzzy grid that shows up in some places. I will need to give this a try to clean up some of what I had to try by hand.
I simply cannot understand people who'll spend forever trying to get AI to generate basic art that any amateur with a bit of practice could do in a minute.
Re: Show HN: Fixing Google Nano Banana Pixel Art with Rust
#29It feels weird to me that on the before/after comparision they felt the need to zoom in on the “before” but not on the “after”. Either both should have the magnifying glass or neither. This just makes it hard to see the difference.
There are more details in the fixed version too, e.g. an extra detailed dark line within right leg (tibia) that is not present in the original; where do these details come from?
Re: Show HN: Fixing Google Nano Banana Pixel Art with Rust
#30It feels weird to me that on the before/after comparision they felt the need to zoom in on the “before” but not on the “after”. Either both should have the magnifying glass or neither. This just makes it hard to see the difference.
The purpose of zoomed out comparison is to show the quality reduction of applying this tool. The purpose of zoomed in before picture is to show how a typical pixel misalignment. Aligned pixels can be easily imagined.