Jump to content





  • Posts

  • Joined

  • Last visited

Everything posted by cgarry

  1. I have never used an automated sequence for this because I always need to tweak the focus for the blue channel at least. However, are you using FC to autoguide on the planet? If not, I would definitely get this working as it makes planetary imaging a much more relaxing experience. Well it does with my mount that likes to wonder about of its own accord. Cheers, Chris
  2. If you are planning a career in software engineering, or even a similar field, then having an open source project such as this under your belt actually makes you very employable. The code itself showcases your skills and the fact that you have done it shows that you have drive. Cheers, Chris
  3. In my experience you do not just write software and it is "done"! You either continuing maintaining it forever or it will be considered "no longer maintained" and it will die a natural death... Cheers, Chris
  4. Interesting. I wonder how it would work with the ISS...
  5. Were you sorting a lot of frames in quality order using PIPP? If your new machine has more memory (and a 64-bit OS) then PIPP will take advantage of this rather than writing frames to the hard drive during processing. Also PIPP will naturally run much faster with an SSD that an old HDD as planetary naturally processing involves a lot of hard drive activity. I believe that Registax is only a 32-bit program so will probably not be able to take advantage of any extra memory. However, I would have expected to be a bit faster on the new machine. Cheers, Chris
  6. That is a great idea, I shall do the same for SER Player. This should help Vincent who has the misfortune of maintaining both oacapture and SER Player on Arch Linux! Chris
  7. Good news, oacapture v1.4.0 is now working correctly in Arch Linux. Cheers, Chris
  8. That is working for me, thanks. I have added a comment to oacapture's AUR package page: https://aur.archlinux.org/packages/oacapture/ Hopefully, this should be enough to alert the maintainer of the files you created. Cheers, Chris
  9. The way forward: $ git clone https://aur.archlinux.org/oacapture.git$ cd oacapture Update PKGBUILD to get and build the latest version of oacapture.$ makepkg -si When you have a working PKGBUILD file, send it to your maintainer. Chris
  10. It looks like they have fixed their problems now, the installer is working again for me. Chris
  11. Yes, it does look like they are having problems. I just tried to install Antergos in a new VM using the ISO that worked fine yesterday morning and I got the same error message as you. I assume they will get it fixed shortly. Chris
  12. When you have Antergos installed, the following at the command line will show the problem: $ git clone https://aur.archlinux.org/oacapture.git $ cd oacapture $ makepkg -si The file 'PKGBUILD' contains all that is required to build the application. Cheers, Chris
  13. I am using Antergos rather than plain Arch, far simpler to install. If you can get it to build on Arch then producing a package is pretty simple as all it does is download the source code and build it. Chris
  14. Hi James, Good work! Is there any chance of getting the Arch Linux AUR updated to the latest version? It currently looks to be stuck at a broken version of v1.0.0. Cheers, Chris
  15. Also, on Windows SER Player integrates with the file explorer so that SER file thumbnails show the first frame of the SER file instead of an icon.
  16. This is just a quick heads up for the release of SER Player v1.7.2. https://sites.google.com/site/astropipp/ser-player Details of the changes since the last release (v1.6.0) are on the download page. Cheers, Chris
  17. There will be no loss of quality when converting from CR2 to SER with PIPP. Both formats are lossless and SER can hold 16-bit data. Cheers, Chris
  18. SER Player will do this and much more: https://sites.google.com/site/astropipp/ser-player Cheers, Chris
  19. Calibration frames are not normally used for planetary imaging, I certainly never use them. Because of the small size of the sensor in planetary cameras vignetting is not normally an issue so flat frames have little benefit. Plus due to the short exposure time dark frames are of little use. Basically do bother with calibration frames for planetary imaging would be my advice. However, flat frames can remove dust spots from a capture so it is best to never say never. I am not sure whether Autostakkert! accepts calibration files directly, but PIPP will accept them if not. For calibration frames, a short capture in the same format as your image capture would be the way to go. I would also advise capturing all you data in SER format, but AVI will also work is you insist on using an ancient, over-complicated format. Cheers, Chris
  20. Also, to play a SER file in the way you would an AVI: https://sites.google.com/site/astropipp/ser-player Cheers, Chris
  21. Hi Kirk, No, this is very much a bug! Cheers, Chris
  22. Ah, I have just checked the source code and the problem is it was checking for the sample value being equal to 65535 in 8-bit mode. before deciding it was overexposed This was never going to work well with values that max out at 255! This algorithm is somewhat simplistic and does not handle the case where values max out below 255, but that is a problem for another day. I will do a quick fix for now and it would be good to see if it works with your data. Cheers, Chris
  23. Can you please look at the file in SER Player and use the histogram viewer to see if the blown out frames actually any have pixel values of 255? Also if you could save a few (2 or 3) of the blown frames in another SER file (SER Player can do this) I would be interested in examining them and with a view to fixing PIPP. Cheers, Chris
  24. I thought that relativity says that the order of cause and effect is always preserved, no matter what your frame of reference is. The exception is if you are travelling faster than the speed of light when the order of cause and effect is not preserved, but then you are into time travel anyway... This is most definitely not my specialist subject though, so I too am interested in what other have to say.
  25. Hi, What format did you capture your data in? Is it raw colour (monochrome with a bayer pattern) or colour video? What options are you selecting in PIPP? For raw colour video you either need to debayer the video in PIPP or protect the bayer pattern while cropping or centring the frames. See these controls: * Input Options Tab -> Colour Debayer Cheers, Chris
  • 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.