StarAlignment Register Union / Separate mode Bug

[RadarBoy]

Hi Folks;

I'm trying to do a 4 panel mosaic of the Veil, and have run across a bug which is driving me nuts.

I've used StarAlignment to create a mosaic, and now creating individual panels in order to be able to run Gradient Merge Mosaic.  The "Rough" mosaic I am using to align is 7983 x 6048 pixels.

However, the 4 panels, when then registered with Register Union/ Separate mode to create each panel for GMM end up having slightly different sizes, with an extra row of pixels added one at least one of the panels, bringing it to 7984x6048.

I'm assuming this is a bug?  Is there a workaround available?  This is not the first time I have seen this behaviour.

Version 1.08.06.1475 on Windows 10.

[dave_galera]

When I do a mosaic the first Star Align is Register Union Mosaic, then to create the individual images for Gradient Merge Mosaic I Star Align with Register Match Image with Frame Adaption checked and specifying the output from the first Star Align as reference image template. This automatically calculates the final mosaic image size so everything fits correctly.

This always works for me without any problems, this video shows the technique using Register Match Image https://www.youtube.com/watch?v=H2r3ZYqCaP8.

It really needs someone with more knowledge than me to directly answer your question........

[pfile]

i have seen this problem long ago, and i can't remember anymore if it was user error or not.

IMO it's a better idea to use the MosaicByCoordinates script to generate the input panes for GradientsMergeMosaic. there's essentially a 0% probability that MBC will fail, as long as you can successfully solve your panes with ImageSolver. with StarAlignment based methods eventually you get into a situation where you need to restrict star matching to previews as the mosaic grows and it's kind of a pain.

rob

[starhopper]

Hi Folks;I'm assuming this is a bug?  Is there a workaround available?  This is not the first time I have seen this behaviour.Version 1.08.06.1475 on Windows 10.

I can confirm this behavour. This ended with a error in GradienMergeMosaic claiming that image size is different.
This was not the case in older versions StarAlignment.

Thomas

[peabody1998]

I too have noticed this behavoir  ( in the previous version too). Appears to be a bug but a work around is to resample the images to ensure all the panels are the same exact size.

--Rich