TakMan Posted May 27, 2020 Share Posted May 27, 2020 (edited) Sorry for the delay in posting, this has put us out of sequence now! I missed the opportunity to see how it had progressed yesterday and missed out on getting some great images after seeing the results on here! Still plenty of data to go through, but I'm pleased with this... perhaps my best solar image to date. Was very lucky with the superb seeing around 8.56am. Took my usual 6000-9000us exposures (which should allow me to process the solar surface and prom in one exposure), but as the seeing was so stable, I tried a 18000us exposure and went just for the prom. Best 400 frames from 1661. TSA102s > Baader 2" UV/IR on the TV diagonal > Quark Chromo > Basler acA1920-155um (Sony IMX 174m). Captured in Basler's Pylon software as separate Mono12P (packed).tif files on a MacBook Pro as it doesn't allow saving out as a movie file)! Processed in AS!2 and ImPPG (via Wine), then PS CC2017 Two colour variations: I've tried making a rough 'scale image' using this chaps resource (it was linked to a week ago or so): https://sites.google.com/site/astroblue1/astronomie/brico-utiles And now onto my issue. As some of you who've read my previous posts will be aware, SGL member Vlaiv has been helping me sort the optimum gain and offset for this Sony 174 based camera (all new to me being a CCD based deep sky imager). We started with Mono12P as it offered increased bit depth but faster capture rates (32fps more), over 'standard' Mono12. Then I switched to Mono8, to sort the best settings. In Mono8, I’m getting very obvious vertical lines in the Dark/Master Dark Flames. They are also apparent in the master BIAS frames (that we used to measure the correct gain/offset), the flats/master flats and also the dark ‘void of space’ areas in the lights and in the final image. We have no idea why. I've changed cables, exposure settings, computer ports. Until James who writes OACapture supports the camera, I can’t test to see if it is perhaps a software issue… They are not (or no where near as obvious) in the Mono12 or 12P data...? Before anyone asks, Mono12P isn’t something that most software would recognise, but the Basler software obviously sorts and saves the .tif files in a standard way, so that AutoStakkert, Photoshop, etc can open. Does anyone have any ideas...? Have any other 174 chip camera users seen these vertical lines (see screen grabs below)..? For reference, the settings we came up with are: Mono8 - Gain 30.5 Db / Offset (Black level Dn) 15 Mono12/12P - Gain 18.5Db / Offset (Black level Dn) 40 ----- Mono12P master dark_stretched in Ps Mono8 master dark_stretched in Ps - see vertical lines Mono8 master flat 2000ms_stretched in Ps - again you can see stronger vertical lines in the Mono8 over the Mono12P... Mono12P master flat 11000ms_stretched in Ps Regards, Damian Edited May 27, 2020 by TakMan 5 Link to comment Share on other sites More sharing options...
Kitsunegari Posted May 27, 2020 Share Posted May 27, 2020 Just a guess but maybe the mac handles the global shutter a bit slowly with camera refresh rate and data capture rate? IF monoP stands for "progressive", then this could relate to image flicker and scan line writing. Back in the early days of hdtv's , interlacing was a big problem where the image was made of individual odd/even lines that refreshed a bit slow so you could see them visually. Then progressive scan came out, but the rate of refresh took a while to catch up with it and special hardware had to be adapted to allow quicker image processing . (most nvidia cards have no problems reproducing the video and all the video encoders are built into the windows devices by default) Mac's are a bit slow on industrial standards, and are typically proprietory based so they have issues with 3rd party software development that doesnt pay for some patent or trademark support. https://en.wikipedia.org/wiki/Progressive_scan Not sure on the video writing / handling of mac, but i know there are tiny bugs like this in reference to how the images are refreshed on the screen in apple products compared to microsoft products. Basler pylon is not exactly an industry standard program that apple would be looking at for compatibility. You may have to rummage through the "pylon guru" settings for an interlace button, or rate of refresh button. Link to comment Share on other sites More sharing options...
TakMan Posted May 27, 2020 Author Share Posted May 27, 2020 Thanks for your thoughts on this. P stands for packed, not progressive. Plus it's the Mono8 data that is showing the vertical lines, Mono12/12P is fine... Here is the info from Basler: Link to comment Share on other sites More sharing options...
Pete Presland Posted May 29, 2020 Share Posted May 29, 2020 Excellent detail visible there. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now