Search the Community

Hello team, I miss in Publisher the possibility of an overprint preview, as well as the possibility to set individual colors or objects to "overprint" or "cut out" (hope this is the right term, maybe "omit" is better?). I did not find a satisfying answer in the forum. Are these features available and I just can't find them? Regards, Puck

I’ve had a bit of an experiment with it on curves and shapes but can’t seem to get it to make a difference whether it is on or off? (I did a bit of searching in the forums but started to get frustrated with how the search works.)

Hello, I can’t enter anything above 50 px in the radius input box. The only way to successfully achieve a higher value is to grab an object’s handle (be it corner, or side, doesn’t really matter) and drag it left to decrease the value and right to increase it. Unfortunately there’s no cursor on my screenshot but that’s how I did it. Immediately after increasing the value via the input it resets to 50. The same for moving the pop-up slider. cheers Matt

I have a bunch of former strokes I expanded - used the new divide function to clear overlapping former strokes and then selected all and hit "add" to merge back as one piece. The last step froze the app - this is not just a 1.9 beta issue, it's happened with all versions at times... I had to force quit the beta and reopen it. When it asked me if I wanted to restore the previous file, it brought up another design I was playing around with prior to this current one I got frozen with. That recovered file was an totally unsaved version - the one that froze on me was an existing file with a name saved prior. When I went to the open recent files, and selected my file that had frozen, it then offered to use the restored version... im glad it did, but I'm curious why it didn't offer both files to be restored since both were open when it froze.

I'm happy with the new release of the Affinity suite but as always ... I'm a beta cycle man, So I feel such boring and would like to know when is next Beta session planed and what's targeted ! Thanks.

Hi Affinity Team, I was so excited to see Affinity products on Apple's WWDC 2020 Platforms State of the Union screens multiple times. Congratulations to the Team! 1. PROBLEM At 14:05 we can see how Affinity Photo works seamlessly on macOS 11, however in reality the Toolbar doesn't work at all. We can not use any Toolbar's items and we need to use the shortcuts or the quick help to jump from one Persona to another. I know, I know... it's early macOS Beta with a totally new Toolbar functionalities. 2. QUESTION Yet I would like to know when Affinity start the new Beta period for those folks who are brave enough to test and use Affinity products on macOS 11 Beta system on a daily basis. I would be glad if I could sign up to this opening Beta program because I desperately need to access to the Toolbar. Please, let me know how it is possible. Thank you! Looking forward to your respond and thanks again! Best regards, Robert App Developer and UI/UX Designer 3. UPDATE When I put Affinity in Full screen, suddenly all of the toolbar items work again. Hurray!

After I installed 3. update for all three programs, my apps are no longer linked together. Before, when I opened my Publisher file, the other two would open as well and would show on the top tool bar so I could jump between the three programs. Now, they are no longer linked and I have to open all three apps individually, which will make sharing and working on files between the three programs so much more difficult. Does anyone know why or have a solution to the problem? Was I on a beta testing or something because I read a question where someone "wished" they could do something like this, but I have been doing this for at least a year now... I want it back!!!!!

I was experimenting with batch converting arw to jpg on about 10 files with different parameters (with or without "convert to sRGB macro, pixel format default, rgb, cmyk, embedded sRGB profile). Anyway, I decided to output around 118 images that I'd already successfully output with sRGB macro/embedded profile, and I think rgb pixel format (maybe left at default). Importing in the same dir where I recently deleted a 10-file batch. parallel checked. The batch job spun up and got to "saving" on the first 24 images but never made it past that. CPU hung out high for about how long it would take to save them then went to idle but the gui still says "saving". I was writing to a NVMe SSD. The drive is not full. under task manager Affinity photo beta is using 29GB (I have 256GB) and barely any (less than 1/2%) of CPU (712 threads). There's another process - crashpad_handler.exe at 0% cpu (6 threads). Been this way for maybe 20 minutes now as I waited, then started writing this. Nothing in event logs. From looking at the thread handles in Resource Monitor it looks like maybe it's trying to write crash info. I attached a txt file with the copy/paste of the handles from Affinity Photo and Crash Handler. System Info: Win 10 Pro 1909 build 18363.836, 256 GB RAM, 2x EVGA RTX 2080 Super GPU, AMD Ryzen Threadripper 3960X 24-Core (SMT off), ASRock TRX40 Creator mobo Affinity_beta_CPU_Handle_Dump.txt ---EDIT--- As a followup, I can't even reproduce what I did to successfully output images in batch. I can do little batches now, but haven't been able to reproduce the 118 image batch - I keep hanging. Have tried all sorts of color profiles and combos of clicking JPG/macro options. have also tried DNG/ARW. Haven't reset my pc yet but that's next. Also tried to do batch in non-beta and had the same hang. --EDIT-- rebooted and still cannot find settings that successfully generate a 118 image batch (except turning off parallel processing). The first one I did worked in parallel (accidentally left box checked to generate affinity format photos and had to delete them) but I tried that too and it didn't work. -EDIT- I did some more tests and things work fine with parallel processing up to 20 images, break at 22. When it breaks the CPUs stop running sooner than when it works (with message saving jpeg... and spinning wheel). I have no idea why I was able to make it work for a whole run my first time, but I wish I could repeat that luck. I know I included the sRGB macro, which I don't need, and I know I ran it from the developer persona, and I know I accidentally created the affinity-format files too, and I was working on a sRGB workflow, but I've tried all the permutations of that my patience can handle, and I haven't been able to find that magic that makes me get the whole batch done with all 24 cores. Which means I'm stuck with one. Unless I can set processor affinity to 20.. maybe I can do that.. And in case you're wondering I regularly peg out all my cores (and GPU cores) on other things, so I don't have some hidden system instability. incidentally it would be nice if the batch settings (output dir/source dir/output type checkboxes/file type options) were persistent instead of resetting to default every time. And I'd love a ctrl-shortcut for batch or at least an alt-F-something shortcut. let me know if I can help debug. also a CLI for batch like darktable-cli would be super-amazing. I'd buy you a case of beer for that Oh how I miss having beers with friends...

I'm not sure if this is a bug or my inability to understand how layers work with AD. I noticed that when I move a line it moves to another layer. It doesn't matter if the layer is locked or not. I notice this behavior when trying to connect paths as well. I haven't totally tested this yet but...the lines that I am having problems with are ones that were copied from one layer and paste into another. It's as if it remembers the layer is originally came from. The problem goes away if I paste the lines into a different drawing or file. This is happening in beta 6 and 7. lineMovestoDifferentLayer.mov

See graphic below. Beta 1.8.4 fails to install on a Windows 7 machine which has been running Afinity software without a hitch lmv968@yahoo.com

Image created with 2 5-image HDR merge, exported as 16bit tiffs, and then combined as a vertical pano Have not been able to save to Photos Export 16bit, RGB & 8bit RGB Tif and jpeg file size calculated Share Botton Crash Am able to export 16bit RGB tiff to ‘my iPad’ without issue RPReplay_Final1563335210.mp4

In the latest Affinity Designer Windows Customer Beta - 1.8.1.610, Click to create a new node on the curve dose not work when using Wacom pen (I have to right click to create a node). It works with mouse. Windows 10 Wacom Intuos Pro Medium Desktop 2020.03.12 - 15.48.38.01-1.mp4 Regards,

I have already noticed the problem with version 1.8.0x and communicated that the document size could not be changed afterwards, unless you change the DPI value minimally and the desired length and width (dimensions) of the document is changed!

Unfortunately the line / curve ends are still cut off. I added a AD file with document history, hope you can reproduce the problem! S_Curve_expand_stroke.afdesign

I just starting using the iPad version of Affinity and I can't tell how you install betas. Is it done through the MAS somehow? Is there a current beta on iPad?

Point 1. I decided to try to put a pdf together in AP Beta. I successfully created a pdf. The following day I accidentally deleted it, which was not really a big deal as I needed to update many of the images (.jpg). I was surprised that when I created a brand new pdf with the updated images, Publisher placed the old images! How is this possible? Point 2. Also, I can see no way to 'refresh' images. Point 3. All my images are linked, but do not update.

Hi, Am using AP Beta 1.8.0.486 & found James' great video on adding in lens profiles. I followed it to add in my Sigma 18-300mm lens which was included in the profile. However, when opening a RAW file, there is no lens profile. Here's a screenshot showing the inclusion of the profile file, the lens itself & lens profile distortion box revealing none. Any ideas as to what I need to do? Thanks so much, Julie.

Hi! There's a little glitch with the Blur Brush Tool in Photo beta 150 RC2: It does its job, but the live preview becomes transparent. But not always! I guess it depends on the type of file ... maybe Metal on.

Hi, Each time I open an older file or one made with the stable release, instead of showing its name, the file is unamed and I need to go back to the original file to copy its name. I'd rather have "_Beta" append to the name or something else (since the apps keep the last folder path, and don't use the current file path, if I open a file by double-click, it's not always possible to overwrite the original file with a simple ctrl+S shortcut).

all was fine from the beginning i installed publisher. then i updated to the last beta version and everything turned out fine, too! i was working on some projects with no problem. but since some days publisher crashes very often when i want to start the app. i was guessing a fontcache problem because every time the program was starting i saw the welcome window saying it's loading the fonts. but short time after that the app was crashing. i deleted the cache from time to time and sometimes it helped... but it didn't solve the problem at the end. 2 times i was putting away the prefs to start fresh- guess what! no deal! one week ago i updated to WIN10 1903. don't know whether this has anything to do with it. i put the last DMP files to this notice. c81cac41-9002-43ce-94f7-d5e591517e88-dump.dmp 46331f14-fe33-4de0-a512-6fae575f98a5.dmp

Hi there, I'm using Affinity Publisher 1.7.1.404 and wanted to open a .afpub-file lastly edited with Affinity Publisher Public Beta 1.7.0.337. Unfortunately, Publisher keeps loading the file and eventually crashes without error notification. Opening with the beta isn't an option since the beta has expired. The file contains text, embedded and linked images. It would be great, if I was able to access the file, since there is some data in it, I would not want to recreate in the retail version. Of course, I know, that working with sensitive or important data in betas is at one's own risk. I just wanted to ask, if there is some knowledge regarding opening beta files in the retail version or getting the data in some other way. Thanks in advance, Valentin Edit: I was able to open the file with all its references and embedded contents with the current Customer Beta of Publisher version 1.7.2.442. I don't know what caused the retail version to crash since it correctly opened another beta-file (less complex and on another computer). I guess, basically beta-files and retail-files are compatible, but some reference or adjustment made the retail version crash. Whatever, for me, personally, this issue has been solved, before this post was approved by a moderator. Nevertheless, I wanted to post the workaround in here for anyone having similar problems with the retail version.

I have a newsletter that I created with the beta version of Publisher which I would like to remake using the current non-beta release. The newsletter has a lot of styles, formatting and settings that would like to replicate in the new document but I worry that anything I bring over from the old document – imported styles, copy/pasted layers, etc. – could bring problems over to the nice fresh non-beta document and somehow break it. What is okay to do and what should I not do? At worst case, if I only have the beta document open and don’t copy anything from it – just to make it easier to note down various settings – could the new non-beta document be adversely affected in any way? Or should I ‘quarantine’ my old beta documents and never open them while I am working on non-beta documents?

Dear Serif and the Affinity Photo dev team... THANK YOU SO MUCH! I fired up the Customer Beta that I keep installed along side my regular release of AP. Imagine my surprise when I checked the export options and saw .TGA as an export option! I'll be running around work tomorrow like a lunatic informing every single artist about this! Additionally, There's going to be more than a few of our tech supervisors that are going to be excited as well. I'm hoping studio management gets around to upgrading to Affinity Photo before the end of the week!

Had consistent crashes with Publisher 1.7.1 official release, so I downloaded and installed this 1.7.2.420 beta build release. Crashing still happens. Crashing occurs when creating new paragraph style within Text Style panel. Purposely did not undock the panels, but left them in their locations; still crashes. Dropping in the system crash report, as well as the document (two graphics, two text frames with text, two text frames with page number fields). One note, this is the same document as was used in the official release. Certainly, the program is bugging out, but perhaps the document itself is the culprit? Running MacOS X Mojave, 10.14.5, iMac (late 2013), 3.2 GHz intel core i5, 32 GB memory, Nvidia GEForce. Affinity Publisher Beta_2019-07-06-114526_iMacUp.crash Bios and Farewells.afpub

Hi, Now I'll admit to being new to AP, coming from PS. But when I go to Liquify Persona, select the tool I want to use, nothing happens. Mac Pro Mid-2012 OS 10.12.6 3.2 GHz Quad-Core Intel Xeon 32 GB 1066 MHz DDR3 ATI Radeon HD 5770 1024 MB Anyone else having this problem? I looked at the video tutorial for help and I'm selecting the correct layer. Thanks! UPDATE: Ok, now it's working! But when I use the freeze tool, it still grabs the area that I don't want to adjust. Is there a fix for this? I attached an image to show what I mean. Thanks again!