Update to Photo Ninja Review in eZine #54
esantos
Nikonian since 10th Nov 2002
Fri 21-Dec-12 09:13 AM | edited Fri 21-Dec-12 10:28 AM by esantos
Ernesto Santos
esartprints.com Ernesto Santos Photography
Get my new e-Book "Churches of Texas"
See my portfolio.
-
#1. "RE: Update to Photo Ninja Review in eZine #54" | In response to Reply # 0
zanz34 Nikonian since 11th Sep 2008Sat 29-Dec-12 09:49 PMGreetings Ernesto,
I want to apologize upfront if my question should be posted elsewhere. I upgraded to Photo Ninja from Noise Ninja several months ago. In Noise Ninja you were able to import specific camera noise profiles like the D300. I've upgraded from the D300 to D800. I was wondering if you know if noise profiles were developed for the D800 which can be imported into Photo Ninja. I really like the product and I'm looking forward to a batch processing capability much like that in Noise Ninja.
Sincerely,
Bob Z.-
#2. "RE: Update to Photo Ninja Review in eZine #54" | In response to Reply # 1
esantos Nikonian since 10th Nov 2002Sun 30-Dec-12 01:41 PMHello Bob,
At this time it looks like there is no Noise Ninja profile for the D800 based on the listed profiles here. I would recommend you contact PictureCode's tech support. I am sure they can assist you in this.Ernesto Santos
esartprints.com Ernesto Santos Photography
Get my new e-Book "Churches of Texas"See my portfolio.
-
G
Upload images
6
Uploading and including images in forums available to members on Silver membership level or higher. Please upgrade to take full advantage.
UPDATE - 12/21/2012
Jim Christian, Founder of PictureCode recently contacted me regarding my concerns about the speed performance of Photo Ninja. He pointed out that it is recommended to set the level of RAM in the program settings from 1/3 to 1/2 of the installed RAM. For my system, which has 16 GB, that means setting from 5 to 8 GB depending on how many memory hungry apps I run simultaneously. I set the memory allocation to 8 GB in the image cache in the Preferences dialog and tested the program. I saw a noticeable improvement with the issues I mention in the review. Additionally, Jim has made some changes in the latest release version 1.04b to further address this issue. He states:
"I tweaked the defaults in the 1.0.4b pre-release yesterday, so now it will use 30% of RAM on a 16GB system unless you have specified a different value. I think the previous 2GB default could be a little tight particularly for e.g. 36MPixel Nikon D800 images."
And in reference to the spinning icon issue and batch processing:
"The spinning icon just means it is processing parts of the image pyramid in the background. When the icon is red, it is updating what is currently visible on the screen. When it turns white, it is processing parts of the image that are off-screen at the current zoom level and/or at the 100% zoom level (so it will hopefully have less work to do when you go to render the file to JPEG/TIFF). Of course, you can keep working while it is spinning, and you don't have to wait for it to stop if you only want to update the XMP sidecar and close the image (via the "Done" button). If you render a 100% JPEG/TIFF, then it will wait for the processing to finish before it saves to disk.
Also, for what it's worth, we've had a lot of requests for batch processing and we're intending to implement it soon, as soon as we finish the Photoshop plug-in integration."
Thank you Jim!