4dimage

There a several post in the bug report sections from users working in the architectural context. Despite this simply think of creating huge designs that will be printed as posters via online print services. All DIN formats should be availlable as presets.

Dein Bild ist im sRGB-Format im PDF.

 
Beim Export muss zusätzlich «Bildfarbraum umwandeln» aktiv sein.

So stimmt der Eintrag.

Bereits mit v2.x erstelltes Dokument mit v1 standardkonform nach PDF/X-3:2003 exportieren
Das ist eine Knuschellösung für alle, die glücklicherweise noch die letzte stabile Version v1.10.6.1665 installiert haben. Und weil das scheinbar eh vor allen Dingen die deutsche Version betrifft, spare ich mir hier den üblichen Übersetzungsmarathon.
Ich hatte leider das Layout in v2.3.1 bereits erstellt. Für den Druckservice ist eine Beschnittzugabe von umlaufend 5mm vorgegeben - und wie fast überall das Farbprofil "ISO Coated v2 300% (ECI)".
Wie bekomme ich nun die korrekten Druckdaten, ohne alles in Publisher v1 neu aufbauen zu müssen ? Kann sein, dass nachfolgend die ein oder andere Option nicht zwingend erforderlich wäre - aber so hat es bei mir am Ende funktioniert.
 
1) Ich exportiere das Dokument aus v2 komplett oder seitenweise NICHT direkt nach PDF/X-3 sondern mit der Vorgabe "PDF (für Export)".

Ziel ist es so viele Eigenschaften der Grafikobjekte wie möglich ins PDF herüber zu retten. So sollen z.B. die eingebundenen Bitmaps nicht heruntergerechnet werden, die Texte als Fonts erhalten bleiben und ich will auch die Beschnittzugabe mit exportieren. Hierzu ändere ich einige Optionen gegenüber der Vorgabe. Vor allen Dingen bette ich sicherheitshalber das ICC-Farbprofil NICHT ein!

 
 
2) Ich öffne die alte letzte stabile Publisherversion 1.10.6.1665 und erstelle dort ein neues Dokument mit den identischen Einstellungen, wie das v2.x Dokument. Das bezieht sich auf Größe, Auflösung, Farbmodell, Farbprofil, Anschnitt etc.

 
3) Ich platziere das aus v2 exportierte PDF in Originalgröße auf meiner Layoutseite. Hierzu erstelle ich einen Bilderrahmen, der sich bis über den Anschnittbereich ersteckt. Hierbei ist zu beachten, dass die Seitenbox-Voreinstellung für platzierte PDF zunächst "BeschnittBox" ist. Das würde zu einem verzerrten Einpassen des PDF in den Bilderrahmen führen. Stattdessen sollte die Seitenbox auf "MedienBox" stehen und der Vollständigkeit halber der PDF-Transfer auf "Interpretieren". Letzteres zeigt dann auch bei nahem Heranzoomen, dass die Texte korrekt exportiert und nicht gerastert wurden.
Die Einpassen-Eigenschaften des Bilderrahmens sollten auf "Minimal passend skalieren" stehen. Stimmt alles, so zeigt das Transformieren-Panel beim Selektieren des Bitmap-Inhaltes exakt die Größe des Bildes an, die inklusive Anschnitt erwartet wird.


 
4) Aus diesem v1 Dokument exportiere ich jetzt mit der Vorgabe "PDF/X-3:2003". Die Option "Inklusive Anschnittbereiche" muss aktiv sein, damit die Beschittzugabe Teil des PDF wird und alle Rahmen korrekt geschrieben werden.

Heraus kommt ein standardkonformes PDF/X-3:2003, das in Acrobat den Preflight Check fehlerfrei besteht.

 
Danke Serif, dass ich diese Aufgabe, die normalerweise 1/2 Minute dauern würde, in einer Stunde erledigen durfte.
What an amazing tool...
 
 
 
 
 

Damned, i ran into this crap one more time. Stil trusting in Publisher v2 (2.3.1), i did some signage layouts. How could I have been so stupid? Of course, when exporting it to PDF/X-3 for an online print service i got the same color profile errors. The preflight check in Acrobat fails.

This error also appears when exporting from beta v2.4.0.2240. Unfortunately there is no backward compatibility with Publisher v1.10.6.1665 😒 But i don't want to recreate the whole layout in v1.10.x again... 😶
Hi guys - the first post in this thread is of Novemer 2023. Meanwhile any plans to fix this heavy bug ?!
Or should I give up my job as a graphic designer and work as a delivery boy instead? All I need is two healthy feet, which thank God I still have. Nothing against delivery workers - they do an honest, hard job!
 
By the way: this error appears even with a fresh EMPTY document. Of course this passes the preflight check because there is no offending content in it.
test1.afpubtest1.pdf
 

Hi K_au,
This seems to be working fine for me here, please could you ensure you have installed the 2.3 update?

Apps: All
Platforms: Windows, macOS and iPad
All Affinity apps now support import and export of 32bit HDR PNG files, as described in the PNG specification (3rd edition). Both PQ and HLG are supported alongside full / narrow range and a full set of primaries. Files exported can be used directly in video editing applications or shared on the web (Chrome now supports HDR PNG files). In addition, legacy PNG and TIFF files exported from Photoshop with CICP data embedded in an ICC profile are also able to be imported.
 

I believe this has been requested before: In the case of the Desktop version, having a Panel dedicated for this alignment actions would be better than the current Dropdown option. Still, nice additions.  
Best regards!

Apps: All
Platforms: Windows, macOS and iPad
Within alignment options you will see three new options to make all items in your current selection adopt the same width, height or rotation. By default this will transform all objects to match the first item selected, or alternatively if a key object has been nominated (alt-click) it will use that as the source.
Additionally you can choose to maintain the aspect ratio of the objects being resized.
On desktop this is available via the alignment dropdown:

And on iPad via the alignment options panel which you can get to via the transform panel:

 

Apps: Designer
Platforms: Windows, macOS and iPad

Affinity Designer now supports both DWG and DXF export, available from both File->Export and the Export Persona.
It's important to note that both these file formats are primarily concerned with vector outline data, with limited support for many of the features Affinity offers. However, it's been a heavily requested feature particularly as it means outlines created in Affinity can be easily exported and consumed in various CAD applications as well as utilities for things such as vinyl cutters, plotters and CNC tools.
Because of this, as well as some of the other fundamental differences in the file formats such as layer structure, while both import and export of DWG is now available we do not consider this a format which is suitable to round trip in Affinity. Or put another way we would not recommend collaborating with an AutoCAD user on the same DWG file.
Within export we do offer various options on how to deal with some of the unsupported features / differences in the file format:

 
Layers
All entities in DWG/DXF belong in a layer. There is always a default “Layer 0” in a valid DWG/DXF file. Affinity also has layers. This setting determines how Affinity layers are mapped to DWG layers, and therefore which DWG layer an exported item belong in

Gradient Strokes
Determines what to do with strokes with a gradient fill applied, which DWG does not support.

Gradient Fills
Determines what to do with fills with a gradient fill applied

Bitmap Strokes
Determines what to do with strokes with a bitmap fill applied, which DWG does not support:

Bitmap Fills
Determines what to do with fills with a bitmap fill applied, which DWG does not support:

Pressure Strokes
Determines what to do with strokes with a pressure profile applied, which DWG does not support:

Overweight Strokes
Determines what to do with strokes with a line weight > 2.11mm, which DWG does not support:

Dashes Strokes
Determines what to do with strokes with a dash pattern applied. DWG does support dash patterns; however DWG dashes do not scale automatically with line weight, as they do in Affinity. 

Scale dash patterns
If any line weight adjustment is made to an exported curve (e.g. it is clamped to the 2.11mm maximum), you may expect the dashes to stay the same length, or you may prefer them to scale automatically as they do in Affinity. The former is similar to AutoCAD’s behaviour - when you change an entity’s line weight, it does not recompute the dashes, which is effectively the opposite of Affinity’s behaviour. If “Scale dash patterns” is on, Affinity’s behaviour is used, so dashes will be scaled down if the line weight had to be scaled down.
Apply drawing scale
When enabled, the drawing scale is honoured. If you export an rectangle that is 1 inch wide and your drawing scale is 1:10, the rectangle will be exported 10 inches wides. Note that Affinity documents support multiple drawing scales within the same document, which cannot be honoured in a DWG/DXF file, so only the first/common drawing scale is applied.
 

Apps: All
Platforms: Windows, macOS and iPad
Using even space distribution on a multiple selection will now behave differently if you have a key object nominated. This relates to either the space horizontally or space vertically options available in the alignment drop down (or Alignment Options available from the Transform panel on iPad):


 
The previous behaviour was always to space the objects in your selection with (in the case of horizontal spacing) the furthest left item and furthest right item remaining in the same position, and all other items in your selection spaced evenly between them. This is still the default behaviour.
However, the new functionality is that if you additionally specify a key object in your selection (alt-click an object) the behaviour changes to mean the furthest left object and the key object will not change position, and the other items are spaced evenly between them. This is particularly useful as you may quite often have the first two objects in your selection at the correct spacing and you want to space all other objects the same distance. Now you can nominate the second object as the key object and achieve this.
Additionally if you Alt-click the spacing button the distribution will be calculated between the furthest right object and the key object.
Below shows the different results:

 
All the above showing results for horizontal spacing, but the same applies to vertical spacing when working top to bottom.

Apps: All
Platforms: Windows, macOS and iPad
While transforming any object with the move tool (whether resizing, rotating, skewing or moving) you can now hold space to temporarily toggle Lock Children on or off (to achieve the opposite behaviour of what you currently have set in the context toolbar).

Apps: Photo and Designer
Platforms: All
In Export Persona Filename is now available as a token variable for building either folder paths or exported filenames of your slices. This is available with two options:
Document Name = the name of the document without the file extension
Document Filename = the name of the document including the file extension
For example if you had a document called "Social Ads.afdesign" which contained artboards named "Version 1", "Version 2", etc.  you could now specify your path to be Document name like below:

And this will automatically create a folder called "Social Ads" with your slices being exported within it:
Social Ads/Version 1.png
Social Ads/Version 2.png
etc.
You can also use these tokens as part of your exported file names, e.g. if you set up as below...

 
That would result in your exported files being named:
Social Ads (Version 1).png
Social Ads (Version 2).png
etc.

Additional note

Worth a reminder when testing these feature you can copy and paste export set ups from one slice to another slice using the copy / paste buttons towards the top of the panel. You can also create your own export set up presets from the burger menu in the slices panel.

The problem I reported at the beginning of the beta cycle (4.07) has not been resolved either. It concerns Mac and the selection of objects after using the scrollbar.
I think it's important because it's working with text.  Why it's not important to you remains a question.
And in the end, beta problems become releases, and the same bugs in releases become betas again. It's a vicious circle.
Soon, a new beta cycle will start, and everything will start all over again, and the beta 2.2 bugs can't be fixed anymore, because there will be beta 2.3 and you're going to have completely different priorities.

Apps: All
Platforms: Windows, macOS and iPad
There is now an option in the guide manager to change the colour of your guides. On desktop you can set this by going to guide manager (View -> Guides... or double click on any guide) and find the colour preference in the bottom left hand side of the dialog. In the example below this being set to red:

On iPad the colour setting is available from the ring towards the top of the guides panel (available from the view drop down menu or again by double tapping on a guide).

This also applies to customer 2.1.1.
1) When opening the fields panel for the first time, the longer property names (nested level 1) are cut off on the left side because the left column is to narrow.
2) I can drag the split point to the right to reveal the hidden words.
3) After closing and restarting Publisher the old/initial panel split is used again and the property names are cut off again. This is annoying because you have to fix the panel layout each time before you can work with it.
Automatic panel layout depending on the word lengths of the localized property names might be difficult. But the panel should at least persist and restore the last split position manually set by the user. E.g. the last position, width/height of the fields panel are already persisted.

 

Apps: Publisher and Designer
Platforms: All
In the layers panel if you alt-click add new layer when you have a selection, all items in that selection are moved to the new layer created. In other words this behaves similar to grouping, but rather than creating a group it puts your selection into a new layer.
Additionally for desktop versions you will find a new option in the right click menu for "Move Selection to New Layer" which achieves the same thing.
 


This makes it far easier to organise your work into layers, without having to create an empty layer first and drag the items you want into it.

Hi @4dimage,
Looks like this is caused by an existing issue with the layers panel hit area not working correctly when drag and dropping objects between picture frames that are next to one-another in the layer stack, I've now added the details of your report and bumped the issue. 🙂

Also applies to current release 2.1.0
The button still has has the english label.

I observed a similar behaviour but with Publisher after working some hours on the same open document. In my case it was mostly obvious when open/close the glyph palette multiple times. The app freezed for 5+ seconds then opened the glyph dialog and somehow recovered.
I decided to reduce the undo protocol limit significantly down e.g. to 128. The initial value in all three apps after install is 1024 which (imho) seems to be far to high and may consume a lot of resources over time. But meanwhile could not reproduce the same long running usecase. Maybe (hope) that setting will help in the future...

 

I observed a similar behaviour but with Publisher after working some hours on the same open document. In my case it was mostly obvious when open/close the glyph palette multiple times. The app freezed for 5+ seconds then opened the glyph dialog and somehow recovered.
I decided to reduce the undo protocol limit significantly down e.g. to 128. The initial value in all three apps after install is 1024 which (imho) seems to be far to high and may consume a lot of resources over time. But meanwhile could not reproduce the same long running usecase. Maybe (hope) that setting will help in the future...

 

Hi 4dimage,

We have a couple of issues that relate to this message logged separately - whilst one of those is fixed, unfortunately the other is not and that is the one that relates to Metz Apparel's file. It is still open and assigned with development however.
However it is not a macOS specific issue, it just didn't have a Windows version logged against it so likely slipped through the release note cracks!

Just tested the Zero-Turn-Mower.afdesign with the latest beta: 2.1.0.1781
The error seems to occur somewhere in this region:

The calculation warning message appears when simply selecting pathes with the fill tool active.
I deleted one part of the drawing after another, selected/unselected different parts of the remaining drawing, inbetween used the fill tool selection mode while having the pathes partially selected until Designer crashed completely. Here is the report.
98798663-23e7-472c-8b1e-012403fd21c0.dmp
 

To be even more specific, it's this layer, highlighted using a black stroke... It shows the same 'Calculations failed message' when using the Shape Builder tool...
Alt clicking the left node handle for this particular node converting it from a smooth to a sharp node seems to fix the issue...

Lawnmower.mp4

Hi All,
Thanks again for all your continued help with this release. We are getting very close to launch. This will be the final beta build before what will hopefully be our first release candidate next week. For that reason we are not really making any further significant changes (or anything which could be considered risky). 
The main thing I want to make you all aware of is that we have decided to not release the cross-references feature with 2.1. For that reason this feature has been removed from this week's build.
Any documents you may have created which include cross references will still open (and they will even still update), but you will not be able to edit or create new cross-references in 2.1. We understand this might be disappointing for some of you, however we will be moving into 2.2 beta very shortly after 2.1 release, and as soon as a 2.2 beta is available that will include cross-references again (and will definitely make it to 2.2 release!)
We have made this decision primarily as we have been working on adding better formatting options (as have been requested on these forums) into the feature, but we have not quite managed to get it to a point where we feel it will be releasable in time - and considering all the other great stuff / fixes we have put into 2.1 we don't want to delay the whole of 2.1 because of it.

Other than that in this build it's mostly just fixes which you can see in this thread.
Thanks,
Ash

I would use Shape Builder Tool to avoid the antialiasing problem as shown in attached video.

planet builder.mp4