I'll grab that, woah, yes that's large. As an afterthought -- if you have
darktable -- just use the retouch tool. It'll be quick, easy, and like
magic!
On Friday, March 4, 2022 at 4:25:22 PM UTC-8 johnfi...@gmail.com wrote:
> My existing examples are absurdly large. I don't mind putting one
My existing examples are absurdly large. I don't mind putting one on a
google drive freely accessible. But you might mind trying to download and
work with it.
For several reasons, I prefer to fix the gaps after blending the panorama,
rather than fix individual photos before. One reason is that
... Currently it does stop because there can be areas at the left and right
edges of panaromas that are transparent after the crop, and the barrel
distortion correction has left a concave area which I'd assume a **user**
might want to repair in postprocessing after running Skyfill...
On
Fillsky should work for those problems -- any area *above* the detected
end of sky which is black (i.e. r,g,b all 0), or alpha < 1. will be filled
with the modelled esimate of the sky color. But the trick will be to
apply a test mask (-tm) to the area so the
end of sky detection
On March 4, 2022 8:51:50 AM HST, "johnfi...@gmail.com"
wrote:
> I got dirt on the sensor of my camera at the start of my vacation (I'm not
> used to this type of camera) and the air bulb I had could not blow the dirt
> off and I didn't have a cleaning kit. So all my photos have dirt
I have many small isolated gaps in the sky of my photos from my recent
vacation. That is a bit different from the example use of FillSky.
Given how many different things I'm trying to learn to use at once now, I'd
appreciate knowing whether FillSky is the right tool before I take time to
I cannot answer your main question, but if you want to know the command
line options hugin passes to enblend, you can:
1. start hugin and make all the settings you want, especially those in the
"stitch" tab, but instead of pressing the "stitch" button, save the project
file (assume the
Hi Kay,
I've now started working on the packaging.
Could you tell me which git commit your prerelease is based on? I need
something to work off.
I noticed that your master branch is still on a 2021-12-15 state and
development seems to be
happening on the associated_alpha branch. Which
