Jump to content

Canada's top-tier Telescopes & Accessories


  • Content Count

  • Joined

  • Days Won


Posts posted by astroman133

  1. BYE 2.0.7 is very old.  The upgrade to 3.0 Classic is free.


    I believe that the timestamp in the file name is created from the time that the downloaded image is written to disk on your PC. It is not directly related to the time that the shutter was opened.




  2. BackyardEOS and BackyardNikon are camera capture programs that are built with lots of features that are particularly useful for astrophotography.  It supports a 3rd party interface where another application can request BYE/BYN to take a snapshot, save it to disk, and pass the file path for the image back to the requesting app.  None of this is particularly useful for autoguiding, either solar or stellar.



  3. Your camera may support HD video recording with audio...My T5i does.  However since Canon has not made that functionality available to PC applications, by providing the needed control methods in the EOS SDK, BYE is not able to control that process.  For that matter, no 3rd party application that relies on SDK can provide that functionality.

  4. It is definitely the latter.


    I believe that the SDK client app (in this case, BYE) tells the SDK that it wants to be notified when a new LiveView frame is available.  The app will receive that notification and respond; usually by downloading the frame and displaying and/or saving it to disk.


    How steady the actual frame rate is will depend on how busy the computer/USB hub are over time.

  5. Yes, you can move the zoom box while in Frame & Focus mode to display the FWHM, or other metrics, of LiveView frames or snapped images.


    With the Premium version of BYE you can drag and drop images in the image area of the Imaging screen, but the imaging screen does not provide any analysis capabilities other than visual analysis.


    BYE is a camera capture program.  This is why it does not do very much without a connected camera.  In its current form it is not intended to be used as an analysis tool, except as needed to support the image capture process.  This is by design.


    That is not to say that future versions of BYE, BYN, and BYCCD may not include some analysis features.

  6. Jerry,


    The index files are in C:\cygwin\usr\share\astrometry\data.  Astrometry.net will use whatever files are in that folder.  I downloaded all the index files, but for my setup I really only need 1 file.  What I do is to drag and drop the unneeded files to another folder.  I created a folder called C:\cygwin\usr\share\astrometry\backup_data.  This is where the unneeded files are moved to.


    Because both folders are on the C: drive a drag and drop operation will move the files, instead of copy them.  This is a good thing because the move operation is very quick.


    Other things that I do are to set the Scale Minimum parameter to about 10% of my field of view and the Scale Maximum to about twice my field of view, so with a field width of 1.5 degrees I set Scale Minimum to 0.2 degrees and Scale Maximum to 2.5 degrees.  Then if I will be connected to my scope when I start a Capture and Solve, I set the Search Radius to 10.  That means that I expect the solution to be within 10 degrees of where the scope is pointing. If it is a blind solve with no scope connected, I set the Search radius to 179.  I leave the sigma value set at 100.


    I hope that helps.

  7. BYE is a camera capture program that is written on a part-time basis by a pair of very talented programmers. As such, there are more opportunities for enhancing the functionality and feature set of the software then they can reasonably implement and support. Just my opinion!  They must pick and very carefully choose what features to incorporate and prioritize the implementation to provide the most valuable features first. 


    Currently BYE does not do any processing of captured images, similar to Nebulosity, except for the optional conversion of RAW files to TIFF.  Therefore it only saves images as CR2, JPG, or TIFF.  FITS is not a supported format in the current releases.


    How would your workflow benefit from having BYE save your images as FITS files?


    You are not the first person to ask for this, but IMO nobody has made a good case for it.  Any program that can stack DSLR images will do that conversion already so what is the advantage for BYE to also create FITS files?  A strong answer here and support from the community may increase the importance for providing this capability in BYE/BYN. (I am not speaking for the developers, only saying that if you can make them see the value of this capability they may decide to move this capability higher on their "to do" list).

  8. I read a previous post and realized that I did not say what I intended to say.  Here is the corrected paragragh:


    Another thing that I have noticed with RC03 is that shortening the exposure time causes the displayed image to become more washed out (approaching white) and lengthening the exposure and lowering the F/stop value causes the image to darken and the histogram peaks to shift to the left.


    Sorry for any confusion.

  9. Jerry,


    In order to confirm that your issue is being caused by RC03, or not.  I would suggest re-creating the issue with RC03 and then immediately shutting down RC03 and trying 3.0.3 to see if it suffers the same slowness.


    I do not believe that there are any settings for for directly controlling the LiveView frame rate.  It is limited by the camera, the USB connection, and BYE's processing.  Testing with both versions will rule out the camera and USB, if the problem does not occur with the older version.

  10. OK, so this is a similar, but unsolved, problem with the Histogram Center not being correctly rendered was previously reported by a single user. The L and 2 buttons are still to the left of the RGB button, but they are being positioned underneath the histogram graph. You can just see the top of the buttons above the right-hand end of the top of the graph.  Guylain was previously unable to figure out why they are being drawn too far to the left for that single, now 2 users.


    dot net ( AKA .Net Framework) is the Microsoft programming framework that BYE uses.  dts350z was suggesting that perhaps updating the .Net Framework would fix your issue.  If your PC is new (Windows 7 or 8) and you let Windows Update apply Microsoft patches automatically, then this should not be necessary, and perhaps not even possible, since the version of the framework that BYE uses is part of Windows.


    You said that you uninstalled and re-installed BYE.  Did you, by chance, choose a new and different, or completely empty, directory for the re-install?  If not, that may be worthwhile to try.


    A workaround for Guylain may be to change the Z-order of those buttons to force them to be drawn on top of the graph.

  11. Dennis,


    Based on my interpretation of your description, what you are experiencing may be due to "pilot error".  The RGB button does not toggle between RGB and Luminance histograms.  It selects the RGB histogram.  So clicking on the RGB button will not cause any change, if the RGB histogram is already displayed.  This behavior has not changed.


    This is what my Histogram Center looks like after taking an image. Notice that the RGB button is displayed with a light gray background and 2 and L are displayed with a dark gray background.



    Here is what it looks like when I click on the L (for Luminance) button. Notice that the L button now has the light gray background.



    This is working as described in the User Manual that installed with BYE v3.1 RC03.


    Please let us know whether this addresses the reported issue.



  12. I just tried RC03 and have the same issue with the color balance being off when displaying CR2 images. The displayed histogram has the 3 colors widely separated with red being well to the right and blue being well to the left.  This gives the image a violet cast.


    The copy that was stored in the camera displays correctly on the LCD display.


    My guess is that the in-camera color balance is not being applied correctly to the raw image when it is converted for rendering.

  13. Dennis,


    If you are saying that you, too, have a problem with the Histogram Center on the Imaging screen, then it will be difficult to provide "resolution hints". 


    This issue affects only a few users (you may be number 2) and Guylain has not been able to re-create it or provide a workaround to the one users who has reported it.  I do not believe that there has been a determination that the issue is based on the video resolution.


    I think that the best approach is if you provide as much information as you can about your installation and what you are seeing.  That may give Guylain additional information that will help him to troubleshoot what is going on and, perhaps, find a solution and/or workaround.

  14. Long-exposure noise reduction is a totally in-camera function.  The conventional wisdom is to turn it off and take separate dark frames.  That way you will maximize your time collection photons.


    I typically take dark frames indoors in a dark room or closet, with the body cap in place, at temperatures that approximate what I will be shooting at night.  That way I don't spend any time shooting dark frames while I can be imaging a target.  By taking darks at different shooting conditions (ISO, temperature, and duration) and combining them ahead of time, I am able to create a library of master darks and apply the the frame that most closely matches the light frames during image calibration.


    I would read your camera's manual to find out about how LENR works.  When I experimented with LENR it took a dark frame for every light frame.  So, every 1 minute exposure took 2 minutes because the dark frame had the same duration as its associated light frame.


    I have read that some of the higher end Canon cameras behave differently, but have no experience there. 


    I always leave LENR turned off.

  15. I believe that the trial version is a fully functional license, with an expiration date.


    BYE uses the Canon EOS SDK version 2.14.  According to Canon this version supports the T5 (1200D) however I do not see the T5 as a supported camera either in the V3.0 user manual or on the BYE web site.  It works with my T5i just fine.


    When you connect the camera to you PC and power it on, does Windows react and recognize the camera? Does the Canon EOS Utility program work with the camera?  If so, then BYE should work with it.

  • Create New...

Important Information

This site uses cookies to offer your a better browsing experience. You can adjust your cookie settings. By closing this banner, scrolling this page, clicking a link or continuing to browse otherwise, you agree to the use of cookies, our Privacy Policy, and our Terms of Use