Search the Community
Showing results for tags 'firecapture'.
Found 5 results
Apologies for asking a question that must have been asked a thosand times before - but where can I find a simple step by step guide to capturing and processing a planetary image? The bright shiny red ZWO camera arrived today , and I have got it talking to FireCapture on the laptop, and even making a short movie. The movie is monochrome (the camera label assures me it's colour) but I mustn't quibble. But then what happens? Does SharpCap sort and stack the frames? I crave simplicity, and (preferably) written answers (on one side of a postcard). Can anyone point me in the right direction?
Hey. I use EZPlanetary with my QHY5L-II. Piece of cake. I wanted to try Firecapture. Firstly; where is the damn capture button? Secondly, when viewing the image on the laptop screen, I can see cross hatching everywhere. This happens in EZPlanetary when the RB GB etc is set wrong. How is this changed in Firecapture? Any help would be great. Thanks Skips
Hi all. I'm using Firecapture to image Jupiter with ASI290MM with an EFW and something odd is going on with my red histos. I set all channels to the same exposure and gain - I realise this isnt neccesarily the best way, but for now thats what I do As I do the captures, typically 4 runs of 120secs per colour, the histo looks consistent - about 66% for R and G and about 55% for blue. But when I l look at the log files, the reported max and average histo values for the red captures are OK on the first capture, but greatly reduced on all the subsequent red ones. The G and B histos are consistent throughout. So for example last night I did 6 runs, for the red max/average histos I got: 1. 162/63% 2. 97/38% 3. 107/41% 4. 112/43% 5. 101/39% 6. 103/40% I watched the histo carefully on the last run and it didnt dip below 60%. So how can this happen??? I'd be really gratefull for any answeres! One other unrelated - I think - issue, is that on subsequent runs, because I dont have a delay set, I catch the filter as it switches in at the beginning of the run - except on the first run of course. Hmmmm as I type this I'm just cross checking with the unsorted AVI files in AS!2 and I see that not only am I getting a few chopped up frames as the filter switches in, but also neearly 100 of the previous run. So at the beginning of my 2nd red run I have about 100 blue images (approx 110 fps) Clearly I could sort this by having a delay. But right now I have 2 issues: 1. Is the reported histo value affected by the carry over of frames from the previous colour run? 2. Crucially, the AS!2 sorted AVI has included at the beginning some dodgy frames at the beginning, ie deemed to be good quality, which are from the previous colour, and also some with half a frame from the filter switch which for some reason arent rejected. So - how do I delete individual frames from the sorted file??? I cant see any way to do this. Alternatively, can I delete them in PIPP which I run everything thought first? Or maybe PIPP has a setting to reject dodgy frames with mismatched data or half frames.? Sorry people - lots of questions!! Would really appreciate any help, especially as Jupiter is about to exit, stage right!!
Hi, After returning to imaging after a long break I have been having a problem using Firecapture with my QHY5LIIc camera. The captures keep coming out with a 'hatch' pattern over them like you are looking through a cloth. The below image is a crop of a Luna image which has been enlarged 400x to clearly show the pattern although it is clear enough on the original image I wasn't sure how it would appear after uploading. Does anyone know what causes this artefact and how I can stop it from happening in the future?