PDA

View Full Version : registration and bug reports



Kerry Pierce
October 25th, 2006, 02:28 AM
I purchased BBPro and DLPro on an upgrade deal a few days ago and haven't gotten the reg keys yet. Just wondering if there is a problem with my purchase.

I haven't installed DLPro yet, waiting on the reg key, but BBPro is pretty cool, a very nice upgrade from my old version of BB. :)

Also, I've encountered a couple of bugs, one of them a rather nasty one, with BBPro.

Some of my files are TIF's edited from NEF files and BBPro is having difficulty displaying the thumbnails. It just shows a bunch of gibberish colors, but the file loaded okay in the preview. So, I had it regenerate the TIF thumbnail, which seemed to work okay, but it actually trashed the file. Clicking on the file brings up a preview image that's like a 16 color GIF. Trying to load the original file, BBPro immediately crashes and completely disappears. Trying to load the original into CS2 doesn't work with CS2 giving an error message about the file being trashed. Fortunately, I still have the original NEF. :D

The files are from the d200 and are either products of CS2 or Capture NX, not sure which one the problem files came from, but I think it was from NX.

If you need more info or sample files, please let me know.

Chris Breeze
October 25th, 2006, 08:42 AM
I'm sorry you haven't received your registration details yet. The most common reasons for this are an incorrect email address submitted with the order or our emails being blogged by antispam software or accidentally deleted. Please email [email protected] with details of your order.

Please can you send me a copy of the TIFF file with the bad thumbnail. We have had problems in the past with some raw converters writing garbled thumbnails in TIFFs.

Kerry Pierce
October 25th, 2006, 12:35 PM
I've sent a copy of the regsoft info to the support email address. I sent an email to the support address yesterday morning. Perhaps you've got my email addy in your kill file. :D It's the one in my profile for the forums here.

Here's a link a file that is likely to have the same issues as I reported. The thumb is corrupted like the other one. I deleted the one that got trashed and didn't try to regenerate the thumb on this file. It's 42megs.

http://download.yousendit.com/8F91A0D771E19D6B

Chris Breeze
October 25th, 2006, 01:46 PM
I think the problem is with your ISP rejecting all emails from my ISP because it thinks they are sending spam. I have tried sending it using a mail account with a different ISP.

Unfortunately I can't access the image on yousendit.com without the right username and password.

Kerry Pierce
October 25th, 2006, 11:25 PM
Huh... I never heard of comcast doing that before. Your notifications from the message boards get through just fine, as did your [email protected] email. So, I now have BBPro registered and will have to install DLPro. Thanks! :D

Here's another link to that file, which expires in 7 days. For some reason, the link posted on the yousendit.com page, which it said was the link to use, is significantly different than the one I got in email later on. You're not supposed to need a username and pword. :( I don't have an account there and don't login. Perhaps this link will work. If not, let me know and I'll try to figure out another place to put it.

http://www.yousendit.com/download/WSB%2BegOMwLg%3D

Thanks

Chris Breeze
October 26th, 2006, 10:24 AM
I've downloaded the TIFF and the problem is due to the way the thumbnail has been written. The offset to the thumbnail data appears to point to the wrong place - at what appears to be EXIF data within the TIFF not thumbnail image data. This results in garbage being displayed.

When you attempt to regenerate the thumbnail in BBPro it writes correct thumbnail data to the thumbnail offset, but because the offset is wrong it overwrites EXIF data which can trash the file. Unfortunately there isn't much I can do about this because the TIFF file has not been written correctly in the first place.

Kerry Pierce
October 26th, 2006, 01:05 PM
Okay, thanks, Chris. I'll keep closer track of the issue to try to determine which program is doing that. I'll let you know and report it to them as well.