markw
Members-
Posts
1,209 -
Joined
-
Last visited
Everything posted by markw
-
Export problem
markw replied to NealE's topic in Pre-V2 Archive of Affinity on Desktop Questions (macOS and Windows)
As you have a viable workaround, then at least you can use that for now, which is good. The important thing is that the actual pixel count of your file isn’t changing so you are not loosing any quality. Apps use the ppi to assume what the finished physical size should be. But it is just attached metadata and can usually be overruled. Out of curiosity, was the original AD file created at 300ppi? If so then the question is why dose the .svg exported from AD now import back into AD at 72ppi and at 96ppi in Inkscape? I think this is possibly to do with the ppi metadata in the exported .svg file from AD not subsequently being read correctly in other apps. I’m sure I read another post around here some place of others experiencing a similar thing?… Sadly I can’t find it now! -
Export problem
markw replied to NealE's topic in Pre-V2 Archive of Affinity on Desktop Questions (macOS and Windows)
At what ppi/dpi are you viewing it at in other apps? Opening your test file in Affinity Designer, it is 6750 x 1800 pixels @72ppi, which gives a potentially printed image of 93.75” x 25”. Changing the ppi to 300 gives your expected size of 22.5” x 5.5”. -
Google Font "Quicksand" is not displayed correctly
markw replied to GRSJeremy's topic in V1 Bugs found on macOS
The above and then this, seem to contradict each other; This seems to be an issue with the fonts obtained from GitHub. How the “Lockdown” sample file Jeremy posted, or any other file containing Quicksand font, displays will depend on which fonts you have installed on your system. Where are you obtaining your Quicksand font from? Google or GitHub? This is the Google Fonts link Sean P posted earlier in this thread to the Quicksand fonts that works correctly for me: https://fonts.google.com/specimen/Quicksand -
Google Font "Quicksand" is not displayed correctly
markw replied to GRSJeremy's topic in V1 Bugs found on macOS
The files you attached Jeremy are indeed corrupt/faulty. However I just downloaded v3.004 from the link Sean P provided earlier in this thread and they all work fine. It might be worth ditching the Quicksand family you currently have and then just reinstalling them from Google. -
Or are you saying that although your documents have content, the Layers panel is entirely empty of any layers? Or that there are no thumbnail images of each layer’s content? The first I’ve not come across but the second is a known, if only occasional, bug whereby the thumbnails can be very slow to populate their respective layers.
-
That looks familiar. This behaviour has also been seen on Macs too. It still happens on mine but since I’ve never needed to do one long continuous stroke as seen in the recordings I’ve never found it a show stopper. But if it could be improved...
-
I see what you mean trying to open it in Designer… So, open the label PDF in Affinity Photo and do the Unclip Canvas trick again, the same as you did with the sleeve last time, to reveal the whole template. Now, in AP go to; File > Edit in Designer. This will load the whole document into Designer looking as you now see it in AP. Once it’s in Designer you can then use the Text Path features of it’s Text tool there. If you subsequently want to get it back into AP when you’re done with the Text tool in Designer, go to; File > Edit in Photo.
-
This I understand, but the use of the two menu items 'Unclip Canvas' an 'Clip Canvas' have very specific meanings when used to working with Pasteboards in Designer and in the context of Photo actually perform in the case of 'Unclip Canvas' a very different action and in the case of 'Clip Canvas' nothing at all.
-
Well, there is sort of, partially at least at present. Open an image. Add say a curve or text to one side of the image on screen. It will not be visible and hidden. Go to; Document > Unclip Canvas. The Canvas will expand to include the previously hidden content. However, items outside the original image can not be hidden again by going to; Document > Clip Canvas, even though that menu item is offered. Though I’m not too surprised at this because the canvas was actually expanded rather than strictly speaking “Uncliped” as the name suggests. Can't help but think this behaviour should in some way be cleaned up a bit and made more logical.
-
In Affinity Photo’s Menubar go to; Document > Unclip Canvas, and it should display the whole document correctly for you. Why it opens "Clipped" I have no idea! I am curious about Old Bruce's screenshot too? Just opening the file from the ZIP link D_ provided in AP, and with Move tool selected, I get no 'Page Box' or 'Artboard' entry’s in the Context Menu, nor would I expect to with this PDF as is.
-
Time for a Pro Version?
markw replied to ANGRYMAN's topic in Feedback for the V1 Affinity Suite of Products
I’ve often wondered what “Pro” feature/s would never be needed by a non “Pro” in graphics apps that market themselves in that manner? All I can think of is maybe some kind of “Billable Hours” feature but then I’ve never seen that offered in any other “Pro’’ graphics app. -
The warning message, “Out of System Memory”, would suggest to me that you are running out of RAM father than disc space. Which would definitely cause your system to grind to a crawl. As Pšenda asks what dose your 500 images add up to? Even linked it’s still data that APub needs to keep track of. How much RAM usage have you allowed APub in it’s Preferences > Performance?
-
Hello dodecaray and welcome to the Affinity forums🙂 To recap some of the above points in this thread; The UI font size can be set to Large in the Affinity apps Preferences > User Interface > Font UI Size > Large. Tool Handel size can be set in Preferences > Tools > Tool Handel Size > Large or Largest. Unfortunately to get the Tool icons larger the only way to do this currently is to change your screen resolution in your Mac's System Preferences > Displays > Resolution > Scaled > and choose one of the options to the left of the Default option. However, as this is a global setting it will change the size of how everything on your Mac looks so it may not be a viable solution for you.
-
Me parece que tiene su documento en el espacio de color CMYK o otra espacio que no es RGB. Aunque es posible acceder a los controles deslizantes RGB en documentos que están en el espacio de color CMYK por ejemplo, al hacer esto, el color real que se muestra será la aproximación más cercana a los números RGB ingresados que CMYK puede lograr. RGBvCMYK.mp4
-
added noise is seen as a a grid when saved in TIFF
markw replied to srg's topic in V1 Bugs found on macOS
Interesting, I’ve never experienced that myself. What settings were used in the noise filter? Dose it happen with both types of filter? Live and/or Destructive? What export settings were used in the TIFF? Would you be able to provide an example AP file and it’s TIFF output that always shows this behaviour for you, so others here on the forums could poke about and maybe see what’s going on? -
Interesting, I’ve never experienced that myself. What settings were used in the noise filter? Dose it happen with both types of filter? Live and/or Destructive? What export settings were used in the TIFF? Would you be able to provide an example AP file and it’s TIFF output that always shows this behaviour for you, so others here on the forums could poke about and maybe see what’s going on?
-
I don’t think there is an “easy” way to do this, if by “easy” you mean a “one, or two click” solution! But things can definitely be improved! You can see what I’ve done in the attached. A strait out Sky replacement works for those areas and a similar approach could be used for the grass too (I didn’t have a suitable image for that though). Otherwise I opted for adjustment layers inside Masked Groups and some Patch Tool work on the grass. Antonov.afphoto.zip