Photos in \BackyardTEMP\Download

[dts350z]

How do photos end up in \BackyardTEMP\Download with short names instead of in the proper folder with long names?

 

Is it because I'm not adding pause time (for flats, darkflats, and bias).

 

E.G. I ask for 50 flats and I end up with less than 50 in the proper folder, and some of then in the download folder.

[Jerry_K]

I have 3.0.3, the latest released, as you know.

 

It didn't tell me anything when I shut it down.

 

I'll watch for indexations next time I'm ready to shut down.

 

Thanks,

Z

 

 

It almost happened to me few nights ago. I was doing Planetary and was about to shut down the system when I noticed number 4 flashing at the top center and then go to #3 so I stopped right there and let BYE finish the download. No idea if BYE would give me warning if I would hit the close button.

Jerry

[Jerry_K]

 

Yes, you have a flashing number indicator in the camera information centre.  On top of this BYE will tell you if you try to close it while images are still in the queue.

 

In 3.0.x the process is terminated if you close BYE.

 

In 3.1 you can close BYE and the background worker will continue to work on them just the same

 

Hope this helps,

 

Guylain, there is 3.1? How did I missed this?

Jerry

[dts350z]

He hasn't released 3.1 yet, but it's under development.

 

So this problem is pervasive for me and NOT do to me quitting BYEOS. In the log file we have:

 

 

2014-06-22 10:54:39,899 [PREVIEW IMG_0121.JPG] ERROR - Fail to load 'IMG_0121.JPG' attempt 2

2014-06-22 10:54:39,899 [PREVIEW IMG_0121.JPG] ERROR - Out of memory.

2014-06-22 10:54:39,899 [PREVIEW IMG_0121.JPG] ERROR -    at System.Drawing.Image.FromStream(Stream stream, Boolean useEmbeddedColorManagement, Boolean validateImageData)

   at BinaryRivers.ImageLoaderProviders.JpgProvider.Load(String fullname)

2014-06-22 10:54:40,905 [PREVIEW IMG_0121.JPG] ERROR - Unable to load image file error

2014-06-22 10:54:40,905 [PREVIEW IMG_0121.JPG] ERROR -    at BinaryRivers.Common.ImageLoader.ImageLoader.Load(String fullpath, Boolean limitsize)

   at BinaryRivers.Orchestrator.Processors.CameraImageDownloadProcessor.LoadImageWithStats(String fullname, ImageSourceEnum imgsource, Bitmap& bitmap, Statistics& statistics)

   at BinaryRivers.Orchestrator.Processors.CameraImageDownloadProcessor.<>c__DisplayClasse.<ProcessImagePreview>b__d()

2014-06-22 10:54:40,905 [PREVIEW IMG_0121.JPG] ERROR - IMG_0121.JPG

2014-06-22 10:54:40,905 [PREVIEW IMG_0121.JPG] ERROR - 

2014-06-22 10:54:40,906 [CameraImageDownloadProcessor] DEBUG - Background Processing PriorityQueue.Count (END) = 1

2014-06-22 10:54:54,861 [Main] DEBUG - ButtonPlus_MouseClick(btnPreview = 'Preview')

 

So previews fail to load and this morning I asked for 30 flats and only got 18, then 30 dark flats and only got 11, due to these out of memory errors.

 

FYI my work flow is to image until 2 or 3 in the morning (or whenever the fog rolls in or DSO goes behind a tree or hill) then setup to take darks and go to bed. In the morning I take my BIAS, FLATS, and DARK FLATS, without quitting BYEOS, and removing the mirror lock delay. I don't have any pause.

 

These morning sessions are when I often have the memory error, but it also happens at other times; however I'm wondering if:

 

1) Leaving BYEOS running overnight has anything to do with it.

2) If Capture plans with no mirror lock, pause, etc. exacerbates or create the problem.

 

 

 

[Jerry_K]

He hasn't released 3.1 yet, but it's under development.

 

So this problem is pervasive for me and NOT do to me quitting BYEOS. In the log file we have:

 

 

2014-06-22 10:54:39,899 [PREVIEW IMG_0121.JPG] ERROR - Fail to load 'IMG_0121.JPG' attempt 2

2014-06-22 10:54:39,899 [PREVIEW IMG_0121.JPG] ERROR - Out of memory.

2014-06-22 10:54:39,899 [PREVIEW IMG_0121.JPG] ERROR -    at System.Drawing.Image.FromStream(Stream stream, Boolean useEmbeddedColorManagement, Boolean validateImageData)

   at BinaryRivers.ImageLoaderProviders.JpgProvider.Load(String fullname)

2014-06-22 10:54:40,905 [PREVIEW IMG_0121.JPG] ERROR - Unable to load image file error

2014-06-22 10:54:40,905 [PREVIEW IMG_0121.JPG] ERROR -    at BinaryRivers.Common.ImageLoader.ImageLoader.Load(String fullpath, Boolean limitsize)

   at BinaryRivers.Orchestrator.Processors.CameraImageDownloadProcessor.LoadImageWithStats(String fullname, ImageSourceEnum imgsource, Bitmap& bitmap, Statistics& statistics)

   at BinaryRivers.Orchestrator.Processors.CameraImageDownloadProcessor.<>c__DisplayClasse.<ProcessImagePreview>b__d()

2014-06-22 10:54:40,905 [PREVIEW IMG_0121.JPG] ERROR - IMG_0121.JPG

2014-06-22 10:54:40,905 [PREVIEW IMG_0121.JPG] ERROR - 

2014-06-22 10:54:40,906 [CameraImageDownloadProcessor] DEBUG - Background Processing PriorityQueue.Count (END) = 1

2014-06-22 10:54:54,861 [Main] DEBUG - ButtonPlus_MouseClick(btnPreview = 'Preview')

 

So previews fail to load and this morning I asked for 30 flats and only got 18, then 30 dark flats and only got 11, due to these out of memory errors.

 

FYI my work flow is to image until 2 or 3 in the morning (or whenever the fog rolls in or DSO goes behind a tree or hill) then setup to take darks and go to bed. In the morning I take my BIAS, FLATS, and DARK FLATS, without quitting BYEOS, and removing the mirror lock delay. I don't have any pause.

 

These morning sessions are when I often have the memory error, but it also happens at other times; however I'm wondering if:

 

1) Leaving BYEOS running overnight has anything to do with it.

2) If Capture plans with no mirror lock, pause, etc. exacerbates or create the problem.

 

 

 

Is it possible that USB cable is the culprit? When I bought BYE years ago and started using it I had very similar problem but after changing USB cable that many members recommended the problem disappeared.

Jerry

[dts350z]

I don't think so, Guylain told me it's a bug in .net.

 

 

[Jerry_K]

I don't think so, Guylain told me it's a bug in .net.

 

 

Ouch, that's a bummer. Is it something that he can fix?

[astroman133]

What is your PC configuration?  It is not normal to run out of memory if you have a reasonably-sized computer.  How much memory? What processor? What version of Windows?

 

Nobody else has reported that error to this forum, so it seems like it is specific to your setup.

[s3igell]

Remember that you can find the Memory Usage details for each Process on the Processes Tab of TaskManager...

 

If you record those numbers at the Start and After Imaging and After Letting BYN Sit Idle and After Attempting Darks, you'll likely find which actions accompany the largest Memory Usage / Leaks...

[admin]

I don't think so, Guylain told me it's a bug in .net.

 

 

Ouch, that's a bummer. Is it something that he can fix?

 

Yep, but... it is very, very, extremely rare.  I have had 3 reported instance in over 4 years with thousands and thousands of images taken by hundreds and hundreds of users.

 

 

[dts350z]

Brand new dell ultra book

i7-4600U, 8 GB of RAM, SSD

Plenty of free memory when this happens.

windows 7 Enterprise 64 bit

 

Yes, I have a 10M active USB cable, but that shouldn't be related to this "out of memory" error(?). Besides, I can PHD guide, image capture (even planetary), control the mount, use astrotorilla, etc. etc. all through the cable with no (other) issues and when this happened this morning BYEOS was the only thing using the cable.

 

Looking at the log files I have this happens in about 15% of my sessions.

 

 

[Jerry_K]

I don't think so, Guylain told me it's a bug in .net.

 

 

Ouch, that's a bummer. Is it something that he can fix?

 

Yep, but... it is very, very, extremely rare.  I have had 3 reported instance in over 4 years with thousands and thousands of images taken by hundreds and hundreds of users.

 

Guylain, why so modest? Hundreds of users? Thousands of images? I alone have recorded over 12,000 jpgs in Planetary in just last 2 days

Jerry

[admin]

Brand new dell ultra book

i7-4600U, 8 GB of RAM, SSD

Plenty of free memory when this happens.

windows 7 Enterprise 64 bit

 

Yes, I have a 10M active USB cable, but that shouldn't be related to this "out of memory" error(?). Besides, I can PHD guide, image capture (even planetary), control the mount, use astrotorilla, etc. etc. all through the cable with no (other) issues and when this happened this morning BYEOS was the only thing using the cable.

 

Looking at the log files I have this happens in about 15% of my sessions.

 

 

 

I don't think this is cable related.  Basically when an image is creating in low level memory the exact number of bytes is reserved first in memory, then the image is loaded into that reserved memory space... and when it does not have enough space it throws an out of memory error.  Again, this is not the computer that is out of memory but rather the memory reserved to load the image that ran out.

 

Do you get this on that computer only or other computer as well?

[dts350z]

Well that will be a project to set up everything on a 2nd computer.

 

I'll see what I can do.

 

Should I try .net updates on the first computer?

 

 

[admin]

Should I try .net updates on the first computer?

Good question.  I'm not sure but having it up to date can't hurt.

[dts350z]

Update:

 

I went to windows update and installed all updates having to do with .NET.

 

I did not have any out of memory errors last night or this morning. So far so good. I'll keep you posted.

 

However, there were some new/different problems. When I checked for files in /temp, there is one, and here is the corresponding entry in the log file:

 

 

2014-06-23 09:07:24,302 [img_0007.CR2] INFO  - Success: EDSDK.EdsGetImage(img_ref, imageSource, bitmapImageType, imageInfo.EffectiveRect, outputSize, stream)

2014-06-23 09:07:24,317 [img_0007.CR2] INFO  - Running (log): EDSDK.EdsGetPointer(stream, out streamPointer)

2014-06-23 09:07:24,317 [img_0007.CR2] INFO  - Success: EDSDK.EdsGetPointer(stream, out streamPointer)

2014-06-23 09:07:24,317 [img_0007.CR2] INFO  - Running (log): EDSDK.EdsRelease(stream)

2014-06-23 09:07:24,317 [img_0007.CR2] INFO  - Success: EDSDK.EdsRelease(stream)

2014-06-23 09:07:24,317 [img_0007.CR2] INFO  - Running (log): EDSDK.EdsRelease(img_ref)

2014-06-23 09:07:24,317 [img_0007.CR2] INFO  - Success: EDSDK.EdsRelease(img_ref)

2014-06-23 09:07:24,317 [img_0007.CR2] INFO  - Running (log): EDSDK.EdsRelease(img_strm)

2014-06-23 09:07:24,317 [img_0007.CR2] INFO  - Success: EDSDK.EdsRelease(img_strm)

2014-06-23 09:07:24,426 [img_0007.CR2] INFO  - Running (log): EDSDK.EdsRelease(stream)

2014-06-23 09:07:24,426 [img_0007.CR2] INFO  - WARNING 4294967295 : EDSDK.EdsRelease(stream) 

2014-06-23 09:07:24,426 [img_0007.CR2] INFO  - Running (log): EDSDK.EdsRelease(img_ref)

2014-06-23 09:07:24,426 [img_0007.CR2] INFO  - WARNING 4294967295 : EDSDK.EdsRelease(img_ref) 

2014-06-23 09:07:24,426 [img_0007.CR2] INFO  - Running (log): EDSDK.EdsRelease(img_strm)

2014-06-23 09:07:24,426 [img_0007.CR2] INFO  - WARNING 4294967295 : EDSDK.EdsRelease(img_strm) 

2014-06-23 09:07:24,426 [img_0007.CR2] INFO  - Read RAW Image/Bitmap: END

2014-06-23 09:07:24,426 [img_0007.CR2] DEBUG - TOTAL .CR2 LOAD TIME ms = 717.6012

2014-06-23 09:07:24,551 [img_0007.CR2] ERROR - Parameter is not valid.

2014-06-23 09:07:24,551 [img_0007.CR2] ERROR -    at System.Drawing.Bitmap..ctor(Int32 width, Int32 height, PixelFormat format)

   at System.Drawing.Bitmap..ctor(Image original, Int32 width, Int32 height)

   at System.Drawing.Bitmap..ctor(Image original)

   at BinaryRivers.Orchestrator.Processors.CameraImageDownloadProcessor.LoadImageWithStats(String fullname, ImageSourceEnum imgsource, Bitmap& bitmap, Statistics& statistics)

   at BinaryRivers.Orchestrator.Processors.CameraImageDownloadProcessor.<>c__DisplayClass5.<ProcessImageCapture>b__4()

 

Also at the end of my lights last night I had a strange issue when I tried to take my darks. BYEOS would "beep" at me each time I tried to start the capture session, and the log data on the left top kept saying (I think) "end of session" or similar. No errors in the log file. I tried a bunch of things like disconnecting and reconnecting the camera in BYEOS, killing and restarting BYEOS, physically disconnecting the camera and USB hub, but nothing worked. I could do frame and focus, but could not preview or start a capture plan.

 

What finally fixed it was a reboot on the laptop.

 

Strange.

 

Anyway, as a said I'll keep posting any issues and also if I DON'T see any more out of memory errors.

 

Thanks for the support!

Z

 

 

[dts350z]

OK this issue:

 

Also at the end of my lights last night I had a strange issue when I tried to take my darks. BYEOS would "beep" at me each time I tried to start the capture session, and the log data on the left top kept saying (I think) "end of session" or similar. No errors in the log file. I tried a bunch of things like disconnecting and reconnecting the camera in BYEOS, killing and restarting BYEOS, physically disconnecting the camera and USB hub, but nothing worked. I could do frame and focus, but could not preview or start a capture plan.

What finally fixed it was a reboot on the laptop.

Strange.

 

Is related to the SSD being almost full. It happened again tonight and while trouble shooting I noticed my C drive was "full". Deleting some large files put me back in business.

 

 

 

[admin]

OK this issue:

 

Also at the end of my lights last night I had a strange issue when I tried to take my darks. BYEOS would "beep" at me each time I tried to start the capture session, and the log data on the left top kept saying (I think) "end of session" or similar. No errors in the log file. I tried a bunch of things like disconnecting and reconnecting the camera in BYEOS, killing and restarting BYEOS, physically disconnecting the camera and USB hub, but nothing worked. I could do frame and focus, but could not preview or start a capture plan.

What finally fixed it was a reboot on the laptop.

Strange.

 

Is related to the SSD being almost full. It happened again tonight and while trouble shooting I noticed my C drive was "full". Deleting some large files put me back in business.

 

 

 

Ha, that explains it

 

Thank you for reporting back.

 

Regards,

[dts350z]

reviewing log files from last night, I do still have the "out of memory" errors. This is after the .net updates. <_

[admin]

reviewing log files from last night, I do still have the "out of memory" errors. This is after the .net updates. <_>

 

I'm using a different library in 3.1 to load raw files, I think this should solve your issue.

 

Regards,

[dts350z]

Thanks, looking forward with anticipation!

 

Another data point, It happened again, first thing in the morning after leaving BYEOS on all night, as I was setting up to take Flats, and previewing to get the exposure right ( I keep forgetting to see if I can put the camera on auto for Flats with BYEOS).

 

Anyway I quit and restarted BYEOS and it was fine.

 

Any chance there's a memory leak somewhere? I ask because (not exclusively) it seems to happen more frequently after having BYEOS on for more than 10 or so hours.

 

Probably unrelated but I also tend to forget and leave stellarium running, so the laptop is working pretty hard all night (fan running constantly).

 

Cheers,

Z

 

[s3igell]

Did you happen to capture your Flats as the last sequence of the night ??  And Terminate BYE very shortly thereafter ??

For Short Exposure Images such as Flats (actually any exposures under 30sec), BYE queues them into the Temp Directory and then processes their EXIF and FileNames after the end of the Capture Plan.

 

If you terminated BYE before that queued process was completed...

[dts350z]

Yes that could be it.

 

Is there some indication that BYEOS is sill working on something?

 

 

 

[admin]

Yes that could be it.

 

Is there some indication that BYEOS is sill working on something?

 

 

 

Yes, you have a flashing number indicator in the camera information centre.  On top of this BYE will tell you if you try to close it while images are still in the queue.

 

In 3.0.x the process is terminated if you close BYE.

 

In 3.1 you can close BYE and the background worker will continue to work on them just the same

 

Hope this helps,

 

 

[dts350z]

I have 3.0.3, the latest released, as you know.

 

It didn't tell me anything when I shut it down.

 

I'll watch for indexations next time I'm ready to shut down.

 

Thanks,

Z