Jump to content

Canada's top-tier Telescopes & Accessories
Be as specific as possible when reporting issues and *ALWAYS* include the full version number of the application you are using and your exact *CAMERA MODEL*
NEVER POST YOUR KEY IN ANY PUBLIC FORUM, INCLUDING THE O'TELESCOPE SUPPORT FORUM ::: IF YOU DO YOUR KEY WILL BE DEACTIVATED WITHOUT NOTICE!
  • 0

Considering a T5i


astroman133

Question

  • Answers 11
  • Created
  • Last Reply

11 answers to this question

Recommended Posts

Guylain,

 

Thanks for the information. 

 

I see from the data that Gary Honus presented that the 700D runs warmer than my old 1000D, or a 6D for that matter. However, my use for lunar, planetary, and wide-field imaging should not be bothered by that.  I am more concerned about what I can expect for the LiveView frame rate.

Link to comment
Share on other sites

BTW, wasn't it the T5i which had the "crippled" LiveView Frame Rate ??

 

If you want Good Frame Rate for Lunar and Planetary, you'd be better off to focus on the T2i with its "Crop Movie Mode True 1:1 Pixels 640x480 @ 60fps" or consider the T3i with its 3x Zoom FullHD Movie @ 30fps mode (which several technical reviews claim is rather a 1:1 Center Crop of about 2.5x @ 768x432 - but at 30fps).  With the latter you get a decent Frame Rate AND Articulating Screen AND slightly better Noise Control, whereas the former you get a great 60fps Frame Rate.  Both of these Movie Modes are "Raw Sensor Pixels" rather than data "pretreated" for LiveView (I've not heard that any LiveView image is more than an Interpolated/Resampled downscaling of the 18MP Sensor to the 1-1.2MP Rear LCD LiveView presentation).  

 

I know from previous inquiries that Guylain has found the Canon SDK doesn't address the T2i/60D Crop Movie Mode, so it is not offered any support in BYE.  I don't know but would guess the same lack of SDK support for the T3i 3x Zoom Movie Mode.

 

I've hopes that eventually Guylain will at least be able to Download the Resulting MOV (even if he cannot effect its Capture), and then apply the basic BYE File Name Template plus any Histogram.  I'd also like to see an equivalent to the Planetary Capture Plan, where BYE manipulates the appropriate Camera Settings (Exposure, ISO, Mode) and then presents a Countdown Timer for the User to press the Record Button for both Start and End of the Capture Plan Timings.

(Hint:  This last part is a Feature Suggestion.)

Link to comment
Share on other sites

I never did quite understand why BYE takes planetary videos as a series of JPEGs and then compiles them into an AVI.  Seems so much easier in my mind to just use the cameras already built-in video mode.  But I'm no programmer so I'm sure there are reasons beyond my understanding.  Only reason I can think of right now is that the camera takes MOVs and we need AVIs for stacking and processing.  But wouldn't a file conversion tool that can be done "offline" be useful here? 

Link to comment
Share on other sites

I never did quite understand why BYE takes planetary videos as a series of JPEGs and then compiles them into an AVI.  Seems so much easier in my mind to just use the cameras already built-in video mode.  But I'm no programmer so I'm sure there are reasons beyond my understanding.  Only reason I can think of right now is that the camera takes MOVs and we need AVIs for stacking and processing.  But wouldn't a file conversion tool that can be done "offline" be useful here? 

 

It is straight forward, all live view frames -are- jpeg coming out of the camera.  BYE takes whatever format the camera provides.   Live view = jpgs so that is what I use :)

 

Guylain

 

 

 

 

Link to comment
Share on other sites

This question has been Asked and Answered in more detail in other Posts.

 

There are 2 basic reasons:

 

1) Canon SDK doesn't expose most of the Video Functions - so BYE would be unable to control them.  The SDK does provide access to the LiveView stream, including the 5x Zoom 

 

2) DSLR Video is seriously Interpolated - diminishing the accuracy and value for Planetary Imaging purposes.  DSLR Video is a 16x9 format 1920x1080 or 1280x720 pixel reduction of the 12-18MP 5128x3456 pixel 3x2 format Sensor.  Since all DSLRs are designed for Daytime Photography (and secondarily Daytime Video) AND consumers want rather standard 24-50mm Portrait and 70-300mm Telephoto Lenses, DSLR Designers would be Shot if they implemented the 1920x1080 as simply a Center Crop as that would turn a 24mm Lens into a 65mm medium Telephoto (worse, a 105mm Telephoto on all the APS-C Canon Rebel DSLRs).  Instead, the full width Sensor Image is Interpolated/Resampled down to that FullHD 1920x1080 Video at diferent non-integer ratios in each horizontal and vertical dimension.  THAT is rather Undesirable for AP Imaging - both because the Planets will only ever cover a small-ish portion of the center of the frame AND because the Interpolation loses vast amounts of fine Planetary detail.

Link to comment
Share on other sites

Canon produces MOV format for whatever justifications / reasons they might have.  It just is...

 

Canon recognizes that AVI is a rather popular, but incompatible, format - so they provide a Conversion Tool in the Export Movie function of the ZoomBrowserEX App that they provide with every Canon DSLR.

 

 

Link to comment
Share on other sites

BTW, wasn't it the T5i which had the "crippled" LiveView Frame Rate ??

 

No, that is the T4i.

 

Guylain

 

Guylain,

 

Do you know if the later cameras than the T4i (650D) suffer with the same Live View frame rate limitation as I have been thinking of replacing my 650D with a 70D?

 

Jim

Link to comment
Share on other sites

BTW, wasn't it the T5i which had the "crippled" LiveView Frame Rate ??

 

No, that is the T4i.

 

Guylain

 

Guylain,

 

Do you know if the later cameras than the T4i (650D) suffer with the same Live View frame rate limitation as I have been thinking of replacing my 650D with a 70D?

 

Jim

 

No issues reported with these models.  It seems isolated to the T4i as far as I know.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.


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