BYN 1.0.5

[ABPiecka]

Guyroch,  FYI

 

I have been trying to get the new release to work with no luck.  I have downloaded it at least 6-8 times. I began  deleting the old versions and all related files between each after about the 3rd time.When I try to download I get the following:

 

C:|Program files\backyardnikonv1.0\binaryrivers.backyardnikon.start.camers1.exc

error: while trying to replace the existing file Deletefile failed;code 5

access is denied

 

the option abort,retry,ignore are available.  retry and ignore get nothing abort is the only option that works

 

when I tried to delete the BYN program files it is denied because of a file AForge.dll is in use

 

I finally got everything deleted and tried several more times and got the program to open only to not be able to connect to any of my cameras ( nikon 800, 800E, 7000)  Tried several times connecting disconnecting restart etc

 

Deleted all the BYN files related to 1.0.5 again including the AForge.dll,  loaded release 1.0.4 and it worked like a charm.

 

I'm up and running but am reluctant to try 1.0.5 again.

[admin]

You seem to be having issues at the OS level.  what you are describing seems pretty drastic.

 

Just reboot and install in a new folder.  Forget about the folder you are in right now because I have no clue what you or the os did.

 

You should never delete an installed software, use the uninstaller for that.

[admin]

I'll add that 1.0.4 and 1.0.5 are 100% identical with the only difference that 1.0.5 was compiled using a full set of new SDK files provided by Nikon in March 2016 to address connection issues with anyone who has upgraded their camera firmware with the latest firmware released by Nikon early 2016.

 

I have received 100% successful feedback from users indicating that 1.0.5 is now connecting where it was not with 1.0.4 after a firmware upgrade.

 

I have also received 100% successful feedback from users indicating that 1.0.5 is still connecting on cameras where firmware was not upgraded.

 

You are the exception so I'm wondering what is different.  I do have a D7000 and it does connect to both 1.0.4 and 1.0.5 just fine.  However, I do not own a D800 or D800E so I can not confirm first hand.

 

Regards,

[admin]

I'll add that 1.0.4 and 1.0.5 are 100% identical with the only difference that 1.0.5 was compiled using a full set of new SDK files provided by Nikon in March 2016 to address connection issues with anyone who has upgraded their camera firmware with the latest firmware released by Nikon early 2016.

 

I have received 100% successful feedback from users indicating that 1.0.5 is now connecting where it was not with 1.0.4 after a firmware upgrade.

 

I have also received 100% successful feedback from users indicating that 1.0.5 is still connecting on cameras where firmware was not upgraded.

 

You are the exception so I'm wondering what is different.  I do have a D7000 and it does connect to both 1.0.4 and 1.0.5 just fine.  However, I do not own a D800 or D800E so I can not confirm first hand.

 

Regards,

 

EDIT:  Looks like a handful are reporting 1.0.5 not connecting whereas 1.0.4 did on cameras where firmware was not upgraded.  If this is truly the case I will have to release 1.0.6 with an option to select which Nikon SDK files to use as I do with BackyardEOS and Canon cameras; this one has 3 different versions of SDK files packaged with the app.

[astroman133]

Could Nikon make it any harder on independent developers???

[admin]

Could Nikon make it any harder on independent developers???

 

There is 1 major bug in BYN... it's the connection bug... and this is tied to SDK.  Sadly for us developers we have no control over that.

 

Aside from this non-connection bug the SDK is as solid as the Canon SDK.  Canon deprecates older models form the SDK every couple of years and as a result I have had to split the SDK into (so far) 3 SDK version in BYE.

 

This new set of SDK from Nikon might (by the looks of it) require that I provide the 2 sets in BYN and have the user select the version of the SDK to use upon connecting the camera.

 

The real solution though would be to forgo the SDK altogether and use PTP protocol to communicate with the camera... but that would require a complete rewrite of the camera provider interface... that is at least 1 year of work if not more.

 

Regards,