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

Recommended Posts

I have been using Filter > Distort > Equations to modify text onto a sine curve. First I rasterize the text, then apply Filter > Distort > Equations with the following formulae:

x=x
y=
y+(h*a/2)*(b*sin(360*x/w/c)+(1-b)*cos(360*x/w/c))

This filter works as intended as a one-off, and whilst recording the macro, but If I then export the macro, and try to apply the macro later nothing happens. The history panel shows that it has been applied, but the image is unchanged. This happens whether I load the macro as a single macro, or if I add it to a library and load it from there.

Text onto sine-cosine curve.afmacro

Anyone any ideas?

John

Windows 10, Affinity Photo 1.10.5 Designer 1.10.5 and Publisher 1.10.5 (mainly Photo), now ex-Adobe CC

CPU: AMD A6-3670. RAM: 16 GB DDR3 @ 666MHz, Graphics: 2047MB NVIDIA GeForce GT 630

Link to comment
Share on other sites

Hi John

You don't say what values you're using for parameters A, B and C when you run this manually, but when I import your macro, I find A=0.257 and B=C=0.000 – see the screenshot below.

That means that your equation is trying to divide two of your inner bracket terms by C=0 which, mathematically speaking, is just wrong.  It should throw an error.  I'm not sure exactly how AP is managing this error, but the result is that it seems your your equation is being evaluated to "y=y".

The moment you change C to anything non-zero, and then re-apply your macro, the targeted layer is distorted.  So it seems the problem is perhaps in the recording of the macro, that it's somehow capturing A, but leaving B and C set to zero.  I've just done a quick test and it did seem to capture each of the three parameters, so I can't offer an explanation for your recording problem.

 

2018-01-02_14-09-55.png

—— Gary ——

Photo/Designer/Publisher: Affinity Store, v2.4.n release

Mac mini (M1, 2020), 16GB/2TB, macOS Ventura 13.4.1(c) • MacBook Pro (Intel), macOS Ventura • Windows 10 via VMware Fusion • iOS: current release

Link to comment
Share on other sites

Thanks Gary. I had assumed when I set this up that the B and C parameters were one (not zero). These were, I thought,  the default values. I will try it out when I get back to my desktop.

 

John

Windows 10, Affinity Photo 1.10.5 Designer 1.10.5 and Publisher 1.10.5 (mainly Photo), now ex-Adobe CC

CPU: AMD A6-3670. RAM: 16 GB DDR3 @ 666MHz, Graphics: 2047MB NVIDIA GeForce GT 630

Link to comment
Share on other sites

I have re-created the macro from scratch, and after recording it, I checked the parameters, and both B and C were one. I then closed the test file and cleared the macro. I then reloaded a file, and imported the macro. Looking at Edit Parameters  showed that both B and C were zero! Both before and after, the A parameter had retained its value of approximately 0.25. Re-setting B and C to one and running the macro gave the correct result.

This looks like a bug to me. Could I ask the moderators if they would please transfer this thread to Bug Reports.

John

Windows 10, Affinity Photo 1.10.5 Designer 1.10.5 and Publisher 1.10.5 (mainly Photo), now ex-Adobe CC

CPU: AMD A6-3670. RAM: 16 GB DDR3 @ 666MHz, Graphics: 2047MB NVIDIA GeForce GT 630

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.