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

Is Canon R50 compatible with Backyard EOS


ashonle

Question

Thank you so much. We were able to connect the camera with 3.5.

The files, as far as we can tell, aren't getting saved. The queue pops up very briefly and then disappears.

This was our log after a brief test. Any ideas?

20:21:43  Planetary imaging started.
20:21:49  Capturing 30.4 frames per second.
20:21:50  25 planetary frames captured.
20:21:51  Retrieving the COM class factory for component with CLSID {40D02BB3-80B5-4EAF-A264-61B9EF30BBE2} failed due to the following error: 80040154 Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)).

Link to comment
Share on other sites

8 answers to this question

Recommended Posts

  • 0

Try the 32 bits version. This issue you have is with the AVI encoder, and it looks like it may not work on your PC.

Alternatively, save your planetary video in individual JPEG instead of AVI. The quality is the same, and most stacking software will do just as good, if not better, given the size of the sum of all JPEG is smaller than the actual AVI.

Link to comment
Share on other sites

  • 0
Just now, astroman133 said:

From the GUID in the log fragment that you are reporting, it seems as though BytescoutImageToVideo.dll is not correctly registered. It is an in-process COM component and so with the 64-bit version of BYE, a 64-bit version of ByteScout must be installed and registered.

I thought I had added this in the installer post-install, I'll have to test it a bit more, perhaps I did not :(

Link to comment
Share on other sites

  • 0

We had luck on our test runs earlier today using the Canon R50 which were a small number of frames at a time, but when we increased the number, we started having issues with the process either not queueing at all, or attempting to queue and then stopping. Do you think this is due to the same AVI issue mentioned above? 

I did see the jpgs are in the TEMP folder.

My computer was capable of working well with BYE when we were using a Canon Rebel T1 (but the camera was a bit heavy for our telescope and I was hopeful about the lighter body of the R50), so maybe we have to go back to that or try on a different computer. 

The log reads a little differently now that we are in the BYE v3.5 32 bit version:

19:35:57  Planetary imaging started.
19:36:04  Capturing 25.9 frames per second.
19:37:26  1950 planetary frames captured.
19:37:27  A generic error occurred in GDI+.

 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

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