Andy05
-
Posts
575 -
Joined
-
Last visited
Posts posted by Andy05
-
-
5 hours ago, Oval said:
Or you need pixel if you would like to vectorize in another app
What kind of argument is that? You obviously never worked professionally in any kind of design sector, which requires a vector workflow. Otherwise you wouldn't post such a suggestion here.
Furthermore, I bet Serif likes your thinking! Hey, you know what? There are so many apps out there which can do what Affinity Apps can do. And I'm not talking about the expensive Suite from Adobe. There are some for free, for similar money etc. So what? Serif should not pay attention to any requests and we all move on to using various other apps which provide the features we need? And leave Affinity apps behind?
I wholeheartedly hope you don't run a business with this kind of thinking.
-
15 hours ago, MCFC_4Heatons said:
OK I see, You can effectively retain editability inside the Afffinity app using the Live Filters, but when you export it will rasterize ...
So, if your final export format needs to be a scalable vector its a problem. If your highest quality requirement for export format is as a high res bitmap then it's still very useful to retain editability inside the Affinity App if you need to return and edit further...
No, it's not useful at all. Show me how you distort text and export it so I can use it in a workflow for laser cutting or for CNC. Or how you export this as EPS/SVG that way so stockpages will accept it as vector.
If you need vector, you need vector - not a pixel image in whatsoever high resolution.
-
9 hours ago, MCFC_4Heatons said:
The live perspective tool in Affinity Photo is non-destructive. Text, vectors and shapes and their properties are still editable after applying it - access it from the liver filters icon at the bottom of the layers panel in Affinity Photo.
But it rasterizes the objects. So the results are not useable in any workflow, which requires vectors.
- Mark Freeman and Dazmondo77
-
2
-
Ich kann das auf den Screenshots nicht erkennen - aber es sieht so aus, als wenn auch andere Programme (z. B. Browser) davon betroffen sind? Hardwarefehler schon ausgeschlossen (z. B. durch Tauschen der Anschlüsse der beiden Monitore).
Die Farbverschiebung ist eigentlich dafür viel zu extrem, vielleicht dennoch mal ein Versuch wert:
Wenn einer der Monitore per HDMI an eine nVidia Karte angeschlossen ist, kann es an den Standardeinstellungen der Treiber liegen. Versuch' einmal unter "Anzeige - Auflösung ändern" die Option "Dynamischer Ausgabebereich" nicht auf "begrenzt" zu stellen.
-
You can't embed fonts into an EPS files unless you ignore the specifications (i. e. like Corel does or Illustrator, which often embeds full own, propitiatory commands into EPS files which can't be rendered correctly by other software than Adobe's).
EPS files are final-form print files, that don't know anything about i. e. the printer or app which they will be used for. If they have specific needs, such as patterns or fonts, they need to be added separately to the printer or app for proper rendering.
-
Pica and points are traditional units, originating from the typography sector. 1 pica equals roughly 1/6th of an inch and is divided into 12 points. To make things even more confusing, there are different "picas" (French and American)... Nowadays, if using pica/point as units they are mainly being used for font sizes and line widths. At least over here, in Germany, neither pica nor points are being used for document sizes.
As for latter it's usually either mm/cm or inches (depending on your country's usual units for measuring) for designing things for print. If you design for web, designing in pixels gives more control over the final result.
-
Again, I have some "remains" from a client's project (like the engraving macros last time), which might be useful for one or two:
Simple 2-file solution, which generates a fake ISO 3D map of any image, shape or even text. Easy to use. Just place your object(s) into one file and update the master file. Cut's colours editable via layer FX.
Caution! Can be quite demanding on weaker systems.
Available for free (just enter "0" as price) at Gumroad.
- Paul Mudditt, FraGar and Dan C
-
1
-
2
-
17 minutes ago, Catshill said:
Yes indeed but my question relates to the determining factor if it isn’t the file suffix.
In that case, some pop-up should appear, asking for an application to open the file with. Starting with a list of "commonly known/used apps" and a link at the bottom which will allow you to search for an app manually.
-
I can confirm, that particleshop (here: v. 1.5.108) is running without any issues in APh. Make sure that the path to the plugin is set correctly. As for native Photoshop CS6 plugins, they are not compatible with affinity apps as far as I know.
If the paths are correct, you need to check the colour profile of your image. particleshop (like some other third party plugins) work only with 8-bit RGB when started from within APh.
-
9 minutes ago, Catshill said:
What determines which app opens a particular filetype if it is not the suffix?
In Windows, the user can set this. Even stupid/broken things are possible, i. e. assigning .af* files to open in Word. Also, apps can do this ("polite" ones ask the user for permission before assigning any file type to their app permanently). But changing the application icon back and forth like the OP mentioned, shouldn't happen.
-
8 hours ago, R C-R said:
Read it again, more carefully. I said that when positions & sizes are set to whole pixel values, then the dimensions do not change.
Read yourself. You said, the user has control over it. Not that he (has to) use(s) it. Just because the user has control, it doesn't mean that the software should expand the image if the user doesn't make use of this control he has.
See? Your initial claim (which the discussion started) is still utter nonsense.
But I'm really done for good now. I even got several private mails in the meantime from other users that it's not worth wasting time with arguing against you as it seems to be commonly known that you will just go on and on and on and on even though you're wrong.
In order to not get tempted to reply anymore, I found the useful function of blocking users' comments here in the fora. Welcome in my killfile, you're my first guest in there.
-
-
Dang, sorry for posting the German link. I used a different browser than my standard one in order to find that URL, so the one I used was set to my system language (German).
But the software should be multi-lingual.
-
The freeware (!) XnView might be worth a try. It's also a not-so-bad DAM, can show at least the embedded previews of .aphoto files and also adds thumbnails to Explorer's view.
-
21 minutes ago, Alfred said:
I didn’t mean that different words never sound the same, I meant that (as per your “ai/ei” example) pronunciation is consistent, so you don’t get funny things like “s” being pronounced differently in the words “choose” and “loose”, or “o” being pronounced one way in the words “chose” and “rose” but another way in the word “lose”, and you don’t get anything like the huge range of different ways to pronounce “ough” at the end of a word.
We have such things, too. "Vampir" (vampire) has a long vowel "i" at the end whereas the "i" in "Pirsch" (hunt) is short.
-
12 minutes ago, loukash said:
Alright alright. Apart from quickly inspecting my late dad's Win7 PCs last year after finally finding his passwords, I have no clue about Windows workflows…
There is actually a comparable way to do it. But that'd also open an external application. So there's no real benefit in comparison to using "edit in". I just wanted to say that there might be reasons why Studiolink isn't always the best option (though it's so damned convenient!).
-
1 minute ago, loukash said:
Then you can just as well use the quick'n'dirty "Resource Manager > Show in Finder > Open With > Silver Efex Pro 2" workflow…
Works for me with the free-as-in-google-beer Nik Collection.
Bit hard to follow that workflow on a windows PC. 😄
-
Just now, loukash said:
However, if you'd really need that kinda stuff, you may possible want to save as native afphoto files anyway and place those, no?
Not necessarily so. I. e. using a quick B/W conversion via NIK silver effects (quicker and better results, more control) is an as destructive edit as those of many other plugins. So the native .afphoto file format doesn't provide any benefits in such case.
-
13 minutes ago, loukash said:
Not really necessary in Publisher if you have the Studio Link anyway, is it?
Studio Link is not the same as "Edit in" as far as it concerns Affinity Photo. You can't use external plugins in Studio Link.
-
3 hours ago, Alfred said:
German pronunciation is much better behaved!
Uhm. Really? "Saite "(the string on an instrument) and "Seite" (page of a book or the side of something) sound exactly the same or "sähen" (to sow) sounds similar to "sehen" (to see). In general "ai" in words sounds like "ei", "eu" sounds like "äu" and suchlike. And there are quite some more weird examples where some of the rules of "if it's written in this way, you have to pronounce it that way" (and vice versa) won't work.
-
4 hours ago, iconoclast said:
I think, the point is that the image layer will only loose quality once, while a pixel layer will be resampled and loose a bit of its quality every time you transform it (scaling, rotating, perspective warp...).
Exactly.
-
Native file save. Sorry for using the wrong expression. But that doesn't render my argument invalid and still proves you wrong.
Secondly,
1 hour ago, R C-R said:As for what you emphasized in red about user control, as @MEB & many others have explained in this & countless other topics, the user has complete control of where to place & how to size objects, including moving/setting them to whole pixel values, so that when exporting to a raster image format, nothing needs to be cropping away nor do the export dimensions need to be increased to include whatever might otherwise be cropped away.
Are you kidding me? That's what I said from the beginning! And that's what you denied to accept. That is what all the discussion is about, Einstein! The software should not increase dimension. But you said, it should. Even if an object is misplaced, the app should NOT change the dimensions of an image.
Now you said it should not. So you basically proved yourself wrong since the start of your discussion. Since you finally proved my point by just repeating my intitial claim:
Please, write down "Even if an object is misplaced, the app should NOT change the dimensions of an image." 100 times. And no cheating by using power duplicate!
-
8 minutes ago, iconoclast said:
As far as I understand, the basic point is that image layers are none-destructive - you can't manipulate them as image layers - and they cause much less file sizes. So if you need to insert a layer that must not - or even shall not - be modyfied, you can better insert it as an image layer.
Yes, another benefit is that image layers (internally) keep their original resolution. So, even if you resize them back and forth over and over again, they'll not lose quality.
-
28 minutes ago, user_0815 said:
You can target a very specific colour by moving those round handles on the colour wheel.
Nice solution. And even easier, if you use the picker tool ("Pipette" in der Deutschen Version) in order to find the starting centre for limiting the colour range.
Designer - Free transform tool (perspective distort)
in Pre-V2 Archive of Affinity on Desktop Questions (macOS and Windows)
Posted
No-one does, if someone doesn't show any sign of sarcasm in a post, especially after there are tons similar to yours in this forums which are meant to be good advice.
Depends on the sector you are working professionally in. I. e. the combination of a seamless pixel and vector workflow is quite striking for digital artists who paint their arts on digital canvas. Also, it's quite usable for almost all demands in conservative printing media, i. e. creating ads for newspapers or business cards. I know, for latter some regions might have different taste for them, so the missing vector warp might be an issue again in order to create "fancy looking" stuff.
But wait! Let me guess! Your comment was yet another attempt of "sarcasm", I suppose?
For a real vector-only workflow, there are other things quite as problematic as the boolean operations or missing vector warping. For instance, the lack of real vector brushes, which—to me personally—is the biggest issue for a true "vector-app". For every other problem, you can find workarounds or call them "extra features, not (yet) implemented" and rely on third party software. But the lack of true vector brushes is simply a joke, if you want to sell vector software.