Search the Community

I cannot put an inside outline on a layer that a topaz plugin has been applied to. Doesn't matter if its photo, denoise or sharpen ai. Please see attached files. bug report on layer effects and topaz plugins.afphoto computer info.txt

Out of curiosity, I've dug out Version 3 of Knoll Light Factory, that was originally supplied with a Serif Photoplus bundle. Although it's installed, Affinity Photo doesn't recognise the plugin. Does anyone know if it's compatible with AP, and if so, how did you get it to work? (All my other plugins Like Nik Collection and Topaz Labs work fine) Thanks

When is AFFINITY going to allow plugins to be made for their software? I would really like to use HOT DOOR CADTOOLS. Its an amazing plugin. I recently asked them if they intend on making a DESIGNER version. But they said AFFINITY doesn't allow this? This is odd, these other companies can help you grow and give us users the specific needs they require. This goes for PHOTO as well. AFFINITY your software is great, but it could be even more amazing with tons of companies supporting it. Please open the doors to these developers. If you don't believe me see how BLENDER had risen to the top of the 3D with completely open source coding. The addons for this software are amazing, making great software even better and one of the best communities for software ever. Just my thoughts Gary

Hey All, I am trying to apply an effect from the eye candy plug in to a layer in my project. The plug in opens perfectly, I can see a preview of what the effect is doing, however when I want to apply the effect the Affinity Photo crashes and I have to restart the program.\ Luckily, I haven't lost any progress, because i saved before using eye candy. However, I really need to apply the effect for this project, so I hope that anyone can help me solving this issue. Thanks in advance and if more information is needed I will be happy to provide it.

I don't know if this should be here or in Feature Requests, so by all means move it to whichever is correct. In any case, I was wondering if there were any plans to add support for plugins in Affinity Designer (as has been done in Photo). If so, will you focus on existing Adobe Illustrator plugins or on plugins designed for Designer? I also have a question concerning the nature of plugin support (both as it is now and in the future), which is why I elected to post this under "Questions" rather than requests. Are there (or will there someday be) plugins designed for Affinity, or is the feature meant specifically for supporting Adobe's plugins? Is it possible to create plugins specifically for use in Affinity Photo?

Oppo Reno 3 Pro + Affinity Photo. Silesian Park, Chorzow City, Poland.

Multiversum and Multiversum 2 Concept art, Affinity and Filter Forge.

Affinity Photo and Filter Forge

Affinty and Filter Forge

Affinity Photo + Filter Forge.

My hobby after my Job. Affinity Photo + Filter Forge.

Distortion pattern. Affinity Photo + Filter Forge. My hoobby after my job.

Diffraction Dream variation no 5, Affinity Photo + Filter Forge.

Software: Affinity Photo and Filter Forge.

Hi, can somebody help please. In my Filter/Plugins list I usually see just my Topaz Labs plugins but in the last week or so I can now see all sorts of other plugins which were not there before (see screenshots - one with an image loaded and the other without). I cannot find out where they have come from and the only apps that has been updated recently don't seem to have filters with those names. Also, when I try to use them either (a) nothing happens or more usually (b) Affinity Photo crashes. I've checked the FAQs for this subject but apologies if I've missed something. All help gratefully received. Thanks, Simon

Installed Release Version 1.7.2. of AP today. Afterwards configuration of Portrait Pro 18 as plugin. Plugin did show up then under Filter --> Plugins -->"PortraitPro..." Pixel layer containing Picture with a face was marked in Photo Persona. After clicking "Portrait Pro" AP hangs and must be killed by task manager. Task manager did not show a process in that state where Portrait Pro could be assumed behind. Same happened after configuring Pro Body 2. What I should mention is that all NIK Filters are working. As various users in AP forums give different experiences with the plugin interface, could you please inform if this is an acknowledged error or what state that topic has inside Serif meanwhile. Is there an official howto (besides that of 2016) available about the configuratio of that interface? Thanks in advance.

Hi, Is there any information on developing plugins to create effects and export other file formats from Affinity Photo?

Has anone gotten NIK Photoshop plugins to work with Affinity? I've been trying to get SilverEffects to work but it won't even come up in the filter/plugins window. Help Please!

There is a difference in the way Affinity Photo 1.10.0 and Affinity Photo 1.10.0.251 correctly or incorrectly handle some Photoshop plugins. 1. In release 1.10.0, all of the newer Topaz Labs plugins (AI and Topaz Studio 2) fail, giving “processing error” messages and/or do not recognize existing presets. They all run correctly in 1.10.0.251. An old Topaz Labs plugin, Topaz ReMask, runs correctly in both. 2. Exposure X6 does not start in 1.10.0. I know this plugin is not officially supported but it has run in all of the recent beta releases of Affinity Photo, and continues to run correctly in 1.10.0.251. 3. DxO Nik Collection 4: Silver Efex Pro and Viveza — the only two apps in the Nik Collection significantly changed in this recent release (updated several days ago). In 1.10.0 the two plugins are running correctly. In 1.10.0.251 beta, the interfaces are not rendered correctly, missing some buttons. My system: macOS 11.5.

I have run tests with the Flaming Pear plugins: Super Blade Pro, Flood, Glitterato, Lunar Cell and Solar Cell. Although they do not work correctly right out of the box, all but one of these Flaming Pear Plugins can be run successfully in the Windows version of Affinity Photo 1.5.0.45 with a workaround. 1. When run within Affinity Photo, the preview window for Flaming Pear plugins splits the image into irregular segments, making it useless for assessment of the way the rendering will look when sent back to AF. However, the preview can be made to render properly if the active layer in AF is selected with the Retangular Marquee Tool before calling the plugin. This works for Flood, Glitterato, Lunar Cell and Solar Cell because they are designed as global applications for a layer. However, Super Blade Pro is usually applied to a local selection; thus you're stuck with a hit-and-miss approach to finding your desired plugin setting for that app. 2. Each Flaming Pear plugin comes with a library of presets (in a subfolder for the preset) which can be randomized in the plugin control panel. You may have to manually point the plugin to the subfolder when this is first run.

Wondering if the Eye Candy plugin works with this latest beta release? Thanks

Moved to Photo Beta Mac Forum

I've been following the forums for a while now since I've decided to switch from the "A" suite and, of all the features requested by users, the most are support for a given file format. Also some users have been heavily requesting for an API they could use to automate stuff (or build stuff - some ideas also came to my mind while writing this) and I think these could be handled with a little bit more of effort in building an API. Since most programming languages are object-oriented I'm also thinking in such terms while I write, however I'm not being specific on language. I believe two kinds of plugins could be allowed: SCRIPTS, which would only help in automating repetitive tasks (think about closing a document for printing) and mostly would only manipulate the document without any sort of argument, and PLUGINS, which would be developed on a chosen platform (I'm pretty sure the Affinity suite relies on .NET) and would enable usage of every feature the platform has to offer. This dual approach is adopted by apps such as ZWCAD and could be great for different uses but it is not a mandatory thing. As for the API itself, the idea would be to enable means to programmatically: access a document (either by creating a new one or retrieving one currently open), layout the document (creating slices on AD or new pages on AP, for example), create, retrieve, modify and/or objects in the document (create shapes, change attributes like colour, add text, etc.), request users to select objects or a point on the document (to ask the user where action will take place). Basically that is allowing anything on an app to be done programatically (yes, with the right script, one could simply automate a complete complex drawing, I'm not asking why would you). I'm thinking of basic object-oriented programming here: // in some pseudo language doc = new document rect = new rectangle object set brush in rect to X add rect to doc ... I'm also well aware the amount of effort and code required to implement this API so I'm not expecting this to be available tomorrow (or in the next version) but I think we'd have to start gathering ideas about this somewhere. Here are some examples of what I would expect that could be achieved with this API: import/export to X file format (PLUGIN): triggered by selecting a file in a recognised format, it would (1) read from a file and create a document and the objects in it using the API representing the contents of the file or (2) traverse a document (or a slice of it in AD) and write it to a file in the chosen format, QR code (PLUGIN): it would open a dialog for the user to enter the info on the QR code (format version, size, tint, text, etc.) and create a group of rectangle objects based on that info. After that, it is just a series or rectangles and does not depend on the plugin (of course this approach does not allow the QR code to be edited, or even its info to be viewed, but I'm sure some other approaches can be taken - like storing arbitrary metadata on objects and groupings and even restricting some of these to be undone), create a draft in PDF format (SCRIPT): this would just add the word "DRAFT" in the background of every page (in a publication - to the original or a copy of the document that exists only in memory), trigger the export to PDF function (it is already embedded on the app, so why not make it accessible) and then remove the "DRAFT" word from every page (since it is not meant to be part of the final document). This could also be done as a PLUGIN if one would like to specify the tag text and colour. Perhaps the biggest concert of Serif in providing us an API is related to security/privacy of its users and that's a noble reason for not releasing an API yet. Of course PLUGINS could be more dangerous than SCRIPTS from this point of view since they have a broader access to the native API of the platform (from enumerating/reading/writing files arbitrarily, to spanning threads, to sending data over the internet) but I've never seen anyone complaining about those issues on Photoshop or any other app that enable the use of plugins. You choose to use plugins from a reliable source and Serif could even be a curator for one of those reliable sources, but nothing mandatory. Another solution to this (and this would take a more considerable amount of time) would be Serif to create a full development platform with each and every API exposed (file access, document access, etc.) in order to minimise the existance of malicious plugins (and someone will always find a way to bypass it, trust me) and restrict programming languages to the one Serif itself choses (I'm not really fond of it but it seems the most claimed in the forums is Javascript). I could live with that with the right API. I'm not in anyway affiliated with Serif and I don't know if they have already decided on any of the issues I raised and my intent here is not to discuss the exact implementation the API will take (thou it could certainly be fun) but to gather opinions on it, specially on whether the API should use an open platform or a more strict one to prevent malicious extensions, and to gather things people would be interested in doing with the API and are not sure I covered above. I would also like if this space were to be used by Serif to talk to us about how they view the issue of the API and how/when they are planning to handle it and to it discuss with us in order to create something really useful for everyone.

What is the latest status on 3rd party Photoshop compatible Plugins & Affinity Photo? Is there a list?

Hello, I'm still learning AP and trying to get used to all it can do ... it'll be a long time before I can say I'm somewhat comfortable. But one of the software programs I use just came out with plug in capability for AP along with a couple of other photo programs. I am trialing it for the moment and opened AP, did some adjustments in it and then opened the plug in program. I noticed that unless I merged the adjustments that the plug in sees the non edited photo. I tried attaching the adjustments under the background layer (I think this is called being a child adjustment) but it still only sees the non edited photo. I learning to use AP for layer work and having the plug in might be nice to use at times. Is this the way a plugin works in Photo? Am I missing something? Thanks!