Jump to content

Banner.jpg.b89429c566825f6ab32bcafbada449c9.jpg

Phillyo

Members
  • Posts

    970
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Phillyo

  1. Who has told you that you can't power your EQ6-R Pro via the ASIAIR Plus?
  2. Tried cropping prior to processing and gave it another go. Maybe looks a little better? Meh.
  3. I had a little play yesterday and it made things look better definitely, but you really need to look close to see the difference with my setup (Samyang 135, IMX571 camera). I've attached a before and after (two slightly different processing but very similar other than colours) along with the full size image to show how tight the crop is. I like the result, but I'm not sure if it's worth £100. Just realised they're different sizes, never mind. You get the idea hopefully!
  4. Thanks Wim, The problem is that the glow extends quite far into the frame and even if I cropped it the glow would still show up. Never mind! I'll do better next time Phil
  5. Another image with the SY135. More details can be found in the Deep Sky Imaging page. About 14 hours of data, Risingcam IMX571, SY135, 60s exposures, EQ6-R Pro, L-Pro UV/IR filter. NINA and Pixinsight for software. The bright glow is Mars....*facepalm*. I didn't even realise it was there until too late, but it is what it is. Phil
  6. We've actually had a couple of clear nights here the last few nights, albeit with a moon rising later in the evening. I decided to try and add a bunch more data over two nights of a widefield image around Barnard 10. What I had failed to notice, however, was that Mars was making it's way through that part of the sky. Much to my frustration I didn't notice until I got up the next morning and stacked the data together and saw a huge glow just off frame. Still, it is what it is and I've learnt a valuable lesson here. So, I've processed it as best I can (I really don't know how to process dark nebula very well at all) and I have an image I do like, just annoying to have some of it ruined by the glow from Mars. So this is 784 x 1min exposures (13hours 4min) taken with the Risingcam IMX571 OSC camerea. L-Pro filter, Samyang 135@ F/3.5 using stop down rings. NINA for capture, Pixinsight for editing. Any advice on how to edit this better would be very greatly appreciated. I can even upload the XSIF files (normal and Drizzle) if anyone wants to have a go. Thanks for reading and looking, Phil.
  7. I watched most of the video posted by Adam Block last night and it looks fantastic. I'll be giving the free 30 day trial a go and will probably get it. If it works anywhere close to as well as noise and star xterminator then it'll be another fantastic bit of software/coding.
  8. I rarely do a re-calibration. Unless the orthogonal angle has changed, or unless I've moved my mount then there's no point. It doesn't matter where you're pointing in the sky, once you have a good calibration it won't change (except for orthogonal or mount position change). Guiding varies night to night. Sometimes around 0.5"RMS, sometimes closer to 1"RMS. The seeing is a larger determining factor for me.
  9. The checkerboard artefacts are from using StarXterminator. Give it a try with Starnet and see if it looks any different? I often use both and go with the best one.
  10. Thanks Scotty, I've posted a comment. See if he replies
  11. Good evening, Whenever I try to run the NSG script, Pixinsight shuts down and the error code "A breakpoint has been reached (Error 0x80000003)" and I have no idea what could be causing the issue. Just running WBPP doesn't have the same issues and I've never seen it anywhere else outside of using NSG within Pixinsight. Anyone have any ideas? Thanks, Phil.
  12. Only 1h 15min of data...that's about all I've had in weeks. Even then I've had to shoot through some high hazy clouds, hence the slightly fuzzy looking stars but I'm getting desperate now! Definitely need to add about 20x as much data to really do this justice, but we have what we have. Risingcam IMX571, Samyang 135 @ f3.5, UV/IR filter, EQ6-r Pro and 75ish x 60s exposures. Not my greatest work, but it's a start. Phil
  13. Gorgeous image! I don't know what your acquisition details are but you've pulled a lot out from one night. Great job!
  14. Light pollution or not, this is a really lovely capture of M45. Subtle processing to bring out the surround nebulosity is really nice too. Congrats!
  15. This is really nice. I love the detail you've captured and the processing too. I'm trying to gather a LOT of ha data for this to bring out the nebula that can be seen around it but it's turning out to be very hard, especially with the UK weather.
  16. Thanks Steve, very interested in this little scope as a step up from using the Samyang 135.
  17. Someone else asked that question and the reply from Sharpstar was that it's a completely different optical design? No idea. I'm sure there'll be some reviews from youtube types
  18. I saw on facebook this morning that Sharpstar are releasing a new ASKAR telescope, the 65PHQ. I can't remember the full spec but it's something like 65mm, 416mm focal length, f6.4 quintuplet scope with full frame sensor coverage. As for price, they've quoted $999 so probably over £1000 after uk tax etc. I wonder if anyone from @FLO could enlighten us with any further information?
  19. Just want to add a reminder than you don't need to purchase everything brand new. I'm likely selling a ZWO ASI533 soon and I have seen people selling the Samyang135 lens with adapters and mounting for good prices. That's always a good way to get into things rather than buying brand new. Phil
  20. So from 115 x 60s images, 6 of the them had that strange lines thing going on. Really strange!
  21. I'm taking some pictures at the moment and I've just had 1 frame do the exact same thing. Really strange and I have no idea what might be causing it!
  22. Ha, yeah I hear ya! I sometimes miss my old QSI583 CCD camera...but I don't miss the 20min exposure times required!! So, Risingcam have two different drivers for the camera. They have a native driver and an ASCOM driver. The native driver has an offset of 768 and a gain of 100. The ASCOM driver is different, but the actual results of the values remain the same (I can't remember exactly what the ASCOM default values are as I only really use the native drivers in NINA). I *THINK* it's something like gain 0 offset of 50, but don't quote me on that. However like I say, just because the gain of one of them is 100 and the other is 0 doesn't mean there's any actual difference in gain, it's just how the drivers display it. Same with offset. With my 533MC Pro, I also just left the gain and offset at default and just adjusted the exposure length to the target/conditions/filter etc. Hope that makes sense! Phil
  23. I don't have that exact set up, but I use the Risingcam IMX571 which I think is the same or similar sensor with the Samyang. I shoot at f3.5 using stop down rings and for narrowband (5nm Antlia ALP-T filter) I shoot 3min exposures as directed by NINA exposure calculator having done a sensor analysis in Sharpcap Pro. I don't mess with the gain or offset and leave them at default. NINA will be debayering and performing a stretch on your image, so it's a useful guide but don't look into it too much. As you say, you need to stack them and check them fully in PI before really getting an idea. For broadband I can shoot as short as 5 seconds in my area, but obviously that would fill my hard drive way too quick so I normally shoot 30, 60 or 120s exposures depending on the brightness of the target I'm aiming for. I live in a Bortle 4/5 area for reference.
  24. Where do you place the filter in this imaging train? Looks nice and tidy though!
  25. Thank you I do like this set up lol, very easy to get good results. Though I am considering getting an actual telescope soon, not too sure what yet though. That'll probably make things more interesting!!
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. By using this site, you agree to our Terms of Use.