Jump to content

Canada's top-tier Telescopes & Accessories

admin

Administrators
  • Content Count

    7,267
  • Joined

  • Days Won

    67

Posts posted by admin


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

     

    Regards,


  2. 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?

     

    Regards,

     

     


  3. Driving the camera lens to focus with BackyardNIKON is not yet implemented (like it is in BackyardEOS).  This will probably not be in version 1 of BackyardNIKON, but rather in a subsequent version.  Time is the issue... not enough hours in 1 day <_>

     

    Regards,


  4. Noise Reduction: I've noticed that Long Exposure Noise Reduction may take as long as the exposure at the start of a set of exposures but at the end of the set there may be little or no delay between the end of the exposure and the time the image appears on my computer screen.  Is BYEos cacheing dark frames from the start of the run to use on the end exposures?

     

    Focusing: I've been using a Bahtinov mask to focus as well as the numerical display on the Frame and Focus screen.  Since the live view display of the Bahtinov can be marginal at times, I'm wondering if I'd do just as well without it.

     

    BackyardEOS does -NOT- cache images.  What you see is what the camera delivers for each individual frame.

     

    I find the Bahtinov feature to work best with still pictures of a second or two instead of relying on live view alone.

     

    Hope this helps,

     

     


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

     

    The 1200D is not supported in 3.0.3.  You need to use the 3.1 RC03... follow the link below.

     

    http://forum.otelescope.com/post/backyardeos-3-1-0-release-candidate-03-is-ready-for-download-7017967

     

    Thank you,

     

     


  6. Also it occurs to me that trying to mach the in camera jpeg histogram may not be what we want anyway? I think that was an issue brought up before?

     

    If so, maybe an option to preview with raw vs. jpeg? 

     

    Sure, we still need to understand the DCRAW histogram and make sure it's correct, but it might be a good idea to fix the any/all preview vs. image capture differences at the same time.

     

    DCRAW is very very fast, at least on my laptop, so I wouldn't see any downside to preview via raw.

     

    You can already preview images in RAW.  Just go to settings and select "in-camera" for image quality.  BYE will use your current camera setting, just make sure it is RAW.

     

    Regards,


  7. OK, I'm taking dark flats.

     

    I put the lens cap on, and do a preview and get a dark pic with the histogram hard left, as expected.

     

    http://glenn.ws/web/images/PREVIEW_20140731-20h40m25s064ms.JPG

     

    Now I start capture, but instead of pics like the above I get noisy pics with big fat histograms:

     

    http://glenn.ws/web/images/LEDFLATS_DARK_FLAT_Tv1-13s_1600iso_+68f_02203stdev_20140731-20h40m05s673ms.CR2

     

    I checked the EXIF data and both ARE at the same exposure, so what's up? Is the DC RAW lib "boosting" the values to display in 8 bits or something?

     

    Seems like it would be difficult to use  previews and histograms to judge exposures under these conditions.

     

    I thought I noticed something funny the other night (with RC3). Previewing at 12800 iso to get the exposure and then multiplying that shutter time * 8 to image at 1600 ISO was way over exposed, as judged by the raw histogram.

     

    I guess I can do a capture plan of 1 instead of a preview but I don't think this is the desired behavior.

     

     

     

     

     

     

     

    Your cr2 link is broken so I can't download it <_>

     

    A preview is a JPG image as-is from the camera.  In this respect the camera firmware is processing the image, including white balance.

     

    A capture plan image in RC03 is loaded using DCRAW with the following parameters...

     

    -c        Write image data to standard output

    -w        Use camera white balance, if possible

    -h        Half-size color image (twice as fast as "-q 0")

    -T        Write TIFF instead of PPM

     

    In this RC03 I chose to use the -h parameter so speed things up (this is not high quality but it is important to note that RAW data remains unchanged and is of high quality, only the image display on screen is of less quality), I suspect the -h parameter may be the cause.  However, I have taken over 1000 images with 3 different cameras before releasing and I did not see the behavior your are seeing.

     

    I'll run some tests with and without the -h parameter and try the -q 4 parameters for highest quality.

     

    I'll also try the -6 parameter for loading 16 bits instead of 8 bits.

     

    DCRAW is a proven alternative, looks like it will take a round or two to nail down the perfect combination of parameters for both performance and quality.

     

    Thanks for posting,

     

     

     

     

     

     

     


  8. In RC01 while BYEOS was still taking images I was reviewing some of the images already taken to look at their quality.  I selected an image by clicking on the thumbnail image below the main image.  I then expanded the image to 100% to look for star trails.  When I clicked the button to again Fit the image to the screen the image was displayed rotated 90 degrees, i.e., horizontal was now up and down, and, up and down was now horizontal.  The image was reduced in size so that the entire original horizontal FOV now fit in the vertical direction.  I was not able to get the image to display "un-rotated" in the Fit to Screen mode.

     

    Steve

     

    Can you post a screen shoot?

     

    Thank you

     

     


  9. I don't know much about DCRAW or what is really does, (I leave that sort of stuff to you code guys)  but I do know that Pixinsight invokes it when calibrating/debayering Canon CR2 files for integration.  If there is an outside chance that it will make any sort of positive difference in my using both BYEOS and Pixinsight for my imaging software kit, then I'm all over this like white on rice. B)

     

    Is is completely irrelevant to what PixInsight does.  BYE uses DCRAW to load the image to display it, it does not alter the RAW image data in your .cr2 file in any way.

     

    Hope this helps,

     

     


  10. Thank you Guylain.  That would solve my situation.

     

    Just to make sure, what you said is that BYE can fire shutter signal to two cameras, one

    via USB and one via DSUSB, right?

     

    Cheers,

    Wei-Hao

     

    Not directly.  You need to hack/split your cable so it has 2 camera connection end, one for each camera.

     

    I have never seen someone do this with a DSUSB but I've seen a few users using a straight serial cable and spiting it to add a second camera connector/plug.

     

    Does make any sense?

     

    Hope this help,

     

     


  11. BackyardNIKON BETA 02d is ready for download.

     

    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 beta i no longer using gdpicture decided use dcraw load raw image data. have sent build users who repeatably reported with all bug fix so hopeful is now behind me fingers crossed.>

     

    Change log (from BETA 02c)

    - JPG and RAW images now have the same time stamp

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

    - Minor performance improvement

    - Testing on XP, Vista, W7, and W8

     

    This BETA 02d will NOT overwrite your current BETA 02c installation.

     

    http://www.binaryrivers.com/download/setup-BackyardNIKON-v100-BETA02d.exe

     

    PLEASE REPORT ISSUES using BETA 02d in this thread.

     

    Thank you,


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

    http://www.binaryrivers.com/download/setup-BackyardEOS-v310-RC03.exe

     

    PLEASE REPORT ISSUES using RC03 in this thread.

     

    Thank you,


  13. Hi:

     

    I just scored an old Canon 20D on Ebay, very cheap might add, that I intend to dedicate to astro-photography.  However, my laptop is running Windows 7 which didn't show up on your list of supported operating systems, I shed Windows XP years ago.  Will BYE work with a Canon 20D using Windows 7?

     

    Not if it is 64 bit... Canon has no drivers.

     

    If it's W7 32 bits you can install the 20D drivers for XP on W7 32 bits and it will work.


  14. Hi,

     

    Based on another earlier thread, it seems not possible to launch two BYE instances to control two cameras on the same mount to dither.  Now, my need is slightly simpler than this, and I would like to know whether this is possible.

     

    The situation is, I have two cameras (One Nikon D800, one Canon 5D2) on the same mount, and I would like to dither.  However, only one of the cameras needs BYE or BYN control.  Let's say I will use BYE to control the 5D2, to focus and frame, and to image and dither.  I don't need any other imaging/focusing function on D800.  All I need is a Bulb signal that is synchronized between the two cameras, so the dithering on 5D2 will not destroy the exposure on D800.  Is there any setup that can do this?  For example, if I use DSUSB between 5D2 and BYE for shutter control, can the same shutter signal somehow be wired to D800 too?

     

    Cheers,

    Wei-Hao

     

    Yes that would work. 

     

    EDIT: But you need to split your DSUSB so you get 1 camera connection and one computer usb connection.

     

    1) Start BYE as you normally would

    2) Go to Settings -> Advance Settings and enable "FORCE SERIAL CABLE"

    3) Select DSUSB in cable select (Capture Plan Center)

     

    4) Start BYN and connect your D800.  This is optional but it is practical if you want your NIKON images download to the computer :)

     

    5) Using your BYE instance (from step 1) start your capture plan.

     

    Both cameras should fire at the same time and you'll be able to dither using your BYE instance.

     

    Hope this help.

     

    Regards,

     

     

×
×
  • 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