Grid Lines
-
Timboy16059
- Posts: 6
- Joined: Wed Nov 11, 2026 8:49 pm
Grid Lines
I'm getting tiny grid lines visible in my Moon images taken with an ASI585MC Pro on my 8SE, mainly in lower ROI images but still visible in all. I save the files as RAW 8 TIFs now because I first noticed them in JPG images, but they are still there in the TIF images. I'm wondering if there is another setting - like debayering - I should be using. Or maybe the cable is too long? I'm using a 20' repeater cable and a 3.0 powered hub which seems to work okay as far as the camera isn't dropping out. TIA.
- admin
- Site Admin
- Posts: 17580
- Joined: Sat Feb 11, 2017 3:52 pm
- Location: Vale of the White Horse, UK
- Contact:
Re: Grid Lines
Hi,
if you zoom in on the image to the pixel level and you see a 'chessboard' pattern and is monochrome then that means you are looking at the RAW version of the image and you need to set up whatever viewing software you are using to debayer the image. If you see a chessboard pattern and the image is funny colours (often purple) then the debayering is happening, but using the wrong settings, so the R/G/B pixels are being mixed up. In either of these cases, the image can still look odd when zoomed out to the point that the individual pixels are no longer visible - depending on how your viewer software draws the image there may still be visible lines in both directions that might well change position and number as you zoom in/out.
If you are seeing lines that only run in the horizontal direction and that seem to be brighter or darker then you may have horizontal banding - this can happen on some CMOS cameras, particularly if the voltage being supplied to the camera over USB or a 12V input is fluctuating. This doesn't sound quite right for what you are describing though.
If neither of these quite fit then it might be best to post a screenshot showing what you see - a picture is worth 1000 words
cheers,
Robin
if you zoom in on the image to the pixel level and you see a 'chessboard' pattern and is monochrome then that means you are looking at the RAW version of the image and you need to set up whatever viewing software you are using to debayer the image. If you see a chessboard pattern and the image is funny colours (often purple) then the debayering is happening, but using the wrong settings, so the R/G/B pixels are being mixed up. In either of these cases, the image can still look odd when zoomed out to the point that the individual pixels are no longer visible - depending on how your viewer software draws the image there may still be visible lines in both directions that might well change position and number as you zoom in/out.
If you are seeing lines that only run in the horizontal direction and that seem to be brighter or darker then you may have horizontal banding - this can happen on some CMOS cameras, particularly if the voltage being supplied to the camera over USB or a 12V input is fluctuating. This doesn't sound quite right for what you are describing though.
If neither of these quite fit then it might be best to post a screenshot showing what you see - a picture is worth 1000 words
cheers,
Robin
-
Timboy16059
- Posts: 6
- Joined: Wed Nov 11, 2026 8:49 pm
Re: Grid Lines
Thank you, Robin.
I was just sitting down to type a comment stating that I may have solved my problem last night through trial and error (mostly error - lol). Turns out I needed to set the Video Format AKA Color Space from the default of RAW8 to RGB24 and save my snapshot files as PNG and my video files as AVI. That might not be the perfect way to solve my problem, but it seems to work for what I want to do, as the images I took and uploaded to FB all looked fine to me last night, even on a 4-minute video of Saturn that I aligned and stacked using the usual suspects. I'll do more extensive testing today with the images and videos I took last night. So this may or may not be solved but it seemed like a good work-around at the moment last night and still does this morning.
My mind-set and goal last night was to keep myself warm inside, sitting at my laptop, which meant I had to make the 20-foot repeater cable to the camera on my scope outside on the back deck work. That put my focus on SharpCap settings. I may want to make more adjustments b/c my ASI585MC Pro camera crashed SharpCap 3 times last night during my 4-hour testing session. I considered it to be a minor annoyance at the time for what I was able to achieve. THAT might still be a cable issue. Perhaps I don't need to go to RGB24 for AVI file captures. But for snapshots, which I do use, it seems the way to go - for now.
I prefer to save my video files as AVI, since that format works for me and the subsequent aligning/stacking goes very quickly - unlike how it goes when I have to convert SER files to AVI files first. Perhaps I don't get quite the quality others get if they save vids to SER first and then convert, but for my scrapbook studies, it serves just fine.
I'm learning this as I go, so there will undoubtedly be modifications to my workflow as I learn new things.
Thank you for your interest. Perhaps - with the information I have written above - you may see a different and better solution.
OBTW, the grid I was referring to are very fine squares that sometimes are so small they are virtually invisible and yet sometimes - at different magnifications and/or different ROIs - are extremely visible and ruin an otherwise good image. I thought maybe it was just a BlogSpot and FaceBook aberration due to compression, but I don't see them in anyone else's magnificent images of the moon, etc so I knew it was a problem unique to me that I had to solve.
Thanks again for taking the time to review this thread.
Tim
I was just sitting down to type a comment stating that I may have solved my problem last night through trial and error (mostly error - lol). Turns out I needed to set the Video Format AKA Color Space from the default of RAW8 to RGB24 and save my snapshot files as PNG and my video files as AVI. That might not be the perfect way to solve my problem, but it seems to work for what I want to do, as the images I took and uploaded to FB all looked fine to me last night, even on a 4-minute video of Saturn that I aligned and stacked using the usual suspects. I'll do more extensive testing today with the images and videos I took last night. So this may or may not be solved but it seemed like a good work-around at the moment last night and still does this morning.
My mind-set and goal last night was to keep myself warm inside, sitting at my laptop, which meant I had to make the 20-foot repeater cable to the camera on my scope outside on the back deck work. That put my focus on SharpCap settings. I may want to make more adjustments b/c my ASI585MC Pro camera crashed SharpCap 3 times last night during my 4-hour testing session. I considered it to be a minor annoyance at the time for what I was able to achieve. THAT might still be a cable issue. Perhaps I don't need to go to RGB24 for AVI file captures. But for snapshots, which I do use, it seems the way to go - for now.
I prefer to save my video files as AVI, since that format works for me and the subsequent aligning/stacking goes very quickly - unlike how it goes when I have to convert SER files to AVI files first. Perhaps I don't get quite the quality others get if they save vids to SER first and then convert, but for my scrapbook studies, it serves just fine.
I'm learning this as I go, so there will undoubtedly be modifications to my workflow as I learn new things.
Thank you for your interest. Perhaps - with the information I have written above - you may see a different and better solution.
OBTW, the grid I was referring to are very fine squares that sometimes are so small they are virtually invisible and yet sometimes - at different magnifications and/or different ROIs - are extremely visible and ruin an otherwise good image. I thought maybe it was just a BlogSpot and FaceBook aberration due to compression, but I don't see them in anyone else's magnificent images of the moon, etc so I knew it was a problem unique to me that I had to solve.
Thanks again for taking the time to review this thread.
Tim