Closed wyshmily closed 5 years ago
I think there is no any great idea behind this.
In the first case we concatenate foreground with alpha to output RGBA image that will be nicely displayed in most of image viewers and can be easily composed on the new background with almost any image editor.
Since solving for foreground with known alpha is very specific usecase, I made an assumption that user knows what he/she wants to do with foreground and background so we can just output raw data. Probably, it was bad design decision.
I think PR adding --rgba
output option to solve_foreground_background.py
and keeping --foreground
and --background
outputs intact is warmly welcome. I hope @MarcoForte will agree with me.
@merofeev Thank you very much.
I am working on developing a tool (for windows) with the "intelligent image cut out" functionality, and the cut out calculation should take place in the client side.
I use this code and found it a bit slow without gpu acceleration, even if I zoom in the image to about 200 pixels.
Can you provide some suggestion?
Can you provide some suggestion?
In your case I would try two things:
@merofeev Thanks a lot !
I see this code line is called when --solve-fg is setted![image](https://user-images.githubusercontent.com/18300550/53148505-caefb200-35e5-11e9-9975-4dfd5ad907c3.png)
But in solve_foreground_background.py there is not.![image](https://user-images.githubusercontent.com/18300550/53148409-8f54e800-35e5-11e9-8dfc-72e7f4c50a1c.png)
Just confused why is that?