black screen after integration

What happens when you turn off opengl by clicking on that GL button on top of the screen of APP?

Thanks for responding Vincent. I try that too. No difference.

Stretch and DDP are also activated.

 above a 5 files integration file133 MB

this is integration file of the 119 files  156 MB.  See fits header for difference .

Mm, I see a lot of NaN values in there which is not quite right. You used the exact same workflow, using the same calibration files etc, for the bigger integration? I think I'd need to see the data to be sure what happens.

Yes same workflow. With or without calibration with Darks give the same result. All lights where made with ASI 294 MC 

What files are you interested in? And how do I deliver these ? We tranfer?

So the same problem with different deepsky objects. Is there a limit fore the the amount of files? 

There is no real limit no, apart from the amount of memory resources you can give app. Just try what minimal amount gives you the black integration and include the master calibration files as well.

Go to https://upload.astropixelprocessor.com and use upload1 (or upload2 till 5) as username and password will then be the same as the username.

Create a directory named “dickvantatenhove-blackresult” and upload in there. Thank you!

I have the same problem. Integrating 50 frames made with ASI 183 MC Pro and the Optolong L-Pro filter. Histogram shows nothing, image absolutely black. I am using no flats, 50 darks and 50 bias frames.

I just integrated 50 L-eNhance frames. Same problem.

This weekend I stacked 75 L-eXtreme pics for one target and 110 L-Pro pics for another target without any issues at all. One of them I stacked using the Bayer/X-Trans drizzle mode and the other with the interpolation mode and both pictures came out beautifully well. The pics were taken with an ASI2600 (first target) and a Canon EOS 77D (second target) camera. Everything default, except the integration mode in case of the first target. I used darks but no flats for the first target and a master flat, master dark and master dark flat (from a previous session) for the second target. APP ran on a 2019 MacBook with macOS Catalina.

HTH, Wouter

OK. Because of astrovacation in the bush with very slow internet. I will sent the files later. To be continued

I decided to remake a stack of a previously succesfull image, using “old” darks and bias frames. That worked. So I went on remaking the “black” image, this time also using the “old” darks and bias frames. It works! It seems there is something wrong with the darks or bias frames, or with AstroPixelProcessor processing them. I am remaking the darks now and I will keep you informed about the result.

I remade the darks and bias frames. Now it works! Hm... This is what I did:

1. Using new darks and old bias frames I got a black image

2. Using an old masterdark and an old masterbias I got a good result

3. Using new darks and new bias frames I got a good result

APP can see the strange information it is writing in the FITS header. At that moment “the iron is hot”. APP can therefore give contextual information. So I consider the problem described in this post to be a defect in APP. Even if the darks or bias frames are the cause of the problem, APP can notice this. With respect to this phenomenon APP can be made more robust.

APP is not very buggy as that would cause way more people to shout at me. 😉 But I agree it would be nice if it sees these issues better and take corrective action on that. I'll talk about this with Mabula, will be further in the future though.

Bei mir tritt der Fehler jetzt auch auf. Nach der Integration bleib die Konsole dunkel. Es ist kein gestacktes Bild zu sehen. Auch Fitswork kann das Bild nicht anzeigen. Am Anfang war eigentlich alles gut deshalb habe ich mir die Vollversion gekauft. 

Aber jetzt habe ich ein Programm was nicht funktioniert und es gibt auch keine Anleitung dazu - sehr schade!

Ich bin mal gespannt, ob mir hier jemand helfen kann - ansonsten muss ich auf Deepskystacker zurückgehen.

Gruß 

Norbert

“further in the future”... May be that is not good enough, Vincent! I am sure there is a bug here. After more than 40 years of high tech SW development I smell bugs!

It might still be an issue in the calibration data as well, which seems to have been the case. That's not necessarily a bug but a case where APP is assuming the data to be correct (it can't always tell of course). It would be nice to have some extra checks on things like header info for sure.

@nobbybuddy

Can you try without calibration frames? As you can see above, remaking the calibration files and checking them to be good, solved the issue.

Nach Tests steht einwandfrei fest, dass der Fehler durch die Darks ausgelöst wird. Die Kalibration ist wohl von der sehr korrekten Erstellung der Darks abhängig. Der ISO Wert darf nicht von dem der Lights abweichen. Ohne Darks und nur mit Lights und Flats funktioniert die Integration einwandfrei.

Ich habe noch eine Zusatzfrage. Meine Autosafe-Fits enthalten immer eine starke Vignettierung, möglicherweise vom Teleobjektiv. Welche Einstellung musss ich bei den Tools vornehmen, um die Vignette geringer zu bekommen. 

Vielen Dank

Beste Grüße

Norbert

@nobbybuddyI think that Astro Pixel Processor should tell you this at the moment it detects it. Now it simply fails. So I do not agree with those that would say that this is not an APP issue.

Posted by: @nobbybuddy

Ich habe noch eine Zusatzfrage. Meine Autosafe-Fits enthalten immer eine starke Vignettierung, möglicherweise vom Teleobjektiv. Welche Einstellung musss ich bei den Tools vornehmen, um die Vignette geringer zu bekommen. 

Are you talking about the saving of the integration itself? If you use flats they should take care of vignetting. Otherwise you need to try and improve that by using either a artificial flat or light pollution correction in tab 9.

@jan-monsuur

Well it would be nice indeed if APP can actually tell that and gracefully point you to that, it seems this isn't super trivial apparently. I will talk about this with Mabula.

@vincent-modThanks!

I am having this problem too now, with an ASI294MC Pro, using 180 seconds lights/darks that I think I have used successfully before, shot at same temp, exposure length, and gain as the lights. If I don't calibrate with darks I get a proper final image, but with darks the final image is blank. I have 31 lights to process and it doesn't matter if I use just 3 or all 31 lights, I get the same problem.

Is there a resolution or workaround, or do we even know what is causing the problem yet?

Regards,

Chris M

Looking at what the solution for most in this thread is, is making the darks again and checking carefully if all parameters are correct when taking them. Like offset not being 0, correct gain, time etc. Usually this is a calibration data issue. Also make sure you don't use the darks with bias corrected already for instance as that may then be done twice, which is not correct either.

Posted by: @vincent-mod

Looking at what the solution for most in this thread is, is making the darks again and checking carefully if all parameters are correct when taking them. Like offset not being 0, correct gain, time etc. Usually this is a calibration data issue. Also make sure you don't use the darks with bias corrected already for instance as that may then be done twice, which is not correct either.

Making a set of new darks fixed the problem for me, not that I can work out what was wrong with the old darks as they had correct temp, gain, offset, and exposure length for the set of lights being processed. It was only my 180second darks that were giving the problem, not the rest of my current darks library for other exposure lengths.

Cheers and thanks,
Chris M 

Excellent Chris! It may have been a little thing that you overlooked or something changed due to another program (happens as well sometimes), can be a number of things. But it works again, which is great. 🙂

Was this issue resolved? I am suddenly having the same problem.

If I stack 2 lights plus master dark everything is fine

If I stack 50 lights plus one master dark using the process everything is black.

Any suggestions?

This problem has now reoccurred for me, and I have noticed that background neutralisation says it has failed on all subs. It is happening now with my 300 second exposures (last time it was with my 180 sec ones). I can try reshooting the 300 sec darks next week and see if that fixes the problem as it did last time with the 180 sec exposures, but its' very weird.

Chris M

Yes, not sure why, I think it's something that is going wrong for some people now and again with darks, it's not an issue in the software. Carefully checking you have the correct offsets, gain, etc. and then re-shooting normally resolves these issues.

Thanks Vincent. I have worked out what caused it for me this time. I found that I had accidentally shot the lights with my camera set at a non-normal gain, which was very different from the gain of the darks! No wonder it didn't work well!

Cheers, Chris M