abarkalo
-
Posts
244 -
Joined
-
Last visited
Posts posted by abarkalo
-
-
-
I have tried all the export settings but blend modes are not written to the SVG files. Effects are, however, such as gaussian blur.
Please see the example SVG where blend modes and effects are saved but then try simply exporting to SVG and re-open - blending modes are gone. Please let me know which setting or how to do this since I can't figure out.
-
Every time I save and reopen an Affinity Publisher file, I get the annoying "Open Recovery File" prompt to which I respond "don't open recovery file" and then everything seems to work normally.
If I don't save the document and am asked to save after clicking to close the document, and am presented with a "save changes" dialog then the Open Recovery File prompt won't appear on the next re-open. But if I make changes to the document, then CMD-S save, then that recovery file dialog appears next time - it's really annoying.
I've tried clearing using data, reinstalling Affinity Publisher v2.5 several times, deleting containers -- all the above. But this problem continues. Nothing seems to be apparently wrong with my files or the V2.5 app - it runs smoothly - but this dialog is really not great.
I suspect it's because I tried the V2.5 beta before but then removed it. This is when this crazy behavior started. But I'm only running the non-beta version and there is no beta or its folders on my system.
Alex
-
When previewing Affinity Designer files in Mac OS or in an asset manager the previews are too small, in fact too fuzzy to discern any good detail. I have thousands of Affinity Designer files and this lack of detail in the preview (for instance by pressing spacebar) makes it necessary for me to open the file to see what's there.
Contrast this with an SVG file where there is live drawing of the file in the preview. So what I am doing is converting many of my AD files to SVG (especially logos or simpler files). But SVG is a subset of AD functionality so this is limiting for me.
What I notice that Adobe Illustrator does is save a PDF alongside the file. I realize this takes up more space but it really does help. Is there or can there be an option like this?
-
no I haven't experienced this stall in Photo or Designer as of yet, only Publisher, and only when going to the Export > More section. I just tried opening a super big Photo file in the latest beta and I don't have any stall so far, and did try Export > More was well.
-
I realize I have a big working Publisher document (only 15 pages but a lot of graphics) but when I go to Export and then select More for other export options I very often have a stall that last 30 seconds or so. It's quite annoying. It doesn't seem to happen if I don't click on the More options - although I very often need to go there to change the image downscaling, etc. I've been working with the same document in previous AP versions and this didn't happen before. Perhaps it is related to Mac OS 12 stall bug that was reported, and which AP 1.10.5 beta was created to solve. Not sure but please look into this.
-
actually this has been less of an issue - but actually prefer the quasi full-screen view because I can see the menu bar all the time
-
Before I say anything in Serif Affinity is slow, I need to say that on my MacBook Pro M1, anything Affinity is lighting fast, especially 1.10.4, certainly lightning faster that anything Adobe.
However the full screen toggle (fn-F) is really uncomfortably slow, and sorry for the comparison but in this one single area Photoshop is lightning fast, meaning quite usable in the sense that it doesn't cause lag distraction.
I have written an AppleScript to toggle the window bounds to {1680, 1050} but the window will only resize to {1670, 1040} or something like that. This script is very fast, much faster than the toggle but a little bit of the desktop and the windows behind it peek through - not anything show stopping but not a super clean full screen UI.
-
what do the stock art owners have to do with this? For the most part, the stock art is fine if it opens in Illustrator, and it's grouped nicely and laid out in smaller artboards. Nothing wrong there.
-
this is always a big issue for me. I buy a lot of graphics stock art - objects that are places very closed together, and when opening in AD directly and becomes incredibly tedious to re-group, especially when there is no lasso select tool in AD.
However, one quick work-around: open the file in Illustrator and save as SVG. Then open the SVG in AD - this works for me. The only issue is that are often issues between EPS, AI and SVG files. For instance SVG is the common design language that both AD and AI read with good fidelity. But AI has different shading and coloring that is specifically only to AI.
-
I am on an M1 (not Pro or Max) - will this beta do anything for me?
Also, I just noticed a bug in the beta vs the latest MAS version. Please see attached file. Notice that if you open in the MAS version the SVG file loads perfectly. But notice that if you load in this beta, the ying/yang symbol doesn't render well (border thickness) and the leg of that unspeakable symbol is missing an arm (better that way, but still..)Religious symbols.svg
-
Right now it is painstakingly slow to install LUT folders, especially if you have a lot of them. I have over 100+.
So for each folder containing a LUT theme, I have to
1. go to adjustment layer
2. create new LUT category
3. rename the LUT category (why can't this at least be accomplished when I create)
4. click on import the LUT items
5. go to the LUT folder, open the folder, select all, then click import, then wait up to a minute
6. Repeat all this for the 100 other folders!
Why can't there be a batch method with all the nested LUT folder that I have?
Also, once the LUTs are all installed, why can't I rapidly scroll through the LUTs on an image just like the way I can rapidly scroll through blend modes?
It would really help me, and I'm sure other designers, to have a less painstaking method to install large LUT libraries, and a more rapid creative visualization method to view all the LUT looks?
-
This beta is very fast indeed! Also, I don't know if the GPU speed enhancements directly affect the speed of the inpainting brush but it is much faster now. One of the things that I considered the gold standard in Photoshop was their spot healing brush (inpainting) but now I can say that yours is better on many pictures that I have recently tried, in content-aware mode.
One feature request - and I don't know whether to address here or in the non-beta forums, but will start here is that I would really like the last used settings pertaining to inpainting on current layer or current and below to be remembered. Or better yet to have a preferences setting to choose current and below. This is alway a slight annoyance for me when starting to add layers.
- Nicole Hurst, Chris B and IPv6
-
3
-
On 4/4/2020 at 2:30 AM, DM1 said:
They work fine in photo but you need to set the selection point with your finger. You cannot set it with the Apple Pencil. Something to do with pencil not registering a long press I think.
Yes I am having the same issue on the iPad with the Apple Pencil. You have to make a selection with your finger not the pencil. The inpainting brush works well with the Apple Pencil on the iPad but it is a pain to figure out how to use the Clone Brush Tool with the Apple Pencil. Is this is bug or am I not doing something correctly?
-
-
Very often I am unable to subtract the top layer and punch a hole in the bottom layer. 95% of the time it works but a few times it doesn't. Please see the attached AD file - trying to carve out a simple "A" - can you please tell me what is going on or if this is a bug? I am using AD on Mac OS 11.6, AD ver 1.10.1. I am on an M1 Mac.
-
1 hour ago, walt.farrell said:
Generally the beta should be used only for testing, not production work. And when a major release is being tested (e.g testing 1.9 when the retail is 1.8) then usually the files will not be backward compatible (1.8 cannot open 1.9 files).
However, when testing a minor release (e.g., 1.10.1 when the retail is 1.10.0) the files should be compatible, especially when Serif knows the changes are small. And in that case they may change the recommendation and say it's ok to use it for production.
yes I know all that and to be honest there has been only one beta that did crash a few times and that was the earliest beta version of Publisher. Most betas have been very stable, even those "legally" marked as "don't use for production work." This says a lot about the quality of your releases. I am much happier with the improved performance and new features of the betas. But my complaint here isn't about that, but just with the requirement to have both the store and beta version to run alongside each other. I really want to have just the beta installed and be able to register that version. Otherwise, and to repeat, all the benefit I obtain from the beta is outweighed by my system mess. So, for the meanwhile, if minor releases or bug fixes will be soon updated for the store versions then I guess I'm just happy to wait for the store fixes.
-
I love Affinity so much but, honestly, the Affinity beta system is a real negative for me. The requirement to have the store bought version to run alongside the beta versions leaves my Mac confused as to which software to use. And in many of my creative workflows I cannot select the beta version since the non-beta version has been selected. This leads to a lot of file confusion. I have tried workarounds for the past few years but there aren't any. I use a lot of software in which the beta version just needs a registered license to run on its own, so really why can't this be here??? Also, I've been very confused by messages that tell me to use the beta in preference to the store bought version, and then on the very next beta to not use the beta version for serious work, and then I can't open the updated document in the store-bought version.
For now, I will not use these beta versions. The confusion outweighs the new features, and if there is a serious bug on the store bought versions please fix those.
-
4 hours ago, KeithNFW said:
I'm about to purchase a new Mac Mini M1 and was wondering if Affinity works well with it.
Oh yes it does, even better than on Intel - not knocking the performance on Intel but just saying that on M1 you will feel 2x or a 3x boost. You should get the 16Gb version though to get the maximum performance gains.
-
5 hours ago, Old Bruce said:
yes this crashes on M1 Macbook Pro as well.
-
22 minutes ago, Patrick Connor said:
Thanks we have replicated this problem and as you say it affects both macOS and Windows for some documents
can you post an example document that is known to crash and see if that happens also with M1. Or, will you test on M1. I need to see if I need to revert to an older beta.
-
Was a bit concerned after reading crash comments above. I'm on an M1 Macbook Pro and opened a document that I made with the previous AP beta and so far no crashes yet. Speed of opening is ridiculously fast, but it was also fast on the previous beta.
-
18 hours ago, garrettm30 said:
Now we finally know: 1.10 before (and possible others) before 2.0
But since you have not released 1.9.4, you have put us in a bit of a bind here. Remember that your recommendation for the 1.9.4 betas was this:
I have followed that advice, particularly as 1.9.4.1076 "Fixed issue with Paragraph Minimum letter spacing." That fix is fairly major in that it causes reflow. Therefore, I have been using 1.9.4 betas to use that fix so my documents will not reflow once 1.9.4 would be released. But now there is no 1.9.4, and the current recommendation is
That leaves us stuck, with no recommended version for fixing the text reflow. In order to open my existing "real work" documents that were made using the 1.9.4 betas "in preference to the store version," as advised, I only have these options: 1) open in 1.9.3 release where layout will reflow due to the unfixed bug, 2) use this new beta for real work despite your strong recommendation not to, or 3) use the last 1.9.4 beta exclusively and sit out the 1.10 beta process entirely until release. Option 3 seems the only reasonable choice to me.
I beg you to consider locking down 1.9.4 and releasing before moving on.
I second this. It would be great if the store releases could be refreshed to the latest 1.9.4 bug fixes as 1.10 betas go into play. Another reason for this, other that what GarretM30 stated above, is that once you open and save a 1.9.3 document into a 1.10 format you can't open with an older version, and the same holds true for 1.9.4 (to be fair I haven't tried that but guessing this from past beta experiences and also the warning to proceed when opening in 1.9.4 and beyond). So really sticking to or re-downloading the last 1.9.x versions would probably be the safest best as stated - or is it? What is the stability report on the 1.10 versions? I do heed warnings but I was designing in some of the earliest Publisher beta and I have survived quite intact through all that. So I am left wondering.
Apart from the bug fixes in 1.9.4 and 1.10, I couldn't see myself going back to the current store versions. The new versions are incredibly fast compared to the current store versions by a factor of 10x+.
-
Here is one. I have other examples but I prefer a dropbox link direct to you. But this is a perfect examples. AdobeStock_125449396 [Converted] copy.ai
'file has been truncated due to commands no longer available in 2.6'
in Other New Bugs and Issues in the Betas
Posted
I have an AFPub file in a latest non-beta version that opens in the beta with the message 'file has been truncated due to commands no longer available in 2.6' (or something like that). I accept and then can edit this in beta 2.6. but when I try to save there is a crash every time. I'm concerned I will lose the ability to edit this file in 2.6 once it exits beta. Can a staff member confidentially take a look at this file?