Live data from Hacker News

Colorizing and restoring old images with deep learning

github.com

101–107 of 107 posts

Re: Colorizing and restoring old images with deep learning

#101

I've to admit I have no clue about machine learning, but what I notice is that this seems to have preferred colors for things that can actually have many different colors, most notably clothes. They're almost always this blueish slightly purple color here, even the samurai. Don't get me wrong, this is still awesome and I might try this on some old photos from my grandparents. I'm just wondering if and how one can pre…

The Seneca Native in 1908 example seems the most absurd to me. I know the software has no notion of a "fabric" or "clothing" but it's very rare for brown or beige things to fade to blue (or vise versa). In real life things when transition from brown/beige to another color that other color tends to be a red orange or yellow. I know from the known issue that it likes blue but it still seems very odd that it chose to fa…

Take a look at the two most famous indian textiles from the 1800s which sold For millions/appraised for millions.

They were chiefs blankets.

They were blue/had no red

https://www.youtube.com/watch?v=9cGlS05233Q

https://www.youtube.com/watch?v=WJw2qCnhea0

Re: Colorizing and restoring old images with deep learning

#102
post #99
post #60

Earlier quoted context omitted.

Author here. That's actually what I find quite fascinating myself about the results- that they look almost perfect at first glance, yet you drill down a bit closer and you see another "zombie hand". The resolution issue you mention is definitely something I'm painfully aware of- it just comes down to lack of memory resources to support bigger renderings. That's going to be something I'm going to try to attack next.

Hey, thanks for replying! However, I feel like you glossed over the proposed workaround, which I feel is appropriate (though more complicated if you want to implement"defade"), and extremely easy to implement. I took a couple minutes to write an octave script that implement the workaround [1], it would have been even easier if both images had already been distinct files, and perfectly aligned. The basic idea here is…

Oh shit yeah that really does look good! Amazing really. Ok...I'm going to put these notes on the project board.

Yes..I definitely glossed over the proposed workaround and I apologize. Thanks for this.

Re: Colorizing and restoring old images with deep learning

#103
post #102
post #99

Earlier quoted context omitted.

Hey, thanks for replying! However, I feel like you glossed over the proposed workaround, which I feel is appropriate (though more complicated if you want to implement"defade"), and extremely easy to implement. I took a couple minutes to write an octave script that implement the workaround [1], it would have been even easier if both images had already been distinct files, and perfectly aligned. The basic idea here is…

Oh shit yeah that really does look good! Amazing really. Ok...I'm going to put these notes on the project board. Yes..I definitely glossed over the proposed workaround and I apologize. Thanks for this.

No problem :)

Although I would have made it a fully-fledged github issue, with a link in your board, instead of a text entry, to add supplementary material in the issue thread.

Bonus: if you are only interested in chrominance, you can train your network to use YUV as an input instead, and output only UV. I suspect this might lead to substantial gains in the training time and network complexity.

Re: Colorizing and restoring old images with deep learning

#104
post #102

Earlier quoted context omitted.

Oh shit yeah that really does look good! Amazing really. Ok...I'm going to put these notes on the project board. Yes..I definitely glossed over the proposed workaround and I apologize. Thanks for this.

No problem :) Although I would have made it a fully-fledged github issue, with a link in your board, instead of a text entry, to add supplementary material in the issue thread. Bonus: if you are only interested in chrominance, you can train your network to use YUV as an input instead, and output only UV. I suspect this might lead to substantial gains in the training time and network complexity.

Yeah the more I churn over this idea in my head the more excited I get about it. This really sounds like a big win.

I'm not sure what I want to do about the Kanban board versus issues tracker yet... I'm used to JIRA mostly. I'll figure it out but do know your contribution is very very much appreciated. I don't think I would have come up with that.

Re: Colorizing and restoring old images with deep learning

#105
post #79
post #76

Earlier quoted context omitted.

It's Deep Learning, not much to do with any analytical model, it's not thinking like a human :-(. Recently even good NLP processing needs 24GB+ for training (won't fit into 16GB), a good quality colorizing (no spills, natural colors) could be expected to be as demanding. From the article: "BEEFY Graphics card. I'd really like to have more memory than the 11 GB in my GeForce 1080TI (11GB). You'll have a tough time wit…

I get that. I just have a hard time thinking that is "generalizing" the model, so much as making the model all encompassing.

It's the difference between the sense of training the model to be a "generalist" and it doing "generalizing".

I strongly doubt that you can "generalize" colourization in the sense that you talk about (over a wide variety of subject matter).

Re: Colorizing and restoring old images with deep learning

#106
post #102

Earlier quoted context omitted.

Oh shit yeah that really does look good! Amazing really. Ok...I'm going to put these notes on the project board. Yes..I definitely glossed over the proposed workaround and I apologize. Thanks for this.

No problem :) Although I would have made it a fully-fledged github issue, with a link in your board, instead of a text entry, to add supplementary material in the issue thread. Bonus: if you are only interested in chrominance, you can train your network to use YUV as an input instead, and output only UV. I suspect this might lead to substantial gains in the training time and network complexity.

Update: I got this working, and dude- it's so awesome in every way. This is the most substantial improvement I've seen yet. Most importantly- it massively reduces memory requirements. Thank you so much. I'll commit within a day or so and make sure to mention you, on Twitter.

Re: Colorizing and restoring old images with deep learning

#107
post #106

Earlier quoted context omitted.

No problem :) Although I would have made it a fully-fledged github issue, with a link in your board, instead of a text entry, to add supplementary material in the issue thread. Bonus: if you are only interested in chrominance, you can train your network to use YUV as an input instead, and output only UV. I suspect this might lead to substantial gains in the training time and network complexity.

Update: I got this working, and dude- it's so awesome in every way. This is the most substantial improvement I've seen yet. Most importantly- it massively reduces memory requirements. Thank you so much. I'll commit within a day or so and make sure to mention you, on Twitter.

Hey, thank you a lot, that's awesome! One more thing I recently thought about, but didn't get around to mention, is that you can probably reduce the input of your net to the Y (luminance) channel (with UV-only output), to trim it further ;)

But that might already be what you are doing, for all I know. I am just really glad I could be of any help! And this feels like an "free-lunch" improvement.

Post reply on HN