MEB
-
Posts
31,414 -
Joined
Posts posted by MEB
-
-
Hi @iconoclast,
No, it's not possible to adjust the handles of multiples nodes simultaneously unless you are considering the use of symbols to work with symmetrical objects. -
-
Hi @Darner,
This is a known issue that's already logged with development. I've updated/bumped the report to bring it up to devs attention again. Thanks for your feedback. -
Hi @Oliver Winternight,
Welcome to Affinity Forums
Affinity Photo version 1 did have the Adjustments panel visible by default. Version 2 doesn't - we changed this mostly because you can also add them through the Adjustments button on the bottom of the Layers panel (besides the menu Layer). So unless you need quick access to custom presets you may save in the Adjustments panel there's no reason to keep it part of the default set. -
There's still something wrong with the outline filling the whole canvas. If you could attach the original NEF and the .afphoto file for inspection it would help determine where the problem is. If you do not wish to share them publicly let me know and I will provide an upload link for you to send the files directly to us. Thanks.
-
Didn't noticed the colour of the outline is the yellow. Good catch Garry.
@PhilipC Do you mind attaching the original NEF file please? -
You don't have to export and re-import. Just make sure you rasterise & trim after the crop to get rid of the cropped parts, before applying the FX. In the case above, when you applied the rasterise & trim command toi the layer did you keep the "Preserve layer FX" ticked in the dialog that appears? It's necessary to keep it ticked for the app to (re)apply the FX to the new rasterised/timmed area otherwise the current state (with the outline only visible in some edges) gets backed in the rasterisation process and nothing changes visually which seems what you've done.
-
Hi @awakenedbyowls,
There's no way to know which brush was used in a previously saved document. Those are raster brushes - we only save the ones used in pixel layers (clicking the brush icon in the respective layer in the Layers panel) for the current session. After saving and closing the document that information is lost. The brushed strokes are simply "backed" in the raster data of the layer - there's no way to know the brush used to paint them.- awakenedbyowls and Zukling
-
2
-
Hi @PhilipC,
Seems you have cropped the original image and the cropped parts remain there but invisible but are still being affected by the FX (note the size of the image inside the thumbnail with lots of space around it). Right-click the image layer and select Rasterise & Trim to ensure it's size match the canvas. You can then apply the FX and it should work as you'd expect. -
Hi @_Amageton_,
Welcome to Affinity Forums
No, no fix yet, sorry. I've updated/bumped the report to bring it up to dev's attention again.
Thanks for your feedback. -
Thanks @Wu Yu Sen, @rcniman
I've updated/bumped the existing report to bring this up to dev's attention. -
-
-
-
-
Thanks @GripsholmLion. I'm logging this to be looked at.
-
The terminology as it is, is clear/correct, the problem is it isn't used consistently throughout the apps in several places and in the Help.
I'm checking/logging all these cases and fill a report to fix this.
Regarding the Ask for name improvement, I will add the Alt click option to the report I filled yesterday for a preference setting. Maybe both are implemented, it's up to the dev team/management. -
35 minutes ago, Gatada said:
I'll do my best to not take that as an insult.
MIME type is image/jpeg, the extension—which can be easily change, and therefore means little—is jpg.
The full details: JPEG image data, JFIF standard 1.01, resolution (DPI), density 300x300, segment length 16, baseline, precision 8, 1500x820, frames 3 (Lepton 2.x), scale 0-0, spot sensor temperature 0.000000, unit celsius, color scheme 0, calibration: offset 0.000000, slope 0.000000
Using a HEX editor I can see that the image is made with Photoshop 3.0.8.
Hi Gatada,
I'm really sorry. I didn't mean to upset you. If it's a jpg then it means it contains clipping paths which are imported as vector masks in Affinity apps. -
Hi walt,
The Layer command is being logged already along with the iPad issue.- walt.farrell and Gatada
-
2
-
Thanks Walt. That's clearly inconsistent with the desktop app. I'm logging this to be looked at.
@Return,
I'm just explaining the reasoning behind these names. I have no personal interest (nor Serif I'm sure) in making the apps complicated - quite the opposite. The only difference when compared to Photoshop/Illustrator is that we call Photoshop's equivalent of layers - pixel layers (not layers).
And the reason for this is to avoid confusion with Illustrator (and Affinity Designer/Publisher) layers term (which act as containers). -
@Return,
From what I'm seeing in the forums people (specially regular users) do use the term Layer with capital L, when explaining things to other users.
Regarding your example above - it should read "Layer - used for placing vector objects into". The description isn't quite accurate either since it can also hold other types of object inside including pixel layers (which are also missing from the list as well as fill layers, text on curve and probably more). -
6 minutes ago, walt.farrell said:
There's another variant on the iPad, with the term Vector Layer. That is confusing because it is different from the desktop applications, and also can lead to the question of "what are shapes, Curves, etc." if not "vector layers"?
Where are you seeing this? That doesn't really help unless it's being used generically to refer multiple types of vector objects (text, shapes, curves etc) and not as yet another type of layer.
-
The terms are pixel layer and layer. People got used to call it layer with capital L to distinguish it from pixel layers because they also call them layer generically without preceding it with "pixel".
-
14 minutes ago, Return said:
Yes and that's a wrong implementation, it should be more distinctive.
11 minutes ago, Alfred said:Isn’t the real issue here the decision to call the container a ‘Layer’ instead of … oh, I don’t know … a ‘Container’, perhaps?
Not necessarily. For someone using any app individually the term "layer" covers the regular/expected use it has in that type of application (like in the case of Photoshop and Illustrator - both have layers, they differ in functionality between them and nobody ever questioned their name) but in our case where the apps are tightly integrated (StudioLink for example) the need to distinguish between them becomes important thus the "new" term "pixel layer".
@Alfred Maybe Container (for Layers) and Layer (for pixel layers) would have worked better but then nobody would understand the "Container" term and would eventually ask why didn't we call it Layer like everyone else...
@Gatada This doesn't mean we can't add a similar function for pixel layers (ask for a name on creation).
Affinity 2 does not open the document, it keeps loading
in V2 Bugs found on macOS
Posted
Hi @kimthejo,
Welcome to affinity Forums
No, this issue wasn't fixed in this latest build (2.4.2). You will see a Serif Bot message in this thread when the bug is fixed. Unfortunately it still not clear what's causing the issue - we are still investigating it. Thanks for your feedback.