Massi

It looks like we should open another thread in order to be answered by a person who actually understand the problem here...

I understand your frustration cause I'm probably used to the same workflow as yours, I found really obvious that a auto-clean feature to check was necessary. i.e. When you skin retouching you make tons of quick and precise strokes (mainly in low frequency for me) in order to even the skin tones; so having to click Clean every time is just nuts. It's actually a part of a regular gesture in a retoucher/photographer workflow, I feel like something important is really missing and would be good to have it, it would make a big difference.

Alfred I really have no answers for you, that's what they ask and this topic is not about it. If you have any suggestion regarding the topic you welcome, besides that......

It's working but I've noticed that you need to change these settings anytime again, it doesn't "remind" your last settings...am I wrong?

the stock photography platform I'm working with need min 4mb images

Hi Walt, thanks for the reply. You are right, my settings for jpg export were at 85, so I put it at 100 and now the size has increased. Still I wonder if there is a more accurate way to predict or keep the desired size into a specific range of Mb...in this case I need min 4Mb but I'd also like to avoid having 20Mb files. Working with tons of images would make this non time-consuming, I couldn't imagine do and check the export one by one.. I could easily do that in CaptureOne for example because for any image you can see how much (in Mbs) is going to weight, but it's a longer process since you have to create a new session for any export... Thanks

Good afternoon, I wonder if there is a way to export images (batch export mainly) setting the minimum size of any exported pic. For stock photography I need images that should be 4Mb (jpgs) at least; I'm exporting from retouched Tiffs (generally 3600px X 5000px), setting "export to jpg" as my only custom option, some files are 4+ Mb but most of them are only 2-3Mb.. Thank you in advance

ok thanks I'll try that. Any idea of what parallel processing is meant for anyways and what's the big difference when checked or not?

I have a macro and sometimes (maybe 20% of the times I tried) it's working with one image. Still, working with no macros or less images is not a solution, just another slooooow work around for a well known and crucial issue that's been around for quite some time now. A few months ago I asked for any info about updates and fixes but I had no answer at all. So again, any update to the software, still have 1.6.7

Morning, I can't batch process anymore now, any kind of command lead to the "thinking wheel", the program doesn't respond and I have to force it to shut down. In January I had the same issue, came here and someone said to turn the parallel process off in order to by-pass the bug; it worked and kept it that way because no fix was around. 4 months have gone and this new bug is happening for a few days now, yet no update available and wondering how can I deliver my client this 40+ pics batch without spending my morning to do it one by one... def need an update guys

Hi Walt, thanks for all this info. I guess for my next project I'll try this workflow: RAW to Capture One to Tiffs (8-16bits 300dpi) to .aphoto (converted in APh) to final delivery (Jpgs,etc..). Have a good one!

Meaning that I can keep the levels from the macro only selecting both .aphoto and Tiff in the batch window? If so, I should get rid of the (useless to me) .aphoto files. I also don't get if, in order to have that option, my first file should be a .aphoto file or I can do it from my existing tiffs (export from tiff to a.photo+tiff) after they come from Capture One. I still don't understand what's the benefit on working on .afphoto or .psd files depending on the software you use, when using Tiff is the most looseless versatile option, especially if you work with a retoucher or any other person working with PS. I still have PS for things where APh is not fully reliable for real life productions, where batching/actions/exporting should go smooth and intuitive. Quality wise, is not a good move either. From Capture One you can natively export Tiff and PSD. So just because in AP some operations works better when working on .aphoto file, I should go through another export (let's say from Tiff to .aphoto), losing quality even before retouching skin for example....sorry it just make no sense. It should be simple, and the way it it is just more time consuming and limited.

Ok I guess we both had a misunderstanding on the jpg thing, now I understand what you meant before and why you explained me the compression thing, but anyways, i'm using TiFF, not jpg and didn't want to export in JPG. As you can see on my macro, there's no saving/export command, I just wanted to apply those levels on my Tiffs and just leave it like that in order to continue working on those tiffs one by one for further adjustments/retouch. My point is that I don't understand why after applying the macro with all those levels, the program just decided save in Tiff but flatten, since the only commands on my marcos were to create levels, nothing more. thanks

I use Tiff, but it shouldn't matter really. Why does it actually? Am I not free to keep levels on jpgs? What if I'm working on a graphic layout on top of a Hires jpg and I need to apply it to 10 pics? Kinda non sense don't you think?

Hi Stokerg, sure thing! I attach the macro and also the screenshot with the actions inside. Thanks! 70tees.afmacro