Hi Scott (@srosenfraz),

Hmm, I think it will not be an explanation in this case since the license file is still stored locally in your OS user directory. I am also not sure yet if the bug relates to file locking, but I strongly suspect it.

I access files over network and a usb3 drive without running into this problem.. so I need to test more to…[Read more]

Hi Mabula –

Regarding the file locking – FYI, I do have a local network (Windows 7) with some mapped drives.  Perhaps something about this configuration enforces stricter file locking?

My startup times for APP are fine – usually around 5 seconds. However, I have had some occasions when I receive a message that my license could not be verified. If I had to guess, these usually seem to coincide with times when I’ve shut down APP and started it up soon thereafter. If it helps, the most recent time I had this trouble would have bee…[Read more]

My startup times for APP are fine – usually around 5 seconds.  However, I have had some occasions when I receive a message that my license could not be verified.  If I had to guess, these usually seem to coincide with times when I’ve shut down APP and started it up soon thereafter.  If it helps, the most recent time I had this trouble would ha…[Read more]

Hi Mabula –

I wouldn’t worry too much about the error I was receiving. I eventually found that the problem was coming from trying to integrate the mosaic with the Integrate mode of Reference. Once I changed that to Full, I stopped receiving those errors and the combined panels were no longer ending up the size of a single panel. So, this one was…[Read more]

Hi Scott (@srosenfraz),

The first bug that you describe is a new one for me. I know that at 88% the stack should be finished. Then from 88% to 100% APP performs analysis of the stack and saves it to your harddrive.

So it seems that the stack possibly isn’t there, possibly to a problem in registration.

If you could share these panels, so I can…[Read more]

Ok, I’m sorry to keep wasting bandwidth on half solving my own problems, but it’s been a learning experience at least!  I just found that my problem with the mosaic not expanding as I add frames is that I had chosen a mode of “reference” in 6) Integrate.  Changing that to Full solved this problem as well as the majority of the registration p…[Read more]

A followup to this message.  I think the problem I’ve been having may be related to the # of overlapping frames.  I’ve been able to get past the message by choosing the same number of overlapping frames as the total number of frames to be integrated.  So far, I’ve been able to integrate 3, 4, and 5 panels.  I tried doing 9, but it failed with a d…[Read more]

Thank you for that info, Mabula.  I wasn’t sure if the 1 core was correct, so I’m glad it’s working as designed.  From what I know about you, I’m not sensing that you’re particularly slim on algebra courses, though!

Well, I’m having some issues trying to get it all to work, but I want to try a few more possibilities before I come to you to r…[Read more]

Hi Scott (@srosenfraz),

Thank you for your feedback ;-)

In the case of distortion correction, at the end of the registration, when the multiple view algorithm starts, a calculation is started that can’t be implemented using multiple cores. So you will only see 1 cpu core working, that’s correct. I don’t think I can make these algorithms…[Read more]

Mabula – I’m not sure if this is new with 1.038, but I’ve been seeing a few processes that I would expect to be CPU intensive that don’t appear to be using all cores.  I’ve been working on a 14 panel mosaic, and when I was having it create a distortion model, the CPU usage was pegged at 25% on my quad core machine.  The same thing appears to be h…[Read more]

” But it will prevent a lot of DSLR users, who did it in the wrong way, from processing old data right?”

No completely wrong I am afraid…

Calibrating old data is perfectly fine and possible in APP, why wouldn’t it be?

I am even calibrating old data from 2013 from Scott, @srosenfraz, which was sub-optimal calibrated with Images Plus. (Scott…[Read more]

@srosenfraz, okay, that makes perfectly sense then 😉

Providing dark scaling is on my todo list, but indeed, I would advise everyone to only take “short cuts” for previews or if no other option is available…

As far as IP using the bias for dark scaling – I believe the methodology is to subtract the bias from the dark so that only the dark signal is left.  Then the dark can be scaled.  So, let’s say I have a 5 minute dark and want to use it for a 10 minute light.  If I subtract the bias from the dark, I can scale the dark x 2 to match the (p…[Read more]

Hi @srosenfraz,

Let me try…

1) The creation of 2 bad pixel maps would happen if the instrument name of the darks and or flats are not equal. The Bad Pixel Map will be matched with lights or flats of the same instrument.

Sometimes, different capture programs will output different isntrument names, so be aware of this.

And there is a good and…[Read more]

@srosenfraz, personally I don’t have experience with IP, but I would think bias frames can’t be used for dark scaling since a bias frame is not a representation of any significant dark current.

Dark scaling is on my todo list, since APP can’t do this yet. But having said that, dark scaling should always be considered as a last resort. It’s always…[Read more]