Jump to content

Banner.jpg.b83b14cd4142fe10848741bb2a14c66b.jpg

Space Cowboy

Members
  • Posts

    7,778
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by Space Cowboy

  1. On 03/11/2023 at 14:11, Kon said:

    I think we need to let June rest...😂....so many good captures that the imaging gods are punishing us now. I will probably tell my future grand children  about June 2023  😂. .

    June 2014 was pretty good too 😎 I'm not letting experiences like that rest.....without those memories i'd be packing this in lol

    • Haha 2
  2. 6 minutes ago, geoflewis said:

    I also use auto center ROI, but as you say, still have to watch that it doesn't drift off the sensor. That become even more of an issue if/when I add a barlow into the imaging train, which of course also leads to bigger file sizes. Sorry, I don't know what an NVMe SSD is, but it's not the speed of transfer that's an issue, just the size of the SSD.

    NVMe works as an external SSD plugged into the USB port so you can quickly transfer data if the lappy gets full. £50 for a good quality 1tb. There are cheaper makes but they can slow up as they get full.

    • Like 1
    • Thanks 1
  3. 58 minutes ago, geoflewis said:

    I agree, not much difference in speed, but a 20% reduction in file size, which is a significant win I think. Yes, I use a combination of FireCapture's ROI and Cut Out features to reduce file sizes. I could probably go a bit tighter, but I'm not using auto guidimg, so the target does drift within the ROI a bit, requiring me to nudge the mount with the HC every few minutes. I guess my next experiment might be to try autoguiding, though currently I don't know what I need for that with planetary imaging....

    Very true 20% extra disk space is a lot. My tracking is not good enough to use the crop feature so I use the auto centre of ROI but have to watch the planet doesn't eventually slide off the sensor.

    Have you tried a NVMe  SSD for fast data transfer? I can transfer 100 gigs from my laptop in 5 mins.

  4. 57 minutes ago, geoflewis said:

    I'm not sure how video derotation would help unless you were captureing everything in a very long SER file, as AS3! has no issue aligning the moon and shadows from a 1m SER.

    When I tried video derotation of Mars last year the file size of the derotated SER was approximately double the original SER, i.e a 6min SER at 3ms (330fps) with the small ROI 300x300 required for Mars was approx 10 GB, which after derotation was ~20GB. When I tried a larger ROI of 400x400 the original 6m SER was 18GB and the derotated SER 36GB. This was far too large, so I gave up derotating the SERs for Mars, as the rotation was minimal in 6 mins and I couldn't tell the difference.

    If I was going to try SER derotation for Jupiter, then I guess my workflow might go something like this:

    1. Capture a very long video, say 10m-15m (based on my 8ms capture speed, with the much larger ROI (600x600), the initial file would be ~50GB...🤯)
    2. Grade the video in PIPP to keep, say, just the best 20%, which I think would reduce the file to ~10GB
    3. Derotate the graded video in WinJupos.
    4. Stack in AS3!
    5. Other post processing, in Registax, Astrosurface, Image Analyser, etc.

    I'll be iterested to learn what you find if you do try it.

     

    Yep I used vid Derot on Mars a couple of times. The key for me is the field derotation which Derot of images does not do so possibly that would help with the transit.

    I've a feeling someone on CN said vid Derot was better for transits or I could have dreamt it. 🙂

    • Like 1
  5. 15 hours ago, geoflewis said:

    Thanks Stuart,

    I'm not derotating the videos, but derotating the TIFF stack of best 2000 frames from each video. Unfortunately the moon correction tool in WinJupos doesn't do a great job, when in actual transit, but it's just about ok when the moon is still off to the side.. It does align the moon and shadow, but leaves a nasty artifact around them, so I still have to photoshop (I actually use Affinity Photo now, but you know what I mean) the moon and shadow back in from a lower resolution single video stack, with as near identical time stamp as the derotate stack. To be honest it's a complete faff, but when the data is good its worth the extra messing around. However, it's why I'm not going to go for high res data if I do compile the GIF - even I don't have the stomach for photoshop moon and shadow corrections on ~100 separate images.

    I do have several external HDs for my archive, but a couple of years ago when I went to retrieve something, one of them the drive had died, losing several years of data. Actually I was fortunate that I had a lot of that on more than one drive, but I couldn't recover that HD I sent it to a friend who works in the IT industry, who was able to recover the images (SERS and TIFFs), but all the associted EXIF data, etc., was lost, so I just had a buch of videos with no file names, date, or time stamp, so pretty damn useless to me. After that I took the decision to upload to cloud as well as keeping local HD storage - so belt and braces.

    But you're right, there's definitely too much cloud.....🤪

    Thanks for the feedback Geof. I might try video derotation  just to compare . It must be 10 years since I tried derotation on a transit.

    I can see why you use the cloud. At least they come in useful for something 😉

    • Like 1
×
×
  • 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.