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

BYEOS isnt downloading the files after capturing


tulsatom

Question

was wondering if theres something I can do to get this taken care of. I keep getting a shutdown error and when things do go well my capture gets stuck in the downloading que. I have used this numerous times under the exact situation and conditions as far as cables go. plus I have tried every usb port even going as far as wiggling them slightly while plugged into which ever port and even when wiggling them cannot make camera disconnect etc. can anyone help me out plz my once in a lifetime trip to Yellowstone is in about 3 weeks and im hoping to get this resolved by then :)

 

its just taking forever to download the information into my selected folder could this imply the cable im using is garbage and is causing the disconnects and the long wait to download the information?

Link to comment
Share on other sites

  • Answers 29
  • Created
  • Last Reply

29 answers to this question

Recommended Posts

My Win 7 runs Avast (free version). Never had a problem with it interfering with anything and it's always running. To complicate things, Win 7 is running as a guest OS under Parallels on a 17" MacBook Pro which is also running Sophos - another A/V program.

 

When taking a series of images, downloading images to the computer is slow, and that means images are backing up in the pipeline while BYE is taking a series of images. That could be because the drive being accessed is attached to another computer on the LAN with access to the other computer by WiFi. Once I got PHD2 in the mix doing dithering, enough time elapses between images that each shot has completed the download before the next one is started. If anything interrupts the access to the download folder, it might hang BYE.

 

There are similar reports like this in other topics here. The one solution for one person was to get a new computer. If you are running an old XP, that could be the problem.

Link to comment
Share on other sites

I am also having trouble with planetary video downloads.  Last night I shot a number of vids of Mars and Saturn.  6 downloaded and compiled into AVIs with no problem (a little slow but they were large vids) now I have 11 vids that never compiled.  I can only find four of them in the download folder and they seem to all be jpegs.  I have left BYE running overnight in hopes that this was just some quirk that the machine would take care eventually, but I had to disconnect the camera when I picked up for the evening.  Therefore I can't see the queue anymore so I don't  know what's happening.

 

I love BYE and have for years, but I think this particular feature requires a little more thought.  I will return to 2.09 for planetary in the future until something is improved here.

Link to comment
Share on other sites

I am also having trouble with planetary video downloads.  Last night I shot a number of vids of Mars and Saturn.  6 downloaded and compiled into AVIs with no problem (a little slow but they were large vids) now I have 11 vids that never compiled.  I can only find four of them in the download folder and they seem to all be jpegs.  I have left BYE running overnight in hopes that this was just some quirk that the machine would take care eventually, but I had to disconnect the camera when I picked up for the evening.  Therefore I can't see the queue anymore so I don't  know what's happening.

 

I love BYE and have for years, but I think this particular feature requires a little more thought.  I will return to 2.09 for planetary in the future until something is improved here.

 

Not a lot of people knows this but BackyardEOS can use VirtualDUB to encode the AVI if the packaged commercial encoder I use causes some issues on some computers.

 

It is now possible to have BYE use VirtualDUB directly to encode your AVI if you prefer it over BYE's native commercial encoder.  One benefit I have found is that VirtualDUB is a bit less power hungry to encode so this will have a benefit on slower/older laptop.

 

To use VirtualDUB you need to download it and copy both 'virtualdub.exe' and 'vdub.exe' into the "BackyardTEMP\Download\" folder; BYE will use it automatically.

 

I can not package VirtualDUB with BackyardEOS due to its license schema, this is why this is a manual download and manual copy of files.

 

Hope this helps,

 

Guylain

Link to comment
Share on other sites

I am also having trouble with planetary video downloads.  Last night I shot a number of vids of Mars and Saturn.  6 downloaded and compiled into AVIs with no problem (a little slow but they were large vids) now I have 11 vids that never compiled.  I can only find four of them in the download folder and they seem to all be jpegs.  I have left BYE running overnight in hopes that this was just some quirk that the machine would take care eventually, but I had to disconnect the camera when I picked up for the evening.  Therefore I can't see the queue anymore so I don't  know what's happening.

 

I love BYE and have for years, but I think this particular feature requires a little more thought.  I will return to 2.09 for planetary in the future until something is improved here.

 

Not a lot of people knows this but BackyardEOS can use VirtualDUB to encode the AVI if the packaged commercial encoder I use causes some issues on some computers.

 

It is now possible to have BYE use VirtualDUB directly to encode your AVI if you prefer it over BYE's native commercial encoder.  One benefit I have found is that VirtualDUB is a bit less power hungry to encode so this will have a benefit on slower/older laptop.

 

To use VirtualDUB you need to download it and copy both 'virtualdub.exe' and 'vdub.exe' into the "BackyardTEMP\Download\" folder; BYE will use it automatically.

 

I can not package VirtualDUB with BackyardEOS due to its license schema, this is why this is a manual download and manual copy of files.

 

Hope this helps,

 

Guylain

 

Interesting.  Thanks, Guylain.  I'll give that a try.  I assume that this is for future captures.

 

Will this work automatically for the 4 download lists of JPEGs I did manage to already get?  (FYI: I did not have the "save planetary JPGs" feature checked.)  Also what about the 7 captures that never downloaded at all?

Link to comment
Share on other sites

 

Interesting.  Thanks, Guylain.  I'll give that a try.  I assume that this is for future captures.

 

Will this work automatically for the 4 download lists of JPEGs I did manage to already get?  (FYI: I did not have the "save planetary JPGs" feature checked.)  Also what about the 7 captures that never downloaded at all?

 

Yes, it is for future recordings... but you can use VirtualDUB to encode the JPG into an AVI after the fact.

 

You have not lost any data, all of your non-encoded jpgs are still in "BackyardTEMP\download".  Encode them with virtualdub and you are good to go.

 

Hope this helps,

 

guylain

Link to comment
Share on other sites

Guylain:  Here is my log from last night.  You can see where some AVI files downloaded OK then BYE stopped doing them properly.  I hope this helps figure this out.  FYI; the laptop runs an Intel quad core processor with 6GB ram and a 1TB hard drive.

 

18:55:13  Licensed to Chris Desselles (cdesselles@iscgrp.com)

18:55:35  Attempting to connect camera...

18:55:35  Canon drivers 'Canon\' initialized.

18:55:38  Shutter counter = 5008

18:55:38  Canon EOS REBEL T2i CONNECTED!

20:21:36  Planetary imaging started.

20:21:42  Capturing 27.1 frames per second.

20:23:03  1500 planetary frames captured.

20:25:07  mars_Tv0''3s_100iso_1024x680_20140517-20h21m42s.avi downloaded

20:29:00  Planetary imaging started.

20:29:06  Capturing 26.9 frames per second.

20:30:20  1500 planetary frames captured.

20:30:40  Planetary imaging started.

20:30:45  Capturing 25.9 frames per second.

20:31:43  1500 planetary frames captured.

20:32:09  Planetary imaging started.

20:32:14  Capturing 25.3 frames per second.

20:33:44  1500 planetary frames captured.

20:34:00  Planetary imaging started.

20:34:05  Capturing 26.9 frames per second.

20:35:03  1500 planetary frames captured.

20:35:35  mars2_Tv0''3s_100iso_1024x680_20140517-20h29m06s.avi downloaded

20:35:49  Planetary imaging started.

20:35:54  Capturing 20.8 frames per second.

20:37:14  1000 planetary frames captured.

20:37:31  Planetary imaging started.

20:37:36  Capturing 22.1 frames per second.

20:38:10  mars21_Tv0''3s_100iso_1024x680_20140517-20h30m45s.avi downloaded

20:39:01  1000 planetary frames captured.

20:40:09  Imaging session started.

20:40:18  Imaging session completed successfully

20:40:42  mars21_Tv0''3s_200iso_1024x680_20140517-20h32m14s.avi downloaded

20:40:50  Imaging session started.

20:42:31  mars21_Tv0''3s_200iso_1024x680_20140517-20h34m05s.avi downloaded

20:43:05  Imaging session completed successfully

20:43:12  DRIFT ALIGN_LIGHT_Tv0''3s_100iso_000065.CR2 downloaded

20:43:40  mars21_Tv0''3s_400iso_1024x680_20140517-20h35m54s.avi downloaded

20:44:23  Imaging session started.

20:46:40  Imaging session completed successfully

20:46:44  DRIFT ALIGN_LIGHT_Tv0''3s_100iso_000066.CR2 downloaded

20:54:04  Imaging session started.

20:54:55  Imaging session started.

21:59:21  Imaging session started.

21:59:33  Imaging session completed successfully

22:00:34  Imaging session started.

22:00:45  Imaging session completed successfully

22:01:00  Imaging session started.

22:01:11  Imaging session completed successfully

22:01:25  Imaging session started.

22:01:36  Imaging session completed successfully

22:02:09  Imaging session started.

22:05:15  Imaging session completed successfully

22:06:06  Imaging session started.

22:06:39  Imaging session completed successfully

22:22:18  Imaging session started.

22:24:33  Imaging session completed successfully

22:24:35  PREVIEW_20140517-22h24m35s769ms.JPG downloaded

22:25:31  Imaging session started.

22:27:46  Imaging session completed successfully

22:27:48  PREVIEW_20140517-22h27m48s591ms.JPG downloaded

22:28:32  Imaging session started.

22:30:48  Imaging session completed successfully

22:30:51  PREVIEW_20140517-22h30m50s881ms.JPG downloaded

22:33:14  Imaging session started.

22:35:31  Imaging session completed successfully

22:35:34  PREVIEW_20140517-22h35m34s111ms.JPG downloaded

22:38:45  Planetary imaging started.

22:38:50  Capturing 26.7 frames per second.

22:39:51  1000 planetary frames captured.

22:42:29  Planetary imaging started.

22:42:34  Capturing 26.7 frames per second.

22:43:37  1000 planetary frames captured.

22:46:43  Planetary imaging started.

22:46:48  Capturing 27.2 frames per second.

22:47:51  1000 planetary frames captured.

22:48:09  Planetary imaging started.

22:48:15  Capturing 26.5 frames per second.

22:49:23  1000 planetary frames captured.

22:50:19  Planetary imaging started.

22:50:25  Capturing 26.6 frames per second.

22:52:18  Collection was modified after the enumerator was instantiated.

22:53:01  Planetary imaging started.

22:53:07  Capturing 26.9 frames per second.

22:54:10  1000 planetary frames captured.

22:55:13  Planetary imaging started.

22:55:18  Capturing 27.2 frames per second.

22:56:21  1000 planetary frames captured.

22:56:46  Planetary imaging started.

22:56:51  Capturing 27.5 frames per second.

22:57:56  1000 planetary frames captured.

22:59:29  Planetary imaging started.

22:59:35  Capturing 27.5 frames per second.

23:00:37  1000 planetary frames captured.

23:01:16  Imaging session started.

23:04:02  Camera SHUTDOWN!

23:04:09  Attempting to connect camera...

23:04:10  Shutter counter = 5008

23:04:10  Canon EOS REBEL T2i CONNECTED!

23:05:56  Planetary imaging started.

23:06:01  Capturing 26.3 frames per second.

23:06:08  100 planetary frames captured.

23:13:27  Camera SHUTDOWN!

23:17:30  Attempting to connect camera...

23:17:31  Shutter counter = 5008

23:17:31  Canon EOS REBEL T2i CONNECTED!

23:18:02  Planetary imaging started.

23:18:07  Capturing 28.1 frames per second.

23:18:08  10 planetary frames captured.

23:23:41  Camera SHUTDOWN!

 

 

Link to comment
Share on other sites

Both the camera and the laptop were running off of AC power.  No batteries involved.  USB cable only 3M long and did not drop out the camera at anytime.

 

 

Now: back to VirtualDub... I just downloaded it.  I looked all over for how to input the Jpegs to create an AVI but I don't see where to do this.  Any help out there guys?

Link to comment
Share on other sites

The Canon SDK reported several unexpectedly shutdowns.  It gave no info as to why these events happened.  I was just trying to give you some direction as to where to look for the root cause.  These unexpected camera shutdowns are not caused by BYE.  BYE is merely reporting the event to you as it was told about it by the Canon software.

 

I still think that the most likely causes are disconnects caused by a bad USB cable or a power interruption.

 

 

Link to comment
Share on other sites

Fortunatley, I can explain the several camera shutdowns.  I was quitting for the night when i noticed the several files still in the queue to be downloaded.  With the camera offline the file information wasn't visible.  So I reconnected. Did this a couple of times while trying to understand the situation.  I'm pretty confident there was no USB cable problem.

 

I do appreciate your comments however.  I will always keep in mind to make sure of my connections.  Thanks.

 

 

 

Link to comment
Share on other sites

Now: back to VirtualDub... I just downloaded it.  I looked all over for how to input the Jpegs to create an AVI but I don't see where to do this.  Any help out there guys?

 

What software are you using for stacking?  Most software can just as easily stack the individual JPGs as opposed to an AVI file.

 

I'm not home right now, I'll try to check VDub later and get back to you.

 

Guylain

Link to comment
Share on other sites

Stacking software:  Autostakkert2  (I tried Registax6 on one of the videos that did compile OK but it refused to load it.)  I also have AVIStack, but I haven't used it in awhile.  Autostakkert accepted the AVI that Registax choked on.

Link to comment
Share on other sites

I have also had RegiStax choke on some of my videos created by BYEOS, but only some of them.  The author of RegiStax speculated that my issue is due to not having the correct codec, but if that were the case I would think that the failure of RegiStax to load my videos would be consistent.

 

I believe that my issue is a Windows issue, not RegiStax and not BYE.  When I ask RegiStax to open my video, a Windows file open dialog appears.  When I click on the video file name, the dialog wants to display a thumbnail of the selected file.  The thumbnail image is never displayed and the dialog hangs.  I have to use the Task Manager to kill RegiStax.  As I said, this does not happen with all the videos that I have captured with BYE, but it does happen enough that I no longer try to use the avi files.  Interestingly, all the video files will play in the Windows video player app.

 

My workaround is to select the JPG files for processing by RegiStax.

Link to comment
Share on other sites

I have tried using Autostakkert to stack the videos and then importing the resultings TIFs into Registax for waveltes sharpening.  This works pretty well.  I did't realize I could import all 2000 JPEGs of a video into Registax without them being compiled into an AVI.  How is this done?

 

Also, although it is related, we are getting a touch off topic.  My real question is why did BYE properly compile 4 videos then choke on compiling the rest?  Especially since the were all taken in order at the same settings with only a short delay between captures to check tracking and focus.  Is there a limit to how many can be in the queue before the traffic backlog overwhelms the process?  This is the only thing I can think of that would have caused this issue.

Link to comment
Share on other sites

To get AutoStakkert2 to process a stack of JPG / TIFF, simply select the Source Images in Windows Explorer or most any Image Catalog App and Drag-n-Drop onto the main AS2 Window (you cannot use the File Open dialog).

 

The only oddity is that AS2 will post the resulting Stacked Images to the Parent Directory above that which the Source Images came and named for the Directory (not the Filenames) of those Source Images - a slightly odd choice explained as a philosophy  that the Directory serves same purpose as the AVI "Wrapper" for a Video File.

Link to comment
Share on other sites

A couple of weeks ago a person complained about slow downloads from the camera into BYE.  The problem was traced to the use of AVG anti-virus software. If your problem is re-creatable, I would suggest temporarily disabling your anti-virus software to see if the symptoms change.

Link to comment
Share on other sites

Send me your log files at support@binaryrivers.com and I should be able to tell you more about the issue.

 

But Rick has a point about anti-virus.  Run a quick test with your anti-virus off to either confirm or eliminate it from being the cause.

 

1) Disable your anti-virus

2) Run the same test in BackyardEOS

3) Re-enable your anti-virus.

 

Did step #2 take as long as it did before?

 

Keep us posed,

 

Guylain

Link to comment
Share on other sites

Send me your log files at support@binaryrivers.com and I should be able to you mare about the issue.

 

But Rick has a point about anti-virus.  Run a quick test with your anti-virus off to either confirm or eliminate it from being the cause.

 

1) Disable your anti-virus

2) Run the same test in BackyardEOS

3) Re-enable your anti-virus.

 

Did step #2 take as long as it did before?

 

Keep us posed,

 

Guylain

 

how do I find my log files?

I run no anti virus

 

and thank u everyone for the quick response

Link to comment
Share on other sites

Send me your log files at support@binaryrivers.com and I should be able to you mare about the issue.

 

But Rick has a point about anti-virus.  Run a quick test with your anti-virus off to either confirm or eliminate it from being the cause.

 

1) Disable your anti-virus

2) Run the same test in BackyardEOS

3) Re-enable your anti-virus.

 

Did step #2 take as long as it did before?

 

Keep us posed,

 

Guylain

 

how do I find my log files?

I run no anti virus

 

and thank u everyone for the quick response

 

They are in 'My Pictures\BackyardTEMP\logs'.

 

Guylain

Link to comment
Share on other sites

Tried it again Saturday night.  BYE locked up with 3 videos in the queue.  I had to close and restart BYE.  This time I waited for each video to complete and the queue to clear between videos.  I was able to shoot 15 in a row of 1000 frames each with no issues.  There was roughly a 90 second delay to clear the queue between videos which is perfectly acceptable to me, but the queue is not working as intended.

Link to comment
Share on other sites

Tried it again Saturday night.  BYE locked up with 3 videos in the queue.  I had to close and restart BYE.  This time I waited for each video to complete and the queue to clear between videos.  I was able to shoot 15 in a row of 1000 frames each with no issues.  There was roughly a 90 second delay to clear the queue between videos which is not unacceptable, but the queue is not working as intended.

 

Boy... I can wait to release 3.1.  This should work way better.

 

BYE did not lock up, it worked as designed.  The encoding are put in a queue and processed one at a time.

 

Would you be open for me to send you a pre-release of 3.1 to run a few tests?

Link to comment
Share on other sites

Tried it again Saturday night.  BYE locked up with 3 videos in the queue.  I had to close and restart BYE.  This time I waited for each video to complete and the queue to clear between videos.  I was able to shoot 15 in a row of 1000 frames each with no issues.  There was roughly a 90 second delay to clear the queue between videos which is not unacceptable, but the queue is not working as intended.

 

Boy... I can wait to release 3.1.  This should work way better.

 

Would you be open for me to send you a pre-release of 3.1 to run a few tests?

 

I'll add that 90 seconds is NOT unacceptable.  Video encoding is CPU intensive and that takes time, there is no way around that <_>

 

BUT, in v3.1 the video encoding runs in a different Windows process and as a result will have very little impact on the BYE user interface for subsequent planetary recordings.

 

Does this make sense?

Link to comment
Share on other sites

Yes, makes a lot of sense.  And I would be open to trying a pre-release of 3.1 (in fact, I would be honored.) But I'm probably not the guy to do it in a timely fashion for you.  My sessions at the scope can be few and far between at times due to weather here in south Louisiana and with my own hectic non-astronomy schedule.  But I will be waiting in joyous anticipation of 3.1.  Even with some of these quirks, BYE is still the best thing out there in my opinion.

Link to comment
Share on other sites

I run no anti virus

 

 

You really really should. Even if the computer you use for AP seldom connects to the internet.

 

AVG and Avast! Anti-Virus are decent free utilities.  You might also want to look at getting some anti-spyware software.  Don't rely solely on Microsoft's "security" ;)

 

Paul

Link to comment
Share on other sites

I agree that AV software can impact disk performance depending on the AV software and whether it scans files as they're written and/or read. What I should have said is that anti-virus should be installed, but switched off when imaging.  I was thinking more in terms of my own setup where I use a laptop which is disconnected from the network when I'm imaging and AV disabled.  

 

I re-enable it when not imaging, and before re-connecting to the network

 

Imagine: You've spent many hours collecting subs and producing a masterpiece image only to be hit by CryptoLocker. Not a good situation to be in if you don't have a clean backup! <_<

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