UPDATE FROM MABULA
I have had a very rough 2 months unfortunately health wise. I was struck 3x in a row with bacterial infections. The second infection occurred after a routine hospital checkup and I became very sick. I had to rest and take a lot of antibiotics. Once I was recovering and restarting work 1 month ago, I again became sick. The infection was not yet gone, so even more antibiotics and rest was needed. Needless to say, it took a lot of my energy and I needed a lot of rest.
Finally, the infection is really gone and my energy is coming back step-by-step now and I have started work again. I am terribly sorry to have kept you waiting for support. I will address all outstanding questions and e-mails step-by step and will be on the forum daily from today.
APP 2.0.0-beta47 will come soon as well, a lot of work was already completed before I became very ill, so the release is also nearly ready for you. Beta47 will be much faster actually. Many workflows will be more than 2x faster, mosaics can even be 10x faster than before because registration really received a major boost... all compared to beta46. Before I release it, I will make sure that everything is working properly and then I will release it.
Hi,
how can I achieve this? APP does not do this, in registration it just stops (no specific error shown). Both files are rgb 32 bit fits data with a nikon dslr, lens 105mm and the other lrgb in 32bit rgb format done with a asi 6200mm and a 550mm focal length. Done with APP.
is it too far apart (resolution wise etc) or should it in principle work?
stefan
Anyone here?
so, again, now I put some more info in here:
screenshots of the data and the typical errors message I get are shown. No suggested setting works.
I would like to know, if in principle it should work and if yes, how?
When I use 400mm focal length data with the nikon dslr, registration works right away.
So it must be due to the resolution, meaning 105mm with 36 megapixel will not match 550mm with 61 megapixel...
400mm/Nikon: 2,5 arcsec/pixel
105mm/Nikon: 9,6 arcsec/pixel
550mm/6200mm: 1,4 arcsec/pixel
if so, what would be the shortest focal length used with a nikon d810a, pixelpitch 4,88 mju, to match a imx 455 chip, 3,76 mju using a 550mm scope?
Probably the best way would be to split the RGB frames and save them as R, G and B. These are then also mono and can be added like that. Load each camera and its data (including calibration data) into its own session. These should then result into integrated mono stacks. It should be possible to combine, but I'm not 100% sure this will work for all FOV's.
Probably the best way would be to split the RGB frames and save them as R, G and B. These are then also mono and can be added like that. Load each camera and its data (including calibration data) into its own session. These should then result into integrated mono stacks. It should be possible to combine, but I'm not 100% sure this will work for all FOV's.
hi vincent,
since it works, see my post, with 400mm, it is not neccessary to do this ...
Ah right, sorry missed that. There are a few ways to get the same result, my workflow is what I tend to do, but not required indeed. So if registration doesn't work there may be a limit, would you be able to share the data perhaps? I can check as well on my end and then let Mabula know.
@vincent-mod am uploading 2 files now, takes 20 min ...
Thanks, I have some data to process but will come back to you asap.
So I looked at panels, what I think is happening is that there are very little star pairs to properly align them. That or it is indeed too different.
So I looked at panels, what I think is happening is that there are very little star pairs to properly align them. That or it is indeed too different.
OK, thanx... guess in case trial&error then
