Jump to content

Canada's top-tier Telescopes & Accessories


  • Content Count

  • Joined

  • Days Won


Posts posted by astroman133

  1. Please note that I am a long time user and not an admin, so my answer is not final, but it is in agreement with the License Agreement and what advice has been given in the past.

    It is possible to control to cameras from the same PC with  2 instances of BYE with only a single license, but if you are going to use BYE on 2 PC's at the same time then you need 2 licenses.


  2. Your anti-virus software may be preventing the image download process from completing. Try operating the camera with the A/V software temporarily disabled. If this fixes your issue, you should whitelist BYN (tell the A/V software that BYN is OK). You should also confirm that you have write access to your Download and BackyardTEMP folders and that they are on a local hard drive that is always available.

  3. Could you implement a built-in Save To Camera delay time and expose it as a Setting? Then allow the user to set a value that they have determined works for their camera(s). A dropdown list, slider, or up/down control with a range of numbers from 1 to 20 seconds with an increment of 1/4 second should work.

  4. Just tell us what version you are using. Or go to the Downloads page via the tab at the tope of this screen to see the latest.

    The problem with giving you a link to the "latest" is that after the next release, the link will be the same but the "latest" release will have changed. This is misleading to someone reading this thread two years from now.


  5. Your issue has nothing to do with downloading, installing, removing, or reinstalling BYE. You did not need to any of that. The software is the same for all licenses. It is the key itself that enables or disables features in the software.

    What you do need to do is to enter your purchased license key in place of the Trial license key in BYE's License Validation dialog..

  6. Dark frames are NOT "of the same scene" as light frames.. Dark frames are ideally taken with no ambient light reaching the sensor so where the camera is aimed is of no consequence. Only the sensor temperature, exposure, ISO, and that no ambient light reaches the sensor are of any importance.

    Based on my testing, BYE's behavior is NOT as you state when you say that "Backyard EOS only allow an image of a specified length and then immediately downloads".

    BYE only downloads an image when the camera says that the image is ready to be downloaded. I turned on LENR on my T5i from the in-camera menus and used BYE 3.2.0 - RC4 to shoot images of different lengths (10 seconds, 1 minute, and 5 minute). In each case BYE patiently waited while he T5i shot and applied the in-camera dark frame, and only then downloaded the resulting image. It may be that at some point BYE times out and says that no image was available, but it did not occur with a 5 minute exposure.

    I don't know what would happen if you tried to take a 20 minute Ha image with LENR turned on. You should download the free 30-day trial of BYE and try it yourself, at the kitchen table, during the day, with the lens cap on the camera.

    Personally, I would prefer to capture twice as many light frames rather than use LENR, but I have no data to support my conclusion. However, my testing shows that BYE is programmed that LENR may be used and is tolerant of that.

  7. Also, please tell us which version (like 2.1.10) of BYN you are using. It is also useful to know if you have a lens on the camera or not. 

    When you are imaging with a lens, you should put the lens in Manual Focus mode since it will not be able to focus on a dark sky and will not be able to take picture.

  8. If the lens is an autofocus lens, make sure it is set to manual focus before trying to shoot images. You may be able to use it in AF mode with LiveView to focus on a bright star or the moon, but tape it down and switch to MF to image.

  9. If you can drive your lens when the switch is in the manual focus position, then the lens is not typical. Usually the MF position disengages the motors so you can easily move the focus ring manually and so the camera will not be able to adjust the focus when you take a picture.

  10. Another issue is that with the short focal length, the stars will be so small that the focus metrics will likely not work.

    I have a manual focus 16 mm Rokinon lens that I have used to shoot widefield nighttime images. One of the reasons that I bought it was because it has an accurate infinity mark on the focus ring. I adjusted the focus on the infinity mark and taped the focus ring in place so that it could not accidentally shift. I was able to shoot 1300 20 second images of the Milky Way rising and setting over nearly an entire night. The camera was mounted on a vixen Polarie camera mount. The Polarie is usually polar-aligned, but I oriented it horizontally and let it pan across the southern horizon.

  11. James,

    Please post issues and questions about BYE in the BYE Forum. This makes it easier for someone who is experiencing a similar issue to see how others have solved it.

    BYE uses the Canon EOS SDK software library to control the camera. The SDK does not have access to all the camera's settings, so BYE cannot warn you that they may be set inappropriately.

    If it worked a few days ago, but not during your most recent session, it seems that it is likely due to one of those settings being set inappropriately for BYE's use. 

    Some cameras have a setting that prevents the camera from taking an exposure without a lens attached. Is it possible that your camera has this setting and that you changed it after your last imaging session? 

    The symptoms are the same as yours. Look at this post from last week in the BYE Forum:


  12. If Canon supports the camera via their Software Development Kit (SDK) then it is likely that BYE will also support it. The SDK does not support WiFi control, but some users have figured out a multi-step process to pair the camera with the PC wirelessly before starting BYE. You should look through the archives of the BYE forum for posts that detail how to do this.

    According to the M100 Manual it does have a USB port, to support wired control by a PC

    You also need to read the post below which explains why a camera model may not in the list of supported models.


  13. I should also say that the How-To Forum is not the place to ask questions. If the How-To information did not address your question or solve your issue, you should have posted to a new thread in the BYN Forum (or the BYE Forum for a Canon camera).  The vast majority of users do not have a problem validating their license, but if everyone who did replied to this post then it would be difficult for any reader of the thread to find help for their issue.


  14.  You are correct. Some users experienced issues with Windows 10 folder permissions that prevented BYN and BYE from accessing the AppData folder. As a result, the storage location of the license data was changed.

    Can you tell us what you mean by "keeps asking me to enter the license key and identifier continuously". Did you enter your trial license key and your username as the identifier into the license validation dialog? 


  15. The BYE focus metrics like FWHM and HFD really need a point source of light, like a star, to be able to measure its diameter.

    You can simulate a star by poking a small hole in a piece of poster board and putting a light source, like a desk lamp, behind it. Then move the camera across the room and use BYE with a lens try to get a good diameter for focusing.

    You may want to rethink using an alt-az mount for prime focus astrophotography. The motion of horizontally-oriented alt-az mount does not match the movement of the stars and is vulnerable to the effects of field rotation. Field rotation causes the stars at the highest and lowest declination to be elongated even while the stars across the center of the image may be pinpoints. In your images this causes an unappealing mixture of round and elongated stars. There are 4 solutions. 1) use a wedge to equatorially mount the telescope, 2) replace the mount with a German equatorial mount, 3) find a way to de-rotate the camera, or 4) keep your exposures very short. Each of these options have drawbacks. The wedge makes the telescope less stable and there may not be a wedge for your mount. Replacing a new alt-az mount with a GEM costs $$$ and may not be feasible. Low-end de-rotators are not very popular and may not provide a satisfactory solution, if you can even find one. Keeping the exposure duration short may prevent you from capturing the dim detail that is the hallmark of deep sky astrophotography and so your targets my be limited to brighter objects.

    Depending on what your goals are, you may want to consider returning the Alt-Az mount without even taking it out of the box. The supplier may be able to suggest a better alternative, if you share your intended use with them. Or you could decide to use it solely for visual work and buy a different mount that is suitable for astrophotography.

  16. Guylain has already said, above, that he is unable to personally test every new model of camera with BYE. He is largely relying on the Canon EOS SDK to hide the differences between models, so I'll turn it around. Since you are the owner of a T8i, have you had the opportunity to test the imaging capability of the T8i with BYE? Does it correctly create RAW, TIF, and JPG images from your camera? Is BYE able to set the camera's ISO and lens' aperture? Does it control the camera correctly to shoot Tv and Bulb exposures? Does BYE fully function with the T8i, except for LiveView?

    All of the suggested testing can be done indoors during the day with a lens attached to the camera.

  17. WinJUPOS is what is typically used to de-rotate and combine images of Jupiter and Saturn.

    The AVI file contains the JPG images which are downloaded from the camera. The AVI is not uncompressed because the JPGs are not uncompressed.

    I am not sure why you get such variation in the frame rate. AFAIK, lower frame rates are not better, or worse either. The rate may be lower because the PC is busy processing the first image. In any case you cannot control the frame rate. BYE gets the LiveView frames as quickly as it can.


  18. With a short focal length wide angle lens, the stars are soooo small that the focus metric may not be useful.

    I assume that you are trying to focus with LiveView. If that is not working, manually set the lens as close to infinity as you can get and try taking a couple second snap image. This may help you where LiveView is failing.


  19. The JPG images are the individual LiveView frames that BYE gets from the camera. The JPG files are combined, after the fact, to make AVI. This means that the quality is the same.

    Initially the downloaded JPG planetary images are saved in the BackyardTEMP folder. Once all the requested frames have been collected in the BackyardTEMP folder, a background thread is used to move them to the Planetary folder, rename them, and potentially combine them into the AVI. You need to let this process happen without intervention. By you worrying that BYE is not doing what it is supposed to and moving the files manually, you are interfering with that process. BYE will warn you if you try to quit the program while you have unprocessed data. You can tell that it is finished when the Queue entry (in the Camera Information Center, to the right of the battery indicator) disappears.

    I suggest that you play around with BYE and your tablet, connected to the camera, at the kitchen table, so you are familiar with how to use it and are comfortable with how it behaves.

    I have an i7 desktop PC with Windows 10 Pro and a T5i camera. I get about 14 fps in Planetary mode. I created two 3000 frame AVI files, back-to-back (by setting the Loop count to 2), using BYE 3.2.0 RC4. I had no problems. The frames for the first video were being processed while the data for the second video was being collected. BYE's memory usage did not come close to the 2GB limit, staying below 160MB and its CPU usage was always under 10%.  It took about 3.5 minutes to capture the 3000 frames and less than 2 minutes to create the AVI, so the number of queued tasks never got above 1.

    If you are trying to capture Jupiter, you need to keep your video short. I have heard that less than 70 seconds is good. If you go longer than that you will start to see blurring in the stacked image due to the rotation of the planet. Of course there is software that can de-rotate the images to let you go longer.

  • 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