astroman133 reacted to admin in LENR Canon Ra
Alan Dyer, although well respected, is wrong. You do not want to waste precious dark time taking darks.
Take as much light frames as your can during the night and use/build a dark library that you can re-use time and time again some other time.... a cloudy night is the perfect time to take dark frames.
astroman133 got a reaction from Aplajoie in Trial version update
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..
astroman133 got a reaction from admin in How-to activate your BackyardEOS or BackyardNIKON purchase or trial key
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.
astroman133 reacted to magicmotorworks in Canon EOS Ra won't take bulb photo
Tested 3.2.0.RC5 that you posted on my EOS Ra and could use the bulb mode as intended so the fix works.
One thing that I did notice was the following
Using Bulb mode on Canon Ra and BYE
If using bulb mode on BYE, the Canon EOS Ra needs to have the bulb timer option in the camera menu set to disable so that the BYE program sets and controls the bulb time.
If the EOS Ra bulb timer is enabled on the camera then whatever bulb time is set in the camera will be what is taken regardless what the setting is in BYE.
Canon EOS Ra settings: Bulb timer is disabled
BYE settings under Capture Plan Center (Shutter): Bulb (Duration): 60
Outcome: Ra takes a 60s image using bulb mode
Canon EOS Ra settings: Bulb timer is enabled Expo. Time: 00:01:00
BYE settings under Capture Plan Center (Shutter): Bulb (Duration): 120
Outcome: Ra takes a 60s image using bulb mode instead of taking a 120s exposure as in BYE plan. BYE thinks it took a 120s exposure when it didn't
Canon EOS Ra settings: Bulb timer is enabled Expo. Time: 00:04:00
BYE settings under Capture Plan Center (Shutter): Bulb (Duration): 120
Outcome: Ra takes a 240s image using bulb mode instead of taking a 120s exposure as in BYE plan
For BYE to use the bulb mode correctly in the capture plan make sure the EOS Ra in camera bulb timer is disabled.
Thanks for your quick attention to this.
astroman133 got a reaction from tzaranek in Planetary Live View
When in LiveView, the camera uses both ISO and shutter as brightness controls. They do not affect the frame rate, just the brightness. You can play around with these controls to see what I mean with a lens on the camera and not even connected to BYE. Set the ISO to 200 and the shutter to 2" (2 seconds). Then use the shutter speed wheel on the camera to shorten the exposure while watching the LiveView display. As you get shorter the display should darken.
You will see the same behavior when you are connected to BYE on the Frame & Focus or Planetary capture screens, if you uncheck Maximum Sensitivity in the Settings.
When you are using BYE to focus on a bright star, you want to set "Maximum Sensitivity" on the settings, or set the ISO to maximum, say 12800, and the shutter to 2" (not BULB). That is just about the maximum brightness that you can do. Then when you slew to Jupiter, you want to uncheck Maximum Sensitivity, set the ISO down to a reasonable value, say 200 or 400, and start lowering the shutter until the planet darkens and you can see the equatorial bands.
I hope this helps.
astroman133 got a reaction from admin in i upgraded to 3.1 but mark IV connects and then shows error
Please read the orange banner at the top of this page and provide the requested information.
There are multiple Mark IV models and multiple versions of BYE 3.1.
It would also help to have the exact error message. Either type it in or provide a screenshot.
astroman133 got a reaction from YOURJONES in FRAME RATE and SHUTTER SETTING
BYN does not use the camera's movie mode, so the camera's movie frame rate is not applicable to BYN.
BYN's frame rate is the rate at which it downloads LiveView images. This has to do with the speed of the USB connection and your PC. The ISO and Shutter settings do not affect the frame rate only the brightness of the frames. This is how the camera is designed to work and BYN cannot change that.
astroman133 got a reaction from admin in Backyard Nikon using VMware fusion on MAC
The bottom line is that there are nearly 10 times as many Windows systems as there are macOS systems and if anyone is going to commit to an effort of several thousand hours to develop an essentially new application for macOS, there has to be some realistic expectation of reward for the effort. Making the time to do this has also got to be behind any day job and family commitments. I understand why the authors have decided to let someone else write a DSLR camera capture app for macOS.
astroman133 got a reaction from g__day in Canon 40D - pictures not appearing in BYE 3.18 or downloading to PC
What is the Save To setting in the capture plan area?
Is your Anti-Virus software preventing the image from being stored?
Make sure advanced shooting features like exposure bracketing, LENR are disabled.
astroman133 got a reaction from admin in How to set video resolution in planetary mode?
I was imaging at a shorter focal length but was able to use the BYE Planetary mode at 5X to capture frames of part of the lunar disk. Then by moving the zoom box and repeating the capture I was able to collect 6 videos that between them covered the entire visible part of the disk. I reduced each video into a single image with RegiStax and then combined the 6 images into a single image with a program called RegiStar. This was back in 2012 when I first started using BYE with my XSi. The result came out quite good. Now if I could only find it.
astroman133 got a reaction from gperuzzo in Histogram in BackyardEOS
This has been discussed a few times, but not recently.
The histogram that BYE displays is created from the JPG image that is embedded in the RAW image. I would suggest that it is not suitable for determining your flat frame exposures, because the embedded JPG has been auto-stretched and color balanced in the camera.
I would suggest getting a starting point for the exposure of your flats by putting the camera in AV mode and selecting AV as the shutter in BYE. When you take an image, the cameras exposure circuitry will determine an exposure. You can then switch the camera back to Manual adjust the exposure as necessary to get a flat frame that you are happy with. Just be sure that PI does not base the histo on a stretched image.
astroman133 got a reaction from admin in Planetary Imaging Shutter Speed setting not working
BYE also has a "Maximum Sensitivity" setting that you need to disable in order to use exposure simulation. Also, if you shorten the exposure down to 1/1000 sec and the image still is over exposed then exposure simulation is not enabled.
astroman133 got a reaction from ozawashkoemaengun in Critical Error BackyardEOS version 3.1.8
This error has been reported before. It is due to a problem during the installation of 3.1.18. This has been fixed by either installing 3.1.18 to a different folder, or downloading the 3.2.0 RC from the Pre-releases section of the Downloads page.
astroman133 got a reaction from mpoelzl in Enhance Exif Data values and display
Here are some suggestions related to improving the usefulness of the EXIF data that BYE/BYN adds to images, and to make the display of that data more useful.
1) An EXIF value named "BackyardCaptureDate" is saved. It is not clear from the name whether this is based on the capture start time, the capture end time, the image download time, or the file creation time. My suggestions are to change the name of the parameter to indicate the point in the capture process that it represents. Something like "BackyardCaptureStart" removes the ambiguity. I would also suggest increasing the resolution to include milliseconds. It should be consistent with the Timestamp field in the file name. I should note that this would be a breaking change for any user or application that is extracting and using BackyardCaptureDate, so you may want to get consensus from the community or simply add BackyardCaptureStart as a new EXIF value.
2) Add additional EXIF values, with similarly unambiguous names to represent the capture end time, image download time, and file creation time.
3) Improve the Exif Data dialog window to either 1) allow the window to be re-sizeable and/or 2) present the user with a horizontal scrollbar. It should be easy to do both by making the horizontal scrollbar visibility be Automatic so it is displayed only if needed. The initial size could also be specified as the window's minimum size so the user could make the window larger, but not smaller, than the initial presentation.
astroman133 got a reaction from shbarr2001 in Losing tracking when slewing with BYE
First a clarification of terminology. BYE does not slew a telescope. It nudges or jogs the scope. Slewing moves the scope to a specific target. BYE's operation nudges the scope at a selected rate for as long as one of the nudge buttons is depressed. It does not have a specific target in mind. This is important because according to the ASCOM driver design documentation the driver is supposed to return to the previous tracking mode when the nudge operation ends. Apparently this is not happening. This is a problem with the CPWI ASCOM telescope driver, not with BYE.
Your exact symptoms were reported by another user a couple of weeks ago. That user stopped replying to the thread that he created, so we don't know if or how he fixed his issue. Here is his thread -->
So you have two options. You could contact Celestron about the behavior or you could switch to the Unified Celestron driver, which is not written or supported by Celestron.
First option --- On the ASCOM web site at ascom-standards.org you can download the driver conformance testing tool, called Conform. If you run this program and connect to your scope using the CPWI driver, the generated report will highlight any issues with the driver. If the driver fails any tests, especially the MoveAxis tests, you should provide the report to Celestron who can forward it to the CPWI driver authors. Any driver author should test their driver with Conform before releasing it!
Second option --- Also, on the ASCOM web site you can download the Unified Celestron telescope driver. This driver can be installed side-by-side with the CPWI driver as long as you only use one driver at a time to talk to your scope. This driver behaves correctly with regard to restoring the tracking state after MoveAxis calls.
astroman133 got a reaction from admin in 3.1.18 Hanging on download when minimized
Interesting...My initial reply to David's post, back on March 7th, indicated a saturated USB hub as a possible cause for a momentary disconnect which could cause BYE to hang. This is also borne out by the fact that the issue occurs when a completed image is being downloaded from the camera to the PC when BYE locks up.
Another thing to try, for testing purposes, is to save the image only to the camera's memory card. Then operate the camera both with BYE restored and minimized.
This is most likely an issue on your Computer since no other users are reporting anything remotely (no pun intended) like it.
One other thing is that Windows 10 has a USB Selective Suspend setting that could be causing your issue, even if you think that you have disabled the power saving features. Following is a link with instructions on how to disable it:
astroman133 got a reaction from sreegururaj in Unable to focus
BYE includes both a current version of the SDK and the 2.10 version and allows you to choose which one to use, both versions of the SDK work with the 1000D. However, you should choose the latest (Canon) as the older SDK is really only for models that are no longer supported.
Also, in the future if you are asking a question or have an issue that is related to BYE, you should post to the BYE Forum...Thanks!