black screen after ...
 
Share:
Notifications
Clear all

31 July 2020 - Comet Registration video tutorial using APP 1.083-beta1 released.

30 July 2020 - APP 1.083-beta1 has been released introducing Comet processing! This 1st beta has comet registration. The stable release will also include special comet integration modes.

9 July 2020 - New and updated video tutorial using APP 1.081: Complete LRGB Tutorial of NGC292, The Small Magellanic Cloud by Christian Sasse (iTelescope.net) and Mabula Haverkamp

2019 September: Astro Pixel Processor and iTelescope.net celebrate a new Partnership!

black screen after integration  

Page 1 / 2
  RSS

(@dickvantatenhove)
Brown Dwarf Customer
Joined: 3 years ago
Posts: 7
September 15, 2020 15:26  

Hi,

If I integrate a few files  f.i 5, it will result in an integration Image.

When I integrate all 120 files it results in a black screen after integration. I downloaded the latest version of App, same result. Same with 60 frames of another deepsky object.

Open GL is on. I have 8 mb Ram on board and 200 gy free spac. All individual frames looks OK.

Anyone has a solution?

Dick van Tatenhove


ReplyQuote
(@vincent-mod)
Quasar Admin
Joined: 3 years ago
Posts: 2453
September 15, 2020 15:29  

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


ReplyQuote
(@dickvantatenhove)
Brown Dwarf Customer
Joined: 3 years ago
Posts: 7
September 15, 2020 15:48  

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

Stretch and DDP are also activated.

image

 above a 5 files integration file133 MB

image

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

 

 

This post was modified 1 month ago by DickvanTatenhove

ReplyQuote
(@vincent-mod)
Quasar Admin
Joined: 3 years ago
Posts: 2453
September 15, 2020 16:13  

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.


ReplyQuote
(@dickvantatenhove)
Brown Dwarf Customer
Joined: 3 years ago
Posts: 7
September 15, 2020 16:25  

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? 

This post was modified 1 month ago by DickvanTatenhove

ReplyQuote
(@vincent-mod)
Quasar Admin
Joined: 3 years ago
Posts: 2453
September 15, 2020 17:13  

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!


ReplyQuote
(@jan-monsuur)
Brown Dwarf Customer
Joined: 2 years ago
Posts: 9
September 16, 2020 12:02  

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.


ReplyQuote
(@jan-monsuur)
Brown Dwarf Customer
Joined: 2 years ago
Posts: 9
September 16, 2020 12:28  

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


ReplyQuote
(@wvreeven)
Neutron Star Customer
Joined: 2 years ago
Posts: 239
September 16, 2020 13:22  

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


ReplyQuote
(@dickvantatenhove)
Brown Dwarf Customer
Joined: 3 years ago
Posts: 7
September 16, 2020 13:57  

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


ReplyQuote
(@jan-monsuur)
Brown Dwarf Customer
Joined: 2 years ago
Posts: 9
September 16, 2020 15:06  

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.


(@jan-monsuur)
Brown Dwarf Customer
Joined: 2 years ago
Posts: 9
September 16, 2020 16:12  

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.

This post was modified 1 month ago by Jan Monsuur

(@vincent-mod)
Quasar Admin
Joined: 3 years ago
Posts: 2453
September 17, 2020 14:29  

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.


ReplyQuote
(@nobbybuddy)
Hydrogen Atom Customer
Joined: 2 years ago
Posts: 2
September 19, 2020 12:46  

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

 


ReplyQuote
(@jan-monsuur)
Brown Dwarf Customer
Joined: 2 years ago
Posts: 9
September 19, 2020 13:20  

“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!


ReplyQuote
(@vincent-mod)
Quasar Admin
Joined: 3 years ago
Posts: 2453
September 20, 2020 11:25  

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.


ReplyQuote
(@vincent-mod)
Quasar Admin
Joined: 3 years ago
Posts: 2453
September 20, 2020 11:26  

@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.


ReplyQuote
(@nobbybuddy)
Hydrogen Atom Customer
Joined: 2 years ago
Posts: 2
September 24, 2020 18:23  

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


ReplyQuote
(@jan-monsuur)
Brown Dwarf Customer
Joined: 2 years ago
Posts: 9
September 24, 2020 19:11  

@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.


ReplyQuote
(@vincent-mod)
Quasar Admin
Joined: 3 years ago
Posts: 2453
September 25, 2020 12:57  
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.


ReplyQuote
Page 1 / 2
Share: