![]() ![]() Moreover, there is a huge lack of available resources for help with setting up the iPhone 15 Pro camera, using it under different shooting situations, and using RAW files with LR, PS, Topaz or other post applications. I thought that it would be a simple point, zoom, shoot, crop and use like all of my other iPhone cameras. Now obviously there is nothing wrong with the iPhone 15 Pro’s camera. I bought the iPhone 15 Pro for the better camera, better lenses, more zoom, and the ability to shoot RAW so I could bring shots into Lightroom, Photoshop, etc. To date, the iPhone 15 Pro’s camera has disappointed me time and time again, it’s mind boggling that my previous iPhone cameras took better shots than this one. I am an amateur photographer with a nice mirrorless and high end lenses, so my iPhone’s camera is not my main one. Thank you for your response.I recently migrated from the iPhone 12 to the iPhone 15 Pro (not Max). You must go with wide open aperture and very high ISO. Even great lighting is horrible, and flash is prohibited for good reasons. So why does anyone need batch processing for 50 images? One of the hardest shoots is indoor rodeo. Seven may be a good number to try at one time, if you want limited batch processing. Note above in #2 the settings before you go to Topaz or see my BobPeterson response below. The best way to work with any of the Topaz products or even PS is to “round trip” under LRC Edit (right click on image) for images individually, select your plug-in. ![]() Email me and I will try to get you in to the Zoom or at least give you my speaking notes afterwards. ![]() I have this month a Zoom presentation to two camera clubs and a tabletop coming up. The file size created has become a concern of mine.Ĭhadp, workflow process is critical. This is also true of Topaz Sharpen AI v4.0.2įollowing because I haven’t decided on the best workflow for Lightroom classic with Topaz denoise AI as plug in. ![]() I do know that my Topaz DeNoise AI v3.5.0 will accept, and batch process the latest Canon CR3 files w/o prior processing. Yes, I know that step one does not apply. This is why they added batch file processing. Total savings for 52 files is 14GB or 45%.īefore you ask, why not go directly to DeNoise from Collections? I love “round tripping”, but it cannot handle too many files and interface with LRC. Note, while DeNoise allows you to select save as “original” format, it returns the process imaged as DNG. Sample file=64MBģ.ěatch Process creating a new sub-folder with processed files from DeNoise. Why? You lose the ability to perform the functions after changing software. Initial adjustments to images (Profile, WB, Detail\sharping=0 and Lens Correction Profile active). Selected Raw (Nikon NEF) images imported into Lightroom Classic (LRC) (as is). While all images are not the same size, in the case above 52 images (steps 2-4) would take up 31GB.ġ. The completed image is then exported in a JPG with a size of 4 to 6MB in itself. This is before LRC Collection “normal” processing. Using Steps 2-4, the image has a 596MB footprint. Sample file=260MBĤ.ěatch Process creating a new sub-folder with processed files. Sample file=76MBģ.Ğxport all images to TIFF (Compression=None, Color Space=ProPhoto RGB, Bit Depth=16 bits/component) folder. Selected Raw (Nikon NEF) images and convert to Adobe DNG via Lightroom Classic (LRC) import. Problem, current process is taking up to much real estate (disk space – yes, I have multiple TB drives).ġ. Mission – batch process numerous images via Topaz DeNoise. Take a minute and read the “standard workflow” and then suggested changes. It could be I am missing the obvious or lack of intelligence but humor me. I about to make a presentation to several groups and have discovered a flaw in my processing. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |