Jump to content
You must now use your email address to sign in [click for more info] ×

Recommended Posts

Trying to record Macro to bulk markup images.

 

MacroAssistant says Macro cannot record Art or Frame Text?

 

What am I doing wrong?

 

Screen shot of starting point.

 

Regards.   Sharkey

Screen Shot 2017-07-31 at 12.01.15.png

 

ps:- only a test image.

MacPro (late 2013), 24Gb Ram, D300GPU, Eizo 24",1TB Samsung 850 Archive, 2x2Tb Time Machine,X-t2 plus 50-140mm & 18-55mm. AP, FRV & RawFile Converter (Silkypix).

Link to comment
Share on other sites

Er?   Why??

 

It seems to me one of the first uses for the 'macro' process?

 

Not pleased.

 

Thank you.      Sharkey

MacPro (late 2013), 24Gb Ram, D300GPU, Eizo 24",1TB Samsung 850 Archive, 2x2Tb Time Machine,X-t2 plus 50-140mm & 18-55mm. AP, FRV & RawFile Converter (Silkypix).

Link to comment
Share on other sites

OK.

 

If I cannot record a Macro of creating a water mark or signature - How do I use a Macro to put a watermark and/or a signature in bulk??

MacPro (late 2013), 24Gb Ram, D300GPU, Eizo 24",1TB Samsung 850 Archive, 2x2Tb Time Machine,X-t2 plus 50-140mm & 18-55mm. AP, FRV & RawFile Converter (Silkypix).

Link to comment
Share on other sites

I think I have the idea.

 

Create the watermark and the signature on transparent backgrounds and us Macro to add them to any number of images as and when.

 

So - where do I store these creations so that my Macro knows where to find them. Do I need a separate folder somewhere permanent?

 

Regards.   Sharkey

MacPro (late 2013), 24Gb Ram, D300GPU, Eizo 24",1TB Samsung 850 Archive, 2x2Tb Time Machine,X-t2 plus 50-140mm & 18-55mm. AP, FRV & RawFile Converter (Silkypix).

Link to comment
Share on other sites

15 hours ago, Sharkey said:

...........

 

So - where do I store these creations so that my Macro knows where to find them. Do I need a separate folder somewhere permanent?

 

Regards.   Sharkey

I would have thought that doing a File > Place within a macro would simply store the full path name to the file within the macro, so it would not matter what folder the file was in.

But this does not seems to be the case as if I record a macro containing a File > Place command, I can rename the file and the macro still works as expected, even after restarting AP

Interesting...

Maybe the macro stores a copy of the original file within the AP folders somewhere.

Can't be bothered to look for it but maybe someone else will know if this is the case.

To save time I am currently using an automated AI to reply to some posts on this forum. If any of "my" posts are wrong or appear to be total b*ll*cks they are the ones generated by the AI. If correct they were probably mine. I apologise for any mistakes made by my AI - I'm sure it will improve with time.

Link to comment
Share on other sites

  • 1 year later...
On 8/1/2017 at 6:02 AM, carl123 said:

I can rename the file and the macro still works as expected, even after restarting AP

Interesting...

You can delete it and it will still work. O.o 

iMac 27" 2019 Somona 14.3.1, iMac 27" Affinity Designer, Photo & Publisher V1 & V2, Adobe, Inkscape, Vectorstyler, Blender, C4D, Sketchup + more... XP-Pen Artist-22E, - iPad Pro 12.9  
B| (Please refrain from licking the screen while using this forum)

Affinity Help - Affinity Desktop Tutorials - Feedback - FAQ - most asked questions

Link to comment
Share on other sites

30 minutes ago, firstdefence said:

You can delete it and it will still work. O.o 

Which means the macro stores a copy of the placed file, not a file path link to it. To confirm that, I created a simple 1 step "Place file" macro that placed a 1.1 MB jpg file into a document & saved the macro to a macro category I had already created. My macros.propcol file immediately jumped from about 10.1 MB to a bit less than 15 MB, which I suppose means not only is the image stored in the macro itself, it is stored in some form that is not as compressed as the original jpg file.

I think it works like this because storing a file path name (or a Mac alias or the Windows equivalent) would mean that the macro would not be cross-platform compatible (because Macs & Windows don't use the same path name conventions), & of course that the macro would not be sharable even among Mac or Windows users (because there is no guarantee that all of them would have the placed file or have it at the same file path).

That's fine, but what is not is that after I deleted the "Place file" macro, the file size of my macros.propcol file increased to nearly 18 MB! I tried quitting & restarting Affinity Photo to see if that would change anything but it did not. Maybe there is a threshold of some kind that checks for 'orphan' macro stuff & purges that from the macros.propcol file, but if there is not, that means the macros.propcol file could get very large over time, with no way to recover the lost file space other than maybe exporting each category that has had a macro deleted from it, resetting macros, & reimporting the categories.

Before I report this as a bug, I would appreciate it if someone else would test this to make sure I'm not missing something. Ideally, use an image large enough that it would add a noticeable amount to the file size of your macros.propcol file, save it to a macros category that has at least one other macro in it, & then delete that macro.

TIA

All 3 1.10.8, & all 3 V2.4.1 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7
Affinity Photo 
1.10.8; Affinity Designer 1.108; & all 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7

Link to comment
Share on other sites

On 3/25/2019 at 3:13 AM, R C-R said:

That's fine, but what is not is that after I deleted the "Place file" macro, the file size of my macros.propcol file increased to nearly 18 MB!

Anybody else tested this & if so do you see this behavior?

If you don't want to be stuck with an oversized macros.propcol file, you can copy the original & store it somewhere else. After testing, you can quit Affinity Photo & drag the copy back into its original location & replace the oversized version.

EDIT: reported as a bug here.

All 3 1.10.8, & all 3 V2.4.1 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7
Affinity Photo 
1.10.8; Affinity Designer 1.108; & all 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7

Link to comment
Share on other sites

16 hours ago, stewartvp said:

...also when processing images of different sizes use the align functions to put things wher you want. 

That usually doesn't work correctly, since it's highly image dimension and orientation depend and APh doesn't replay recorded transformations in a dynamic doc size independent manner. - I recall that I once (long time ago after buying APh) tested the overall macro capabilities stuff and realized that in it's current state it isn't usable and pretty worthless for such general automation tasks.

☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan
☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.