Jump to content

Canada's top-tier Telescopes & Accessories


  • Content Count

  • Joined

  • Days Won


Posts posted by admin

  1. Guylain:


    Would it be possible to change the camera display on BYN to be consistent with Nikon language?  For example: You're still calling out Tv and Av for shutter and aperture, this is Canon Speak.  Nikon uses "S" for shutter and "A" for aperture.  Ultimately, this may be confusing some Nikon users who aren't hip to Canon Speak. 


    Hope this was useful.  




    Yes, I will get to that later, it's on the to do list before production release.



  2. Guylain:


    Great interface!  Everything seems to be working has promised.  However, the battery level display doesn't seem to be showing up on the "Camera Information Center".  Do I need to configure something in settings?  Other than that, I think you have a solid piece of software that should warm the hearts of Nikon users.  I'm testing with a Nikon D5100, Win 7 x64 OS.   Great work.




    I could not get the battery level using the Nikon SDK easily.  I'll try to add this in a later release.



  3. Hi,


    Just a little question; when I hibernate the PC, I noticed that the BacyardRED slider is moving each time to the right of the screen (if you shutdown, you won't have this problem).


    Is there a way to move back the slider to the left/center of the screen (I tried combo like Ctrl+Maj but nothing work for me).






    Hi François,


    Unfortunately there is no way right now <_>





  4. Since Guylain makes heavy use of Visual Studio, it'd take a lot of heavy rewriting to support a Mac OSX version.  And it would expose him to being one of the first to plow through and debug the OSX Version of the Canon ESDK.


    All of that effort, and it would still leave Mac-based AP Imagers in the conundrum that so many other of their AP Imaging Needs can only be satisfied in Windows-based Software.


    Myself, being selfish, would first hope that Guylain can find the time to continue on his current course and finish development of BYN, secure the internal Image Handling Library Changes occurring in v3.1 for both BYE and BYN, and make progress on the commitments of an Auto-Focus System (plus whatever additional Features and Tweaks).  That would seem quite enough of a Workload for the little Binary Rivers shop.  


    But, Guylain might have bigger plans...


    A good summary :)


    As I have said before I may try to compile it against the mono framework in the future but this is not for tomorrow.  My current plans are to release BYE 3.1, BYN 1.0, then complete the auto-focus.  Those plans will carry my into 2015 as-is.


    Thank you,



  5. I just download the Beta BYN and must say it rocks over Images Plus.  However, there's that annoying issue with the Inferred senor that I really hate (I'm about ready to pick up a 2nd hand Canon!). Everything seems to be working except the Bulb function which I need if I'm going to test this bad boy in the field.  Does  BYN support Shoestring Astronomy's DSUB-IR1 set up?  That's the one thing I really dislike about my Nikon D5100. 


    It supports the DSUSB from Shoestring (not the DSUB-IR1).


    It also support this cable, made by a BackyardNIKON user.  I have no affiliation with Steve.


    Hope this help,

  6. I've been asked this question frequently lately so I decided create a simple how-to.

    Follow these steps to
    zoom in/out images in BackyardEOS/BackyardNIKON.

    If you have a mouse with a center wheel...

    1. Place the mouse over the image, the zoom will be centered where the mouse cursor is (just like Google Map)
    2. Use your wheel mouse to zoom in/out.


    If you do not have a wheel on your mouse...


    1. Using the mouse (or mouse pad) on your laptop, place the cursor over the image, the zoom will be centered where the cursor is (just like Google Map)
    2. Use your keyboard page up/down button to zoom in/out. 


    You can go as high as 1000% and beyond.

    This zoom method is available in all modes, including Frame & Focus when live view is enabled.

    Hope this helps,


    When you are taking 5x zoom images you are ensuring a 1:1 pixel resolution; meaning 1 pixel on the sensor = 1 pixel on the image.  This is the best image quality you can get because no image transformation occurs, no resize.


    Hope this helps,




    Guylain:  Can you also please let us know what the pixel resolution ratio is for Standard and 10X?


    I have noticed that in recent images of Saturn, 10X is a lot "softer" than 5X and Standard is just too small an image to deal with.


    10x is a 2x digital zoom against the 5x zoom... so 10x will be 1 pixel on the sensor = 4 pixels on the image... it is enlarged by a factor of 2 in both width and height.



  8. Thanks, Guylain, for the quick response.  I know about the 1:1 pixel thing.  I've been getting 1:1 in camera (60Da) by using the 640x480 pixel movie crop mode.  BYE gives me no improvement in resolution.


    However, there is an exposure limitation when using the movie crop mode:  there is a fixed frame rate of 60 f.p.s. which means the longest exposure I can use is 1/60 second.   By using BYE I was hoping to get longer exposures, as long as 2.5 seconds, in order to get fainter double stars within my reach.


     But you say that these longer exposures are 'simulated' and that the simulation is related to the ISO setting..  Considering that I am shooting almost always @ 6400 ISO are the exposure lengths longer than 1/60 sec offered by BYE all 'simulated'?  




    Dave in Toronto


    All live view exposures -ARE- simulated, not just the longer ones. 


    This is a camera limitation/implementation, it is not a software limitation.  I have to take whatever the camera gives me.  There comes a point where the exposure simulation can't go further and when this happens you see no difference even if you change your values to a higher value/limit.


    Hope this helps,



  9. bonjour,


    Je teste les deux versions et hormis quelques changements dans le menu "advanced settings" (disparition de l'auto-connect par exemple), quelles sont les principales differences entre ces deux versions?





    Salut Francois,


    V3.1 est toujours en mode RC (release candidate).  La liste des changements n'est pas 100% compilé <_>





  10. bonjour,


    Je teste votre programme depuis qq jours et il est vraiment excellent!


    juste deux petites questions en planetaire:



    - quand on active le mode x5, est ce équivalent à avoir ajouter une barlow x5 ? en d'autres termes, "x5" n'est pas un zoom numérique, mais plutot "un crop du capteur de l'EOS d'environ 1056x704 dont on choisit l'endroit avec le rectangle"?


    - qd on fait un AVI, la taille de chaque image est d'environ 2Mo, mais quand on choisit de conserver les .jpeg dans le dossier "TEMP" chaque image ne fait plus que 200ko; pourquoi? et quelle est la veritable taille de chaque image 1056x704?





    Salut François,


    1) Non, c'est l'équivalent du zoom 5x de ton APN.


    2) AVI c'est une vielle technologie <_ mais elle fonctionne src="%7B___base_url___%7D/uploads/emoticons/default_smile.png" alt=":)"> malgré sa taille.









  11. I took my first 5x planetary mode videos with BYE this evening.  I shot Polaris at the following shutter speeds, all at ISO 3200 and 200 frames:  1/50 sec, 1/10 sec., 1 sec, and 2.5 sec as tests.


    Although the 1/50 and 1/10 videos look different from one another, the 1 sec and 2.5 sec vids look exactly like the 1/10 vid in terms of exposure.  They don't seem to go any deeper.  


      If I'm shooting 200 2.5 second frames shouldn't it take 500 seconds to do so? i.e. isn't the frame rate tied to the exposure length?  Well it seems not.  The vids are all just a few seconds long....  The 2.5 second frames are most certainly not 2.5 seconds long....


    So, when I adjust the exposure in 5x video mode what am I really adjusting?  Is the frame rate tied to shutter speed?  If not, why not?  etc. etc.






    Live view exposure length with Canon DSLR is not true exposure length, it is was Canon calls Exposure Simulation.  Depending on your ISO (and lens if any)  it is very possible that the exposure simulation has maxed out a 1 second and this is why you see difference beyond that.


    When you are taking 5x zoom images you are ensuring a 1:1 pixel resolution; meaning 1 pixel on the sensor = 1 pixel on the image.  This is the best image quality you can get because no image transformation occurs, no resize.


    Hope this helps,




  12. 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.


    Hi Rick, yes I'm getting the same here.  I seems like I forgot to add -W parameter in DCRaw to tell DCRaw to NOT automatically brighten the image... which it does by default <_>



  13. Rick, I can't duplicate the problem with either version, both now work like they are supposed to. So, I don't know why it behaved like that, I just couldn't slew onto any object without Liveview lagging way behind and in process was useless. I had to switch to DSLR LCD screen by disconnecting USB cable and than re-connect for shooting program.

    Beats me what happened, 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.


    You can -slow- down the live view frame rate in Settings by increasing the Live view Throttle parameter to 100 ms (default is 50ms) and see if that makes a difference.


    BUT, from what I can read in your description this seems simply like the classic -too-many-things-the UI-thread-has-to-perform and as a result some UI tasks (Windows or .net) simply took a bit longer to get to them.  Just a hunch.





  14. Premium.  Just initiated an uninstall; followed by a new re-install.  Nothing has changed and it is still the same issue.


    Well... This is the second confirmed case the control does not renders properly... Out of about 8000 copies in distribution. This is odd.


    Have you tried another computer just as a test?




  15. Guylain,


    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 shortening the exposure and lowering the F/stop value causes the image to darken and the histogram peaks to shift to the left.


    This is may also be related to some issue with DCRAW.


    Thanks Rick. I'm out camping with my wife this weekend... I'll check that later this week. Regards,

  16. Guylain, what is the best way to uninstall Candidate 01 and 02? Through Control Panel or just by deleting subdirectory?



    BackyardEOS 3.1.0 Release Candidate 03 is ready for download.


    Free upgrade from 3.0.x to 3.1.0 to everyone as usual.


    I still had some issues with image being downloaded in the TEMP folder but was not copied to your selected download folder.  The bug seems to be related to the new commercial library (GdPicture API) I purchased to load raw images <_ and it seems to be a the heart of several issues including performance issues. in this rc03 i no longer using gdpicture decided use dcraw load raw image data. have sent build users who repeatably reported with rc01 rc02. all bug fix so hopeful is now behind me fingers crossed.>


    Change log (from RC02)

    - JPG and RAW images now have the same time stamp as in V3.0.x.

    - Using DCRAW to load raw images for stability and performance.

    - Minor performance improvement

    - Testing on XP, Vista, W7, and W8


    This Release Candidate will NOT overwrite your current v3.0.x installation.



    PLEASE REPORT ISSUES using RC03 in this thread.


    Thank you,


    Both, first control panel.  This will uninstall it properly... but the config files are left behind so you need to delete the folder afterwards.



  17. 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.


    Right now my best guess is that DCRaw does not apply the WB properly, or at least it applies it differently.  I'll run a few test with reading the image in 16 bits instead of the default 8 bits and see if that renders the image more closely to what the in-camera rendering does.



  18. Not just one machine.  I just purchased BYEos and found luminance does not operate on mine etiher.  I'm using Windows 8.1 and Canon T3i.  I click RGB and it just sits here.  Any resolution hints would be helpful.


    The control does not render properly -or- the L / RGB does not work?





  • 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