Jump to content

Search the Community

Showing results for tags 'batch job'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Affinity Support Forums
    • News and Information
    • Affinity Support & Questions
    • Feature Requests & Feedback
    • Bugs in Affinity Designer & Affinity Photo
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Affinity Beta Software Forums
    • Affinity Designer Beta Forums
    • Affinity Photo Beta Forums
    • Affinity Publisher Beta Forums

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 13 results

  1. Hi, I'm finally preparing to move away from Aperture, which I still use for its DAM, which remains by far the best, as far as I can see. Sigh. I have several thousand old tiff files, that are unsupported in 64bit (you can test this by starting up in 64bit mode on you Mac). Happily, whilst AFP 1.6.7 choked and crashed horribly trying to batch convert these old .tif files to modern versions, via New Batch Job, AFP 1.7beta cruises through them with much appreciated speed and solidity. So far I have made a >2,000 batch conversion. Problem/Question: Obviously the Batch Job is producing a new Tiff LZW file, which has a new date. Is there any way within AFP that I can set the date to the same as the original file (I can't find anything) or does anyone have any suggestions how I can keep the original file date? I suppose it could be done in the Finder via Applescript, but this is beyond my capabilities. Seems like this is something that could be desirable for quite a few people.
  2. I have selected adobe 1998 as the colorspace in my SonyRX10M4 which is also set to give me raw data .ARW files. When I import them as a batch job to Affinity for processing into .tif files and then save them back to the original folder the colorspace changes to the, less desirable, sRGB 1996 colorspace. I can't find any way of making sure that the colorspace I chose in my camera remains the same the saved .tif file after Affinity has processed it. HELP
  3. I'm very new to Affinity Photo so am getting to know where it really shines and where it falls short. By no means was I adept at Photoshop, but I found it essential for recording Actions. Unfortunately I've run into some issues using Affinity Photo's Macros in Batch jobs. The main one being that if I have a folder full of images that are in different aspect ratios (3:2, 4:3) it seems I am unable to record a Macro that resizes to a specific width or height ONLY. When I record a Macro and resize a 4:3 file to say 800px wide, with the size locked the height of course becomes 600px. If I run that Macro as a Batch on the folder of mixed aspect ratio images, the images that are in 3:2 ratio are resized to 800px x 600px, so they're badly distorted. So the Macro records the dimensions of BOTH edges when the resizing takes place, rather than only the edge you actually edit (as is the case in Photoshop). Is there an obvious solution to this that I am missing?
  4. I'm having a problem with Photo adding a white border when I batch-process converting Affinity files to JPG. This doesn't happen when I export individual files using the file menu. Am I missing a setting in the batch job dialogue that would stop this happening?
  5. The ability to drag & drop folder in the batch window. This will speed up the work.
  6. Hello Many thanks for developing so complex yet affordable editor. I am facing strange behavior of batch processing. I watned process 1300 timelapse shots (JPEGs) for preliminary video check. No big science, just small contrast adjustment and saving as resized JPEG. I recorded a macro (curves + merging layers). I set a batch job - macro, saving as JPEG resized to width 640. I selected all 1300 files and ran the job. Everything went fine. But I forgot to uncheck saving as Affinity format. So I deleted all files and set a job again with the same setting except saving in Affinity format - just JPEG. I was loking forward much faster processing. But it surprisingly took more time. In addition I found that only roughly a half of shots were processed. I ran series of tests but result was always the same - smooth and complete processing if Affinity format was also selected, slow and incomplete processing if only JPEG was selected (except when I selected only 500 shots - then all shots were processed but processing was also slow). I found following: Batch job with Affinity format - processor load 100% continously - disk load 100% continously - memory load - nothing noticeable - files list displays processing progress (green circle arrows) Batch job only JPEG - processor load 100% but there is dropdown to 0 every aprox. 15 seconds - disk load 0%, rises to aprox. 15% when processor is down. Files are written, probably 8 x 2 files at the beginning, 8 x 1 file later, individual files at the end. - memory load rises to full memory size, then drops a little bit and rases again. At that moment processor goes down except 1 thread, memory is very slowly released but no file is saved. - Affinity looks like frozen, files list is displayed but no progress. I made also test withour resizing, I decreased reserved memory, of course I switched Affinity off and on and I also restarted a computer but behavior was always the same. Finaly I tried job which only saved JPEGs to other folder without mocro or resizing. Result was the same just memory was not used to full size. The same test with afphoto format was successful. I have version Regards, Tomas
  7. I am new to Affinity. I am running the trial at the moment but I am liking it and will almost certainly but it when the trial ends. However, there are a few work flows which I have not managed to get as smooth as I like. One example is resizing in batch jobs. Is there anyway to save commonly used settings such as file type, size, and quality? E.g. so I could quickly resize a batch to jpg, 900x900, at 90%. I see the macros but, as far as I can figure out, they don't do this job.
  8. When I apply the Initial Fix Macro in the Batch Job command window, leaving the 'Save as AFPhoto' box ticked, and the Sources are either an afphoto or raw formatted file, the EXIF data is stripped from the saved afphoto formatted file. If I apply the Initial Fix Macro from within the editor and then use the Batch Job command with just the 'Save as AFPhoto' box ticked and no macros applied the EXIF data is retained
  9. Hi guys, I'm having problems batch processing a bunch of my raw files from my Panasonic Lumix GH4 camera to tiff or any other format. The problem is that the batch conversion process makes my raw file look different than if I open each file up directly in Affinity photo. When I open it in Affinity Photo directly, it will apply a lens correction and the colors look correct to the camera jpeg image (which was taken with the raw). I've attached the original raw file as reference and a screen shot of what direct and batch conversion looks like. Please excuse the underexposed image, as I'm taking bracketed photos. Thanks. P1070096.RW2
  10. Windows version when in Batch Job, does not show the Macro Library or allow macros to be accessed. This is an essential part of image processing for me and, I imagine, many others too. I suspect it is available to Mac users, however.
  11. I'd like to have an option for not to enlarge photos over 100% in batch job when I specify W or H size. I use batch job for resizing photos for web and I want to resize only for big ones, not enlarge smaller ones to reach W or H size.
  12. I've been waiting to buy just for this one feature... I created a macro to auto adjust white balance, color, contrast and levels. Saved it to the library. Opened the New Batch job. In the panel, I selected all the images (64 of them) into the left panel. It was populated and showed the image thumbs and file names. I left the save to location as original so the new files would overwrite the old ones. Changed the save as file type to jpg and made sure the sizing was empty and the A box check-marked so that the size would not change. Selected and added my macro from the list to the box on the left. At no time during that process or at the end, did the OK button light up and become active. I watched the video and the OK button was lit up the whole time. What am I missing in the process? I did reboot after installing the software. I've also tested the macro and it does work. Just the Batch - which was the major reason for the purpose at this point that isn't working. I'm running a year old MacBookPro with a Core i7 and Sierra loaded. Thanks Chimper