nikonians

Even though we ARE Nikon lovers,we are NOT affiliated with Nikon Corp. in any way.


Sign up Login
Home Forums Articles Galleries News Workshops Shop Recommended
members
All members Wiki Contests Vouchers Apps Newsletter THE NIKONIAN™ Magazines Podcasts Fundraising

Update to Photo Ninja Review in eZine #54

esantos

McAllen, US
12238 posts

Click to send email to this author Click to send private message to this author
esantos Moderator Nikonians Resources Writer. Recognized for his outstanding reviews on printers and printing articles. Awarded for his high level of expertise in various areas, including Landscape Photography Awarded for his extraordinary accomplishments in Landscape Photography. His work has been exhibited at the Smithsonian. Nikonian since 10th Nov 2002
Fri 21-Dec-12 01:13 PM | edited Fri 21-Dec-12 02:28 PM by esantos

Members:

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!

Ernesto Santos
esartprints.com Ernesto Santos Photography

G