Two strange problems

[Heno]

Hi

last night I had two problems. I have seen them both before, but considered them to be coincidences. But they were not.

1. At some point  BYN refused to display preview images. No matter what I did I could not make them show. I had to use an other program to display them.

2. During a long night imaging I have to change the battery pack. A few times I have forgotten to disconnect before removing the battery. The loss of power of course disconnects BYN, but it is then impossible to reconnect. I get a message that I have to select the correct Canon driver. (Don't remember the exact wording in the pop-up window.) Only solution is to shut down BYN and restart it. That solved the problem.

 

-2016-03-08.txt]

 

Helge

 

 

[admin]

I need the backgorund worker logfiles for the preview image now working.

 

You get a Canon driver error in BYN?  Odd.  

 

That is standard behavior for the Nikon SDK.  If the camera shutsdown due to lack of power you need to restart BYN.  This is because the nikon driver need to restart as well.

[astroman133]

Your comment that " BYN refused to display preview images. No matter what I did I could not make them show." is a bit vague. What did you try and what happened? What kiinds of image files were you trying to preview?

[Heno]

@astroman123: I was simply using the Preview button in the imaging section to see what was in the frame before I started the imaging session. After a few frames, no further images were displayed.

 

Here is the backgroundworker file, I hope it's the right one:

-2016-03-08.txt]

 

I tried to provoke the Canon driver error by removing the battery without disconnecting. But I could not. And not only that. The camera reconnected nicely without restarting BYN. According to yourself, it should not. I am not complaining over that it reconnected, but this is somewhat confusing though.

 

Helge.

[astroman133]

Heige,

 

There are 2 Preview buttons in BYE/BYN.  The first button allows you to display images when the application is not connected to your camera.  You simply drag and drop the image file onto the image area of the app while in Preview mode.  The other Preview functionality is on the Imaging screen and allows you to display a JPG image using the first row of capture settings in your capture plan. I did not know which Preview function you were having trouble with.

 

So, from what you have said I am assuming that you are on the Imaging screen and that Clicking on the Preview button in the lower right corner (beside the Loop button) does not take a picture. I could not duplicate your issue using BYE 3.1.6 with my T5i.

 

The log file does not appear to be the the correct file.  I could find no useful information it it...Perhaps Guylain will have better luck.  I suspect that the background worker does not know the difference between a Preview image and a regular image.

[admin]

@astroman123: I was simply using the Preview button in the imaging section to see what was in the frame before I started the imaging session. After a few frames, no further images were displayed.

 

Here is the backgroundworker file, I hope it's the right one:

logfile-20160307-22h39m06s516-backgroundworker-[9992-2016-03-08.txt]

 

I tried to provoke the Canon driver error by removing the battery without disconnecting. But I could not. And not only that. The camera reconnected nicely without restarting BYN. According to yourself, it should not. I am not complaining over that it reconnected, but this is somewhat confusing though.

 

Helge.

 

Glad it reconnected.  I'm just baffled by the Canon driver error you got using BYN.  Maybe the root cause/bug is related to that.  I'll keep this is mind if this gets reported again.

 

Thank you for the log files.

[Heno]

@Astroman133: Yes, it is the button in the imaging screen. But it do take the picture. It is in the BYN folder. The picture just is not displayed on the screen and it does not show up as a thumb in the lower edge. If I want to see the image I will have to open it in a different viewer. And it does not affect all images, but once it's stopped displaying images, it just won't display any more, no matter how many I take.

 

I find this display bug much more annoying than the re-connect issue. Here I just need to remember to disconnect before I remove the battery. 

 

Helge.

[astroman133]

OK, so when you click on the Preview button on the Imaging screen BYN captures and downloads the image, but does not display it either as a thumbnail or in the main image area. However, the image exists in the specified BYN Download folder and can be opened by other applications.

 

The previously-attached background worker log file does not appear to have any obvious errors (at least to my untrained eye). Perhaps the main application log file has more information.

 

When you start your complete capture plan, are the images displayed, or is it only a problem with the Preview button?

 

I also assume that you are using the latest version of BYN and that the camera's firmware has not been updated or hacked in any way, as others have experienced issues where when the firmware is changed, the camera is no longer compatible with the version of the Nikon SDK that BYN uses.

 

If you switch to shooting JPG instead of NEF, do you still see this issue?  Does temporarily disabling your anti-virus software have any affect?

 

Guylain may want you to upload the additional application log file for a session when this issue occurred.

[admin]

I found this in the log files.

 

2016-03-08 01:50:31,228 [ProcessPreview(Normal)] INFO  - GdPicture img_1.JPG
2016-03-08 01:50:31,559 [ProcessPreview(Normal)] ERROR - Ikke nok minne.
2016-03-08 01:50:31,559 [ProcessPreview(Normal)] ERROR -    ved System.Drawing.Graphics.CheckErrorStatus(Int32 status)
   ved System.Drawing.Graphics.DrawImage(Image image, Int32 x, Int32 y, Int32 width, Int32 height)
   ved System.Drawing.Bitmap..ctor(Image original, Int32 width, Int32 height)
   ved System.Drawing.Bitmap..ctor(Image original)
   ved BinaryRivers.Common.ImageLoader.GdJpgImageProvider.LoadImage(FileInfo file)

It looks like there is something wrong with the jpeg... or the library I use to ready the file.

 

Try with raw NEF only.  Please report back your findings.

[Heno]

 

I found this in the log files.

 

2016-03-08 01:50:31,228 [ProcessPreview(Normal)] INFO  - GdPicture img_1.JPG
2016-03-08 01:50:31,559 [ProcessPreview(Normal)] ERROR - Ikke nok minne.
2016-03-08 01:50:31,559 [ProcessPreview(Normal)] ERROR -    ved System.Drawing.Graphics.CheckErrorStatus(Int32 status)
   ved System.Drawing.Graphics.DrawImage(Image image, Int32 x, Int32 y, Int32 width, Int32 height)
   ved System.Drawing.Bitmap..ctor(Image original, Int32 width, Int32 height)
   ved System.Drawing.Bitmap..ctor(Image original)
   ved BinaryRivers.Common.ImageLoader.GdJpgImageProvider.LoadImage(FileInfo file)

It looks like there is something wrong with the jpeg... or the library I use to ready the file.

 

Try with raw NEF only.  Please report back your findings.

 

The Preview button always takes/displays JPEGs (far as I am able to tell) so whether camera is set to RAW or JPEG should not matter. I always shoot RAW, not RAW + JPEG. I always save to PC only.

There is nothing wrong with the JPEGs. They display correctly, just not in BYN. I have never had this problem during ordinary sessions, only with the preview button. I don't think anti virus program has anything to do with it. At least it does not give any alarms or anything. And it's usually very quick to do that if it sees anything unusual.

 

For your info, the second line in the log file copy above reads "Not enough memory" in Norwegian. That is really strange because if I had a memory problem I should not be able to start a second viewer or any other program. Is it possible that BYN somehow holds all preview files in memory without freeing up memory when next images is taken? Outside my competence, just asking.

Next time I'm out imaging I will follow up on this very closely. But for now, this is all the info I have.

 

Helge.

[astroman133]

"if I had a memory problem I should not be able to start a second viewer or any other program"

 

Memory allocation is more complicated than that. A program can run out of its alloted memory and there is still system memory available to start new applications.

 

However, you may have hit on something...Windows is not always good about freeing up memory that is allocated to bitmaps.  I could envision a scenario where BYN could run out of memory through repeated use of the Preview button, especially because it is a 32-bit app.  That should be pretty straightforward for Guylain to verify and address.  If use of the Preview button is not common it would also explain why other BYN and BYE users are not reporting the same issue...I do not use it on a regular/frequent basis.  I hope that is it.

[admin]

Go in settings and set the image quality to "in-camera" and use the camera menu to ensure it is set to raw only.  Then try it.

 

The memory error is misleading.  When a bitmap is loaded a memory allocation is reserved, but sometime is reserved a few bits less than needed and when this occurs you get and out of memory error... not because you are running of memory (you are not) but because the allocation was wrongfully set by Windows/.Net in the first place.

 

Keep us posted.