Petar Petrenko

Did you setup "Convert to working color space" in Preferences > Color?

BTW, PDF always embeds images.
Maybe, just maybe, the problem arises if you import PDF with 72 dpi images and on export, if you set the dpi to 300, Affinity resamples them?

And what is the canvas size?
Why not? You can do it and then save (export) the picture in the format QImage supports.

Something more specific, like:
why do you need to export them; which format do you use; what resoultion...

... and maybe turn off Caps Lock.

Just a suggestion:
Why don't you announce the updates in one thread instead in 3 with links to all 3 apps?
The main reason for this is that you can separate the info into 4 categories (easier for you):
Common for all 3 apps
Fixes, improvements...
Designer
Fixes, improvements...
Photo
Fixes, improvements...
Publisher
Fixes, improvements...
This way we can easily see what is specific for each app and what is common to all 3.

We may well start doing this, or something like it, thanks

I've just done it.

If you mean last week, then the Photo 2.0.3.1682 and Publisher 2.0.3.1682 you get were not the final release builds. Everything for Windows was officially released yesterday as 2.0.3.1688, and you need to update Photo and Publisher again if they are not yet 2.0.3.1688 (as shown in My Account top right)
 

Status: Beta
Purpose: Fixes and Updates
Requirements: Licensed Affinity Designer 2 (registered to an Affinity ID account)
Windows Store: Not Submitted
Download: MSIX Download
Auto-update: Not Available
---
 
We are pleased to announce that the first Affinity Designer 2 Customer Beta 2.0.3.1670 is now available as a download from the link above.
Please note: We are working on an equivalent MSI/EXE installer to ALSO be available before the time this 2.0.3.x beta cycle finishes, and becomes a public release.
This beta is an update to the 2.0.0 version recently released to all customers and will form the basis of our first patch for 2.0.0. We recommend that you use this beta in preference to the release version if you are affected by any of the issues listed below.
 
If this is your first time using a customer beta of an Affinity app, it’s worth noting that the beta will install as a separate app - alongside your store version. They will not interfere with each other at all and you can continue to use the store version for critical work without worry.
---
New Document: Custom Document Preset order is not retained between app sessions Current DPI of selected layer does not show in V2 Shape Builder Tool now has an additional option to delete open curves that were inside a newly created area, plus you can now hold Alt to delete areas while still in Add mode - more to come... Warp Group editing now supports the Shift modifier to lock node edits to an 8-axis grid. Also can be used with off-curve nodes to maintain their angle while dragging them Modifying Global Colour swatch fails to update document until you click out of the Colour Selector Sliders for Warp Group are broken Using the Select object/ transparency object selects all objects Symbols - Delinked nodes get forgotten when swapping out nodes from synchronised instances Shape Builder Tool: Alt to delete on rotated shapes fails Shape Builder Tool: sometimes drags out a selection marquee Shape Builder Tool: functional improvements on some shapes Placed documents with bleed fail to render the top and left side correctly Quotes can be incorrectly put on newlines and cause text to render differently compared to V1 Straightening in the Develop Persona offsets the image from the canvas entirely, until developed or crashes Transform Panel- Differences in panel size when switching between Curve strokes and expanded objects Cmd+Z / Ctrl+Z isn't working in V2 apps for adjustments Outline Layer Effect is making the anti-aliased edges transparent, rather than blending with the shapes colour Quick Access to Node Tool no longer allows you to insert node Fixed spurious "future version" error under certain circumstances Improvements with PDF Import and Layers Fixes for RTF import - font name discrepancies, fields in footnotes Update for HEIF importer DWG Import scaling improvements DWG file takes a long time to open then shows incorrectly (file specific). Export Panel UI fixes Fixed some tool drawing issues relating to selections across spreads etc Pen tool tweaks and fixes Fixed hang that could occur composing vertical centre aligned text OpenType handling does not respect lookup flags such as IgnoreMarks Hit box of scaled text could be incorrect Gradients on text strokes don't render unless the fill also has a gradient Fixes for line breaking in some odd cases with punctuation Resource Manager updates Light UI Improvements Many and various Layers Panel updates and fixes Clipboard: 32 bit DIB support added Auto Flow Place: Added an option to auto-flow place to replace the content of already populated picture frames More attributes are retained when replacing images in frames Ensure global colour edits update live Select Same Name should only select objects with user supplied names New clearer icons for stroke properties (cap, join, align) Localisation updates ---
To be notified about all future Windows beta updates, please follow this notification thread 
To be notified when this Designer update comes out of beta and is fully released to all Designer customers, please follow this release announcement thread

Status: Beta
Purpose: Fixes and Updates
Requirements: Licensed Affinity Photo 2 (registered to an Affinity ID account)
Windows Store: Not Submitted
Download: MSIX Download
Auto-update: Not Available
---
 
We are pleased to announce that the first Affinity Photo 2 Customer Beta 2.0.3.1670 is now available as a download from the link above.
Please note: We are working on an equivalent MSI/EXE installer to ALSO be available before the time this 2.0.3.x beta cycle finishes, and becomes a public release.
This beta is an update to the 2.0.0 version recently released to all customers and will form the basis of our first patch for 2.0.0. We recommend that you use this beta in preference to the release version if you are affected by any of the issues listed below.
 
If this is your first time using a customer beta of an Affinity app, it’s worth noting that the beta will install as a separate app - alongside your store version. They will not interfere with each other at all and you can continue to use the store version for critical work without worry.
---
New Document: Custom Document Preset order is not retained between app sessions Placed documents with bleed fail to render the top and left side correctly Quotes can be incorrectly put on newlines and cause text to render differently compared to V1 Can't place image when recording a macro in Photo V2 V2 opens raw files slower than V1 Running a V1 Macro that uses 'Add Image' (Place) crashes app - also applies to Batch Processing Importing .JPG and .TIFF files with Keywords only displays the last keyword in the Metadata panel Straightening in the Develop Persona offsets the image from the canvas entirely, until developed or crashes Exclusion blend mode causing unexpected results on 16bit file layers with blown highlights Transform Panel- Differences in panel size when switching between Curve strokes and expanded objects Tone Mapping Preset options missing. Blemish Tool failing after developing image. Develop Persona 'Sync Before' no longer functions Lens Correction Mis-Centered for Portrait Orientation Raw Files Nikon NIKKOR Z 24-120mm f/4 S not identified Phase One IIQ files are being rendered all black Mesh Warp doesn't work with multiple Outline FX. Cmd+Z / Ctrl+Z isn't working in V2 apps for adjustments Incorrect AF region display for Canon PowerShot G1X Mark III White Balance Tool giving different results for Infrared processing. Outline Layer Effect is making the anti-aliased edges transparent, rather than blending with the shapes colour Crop Tool displays checkerboard when rotating image in Develop Persona. The Patch Tool doesn't work with Global Sources & 'Set Global Source' remains greyed out Unable to Undo crop after pressing Enter key in Develop Persona. Blemish Tool lag in Develop Persona Quick Access to Node Tool no longer allows you to insert node (Windows)  Fixed spurious "future version" error under certain circumstances Improvements with PDF Import and Layers Fixes for RTF import - font name discrepancies, fields in footnotes Update for HEIF importer DWG Import scaling improvements Export Panel UI fixes Fixed some tool drawing issues relating to selections across spreads etc Pen tool tweaks and fixes Fixed hang that could occur composing vertical centre aligned text OpenType handling does not respect lookup flags such as IgnoreMarks Hit box of scaled text could be incorrect Gradients on text strokes don't render unless the fill also has a gradient Fixes for line breaking in some odd cases with punctuation Resource Manager updates Light UI Improvements Many and various Layers Panel updates and fixes Clipboard: 32 bit DIB support added Auto Flow Place: Added an option to auto-flow place to replace the content of already populated picture frames More attributes are retained when replacing images in frames Ensure global colour edits update live Select Same Name should only select objects with user supplied names New clearer icons for stroke properties (cap, join, align) Localisation updates ---
To be notified about all future Windows beta updates, please follow this notification thread 
To be notified when this Photo update comes out of beta and is fully released to all Photo customers, please follow this release announcement thread

Status: Beta
Purpose: Fixes and Updates
Requirements: Licensed Affinity Publisher 2 (registered to an Affinity ID account)
Windows Store: Not Submitted
Download: MSIX Download
Auto-update: Not Available
---
We are pleased to announce that the first Affinity Publisher 2 Customer Beta 2.0.3.1670 is now available as a download from the link above.
Please note: We are working on an equivalent MSI/EXE installer to ALSO be available before the time this 2.0.3.x beta cycle finishes, and becomes a public release.
This beta is an update to the 2.0.0 version recently released to all customers and will form the basis of our first patch for 2.0.0. We recommend that you use this beta in preference to the release version if you are affected by any of the issues listed below.
If this is your first time using a customer beta of an Affinity app, it’s worth noting that the beta will install as a separate app - alongside your store version. They will not interfere with each other at all and you can continue to use the store version for critical work without worry.
---
Known Issues
- PDF Layers can failing to import for opened and placed PDFs. This is a regression over the 2.0.0 release.
---
Updates and Fixes
- New Document: Custom Document Preset order is not retained between app sessions
- afpackage fails to find Resources on Open
- Fixed spurious future version error under certain circumstances
- Improvements with PDF Import and Layers
- Fixes for RTF import - font name discrepancies, fields in footnotes
- Update for HEIF importer
- DWG Import scaling improvements
- Opening and closing chapters in a Book can leave the files locked / read only
- Crash opening a bunch of chapters from a Book simultaneously
- Export Panel UI fixes
- Preview exported PDF fails on Book exports
- Fix for export of Books with Bleed
- Fix for Booklet printing model
- Fixed some tool drawing issues relating to selections across spreads etc
- Pen tool tweaks and fixes
- Fixed hang that could occur composing vertical centre aligned text
- OpenType handling does not respect lookup flags such as IgnoreMarks
- Hit box of scaled text could be incorrect
- Gradients on text strokes don't render unless the fill also has a gradient
- Fixes for line breaking in some odd cases with punctuation
- Merge runs of tabs using leaders
- Resource Manager updates
- Fixed various issues involving handling of placed document files
- Placed documents with bleed can fail to render the bleed correctly
- Light UI Improvements
- Many and various Layers Panel updates and fixes
- Clipboard: 32 bit DIB support added
- Auto Flow Place: Added an option to auto-flow place to replace the content of already populated picture frames
- More attributes are retained when replacing images in frames
- Pages Panel, double clicking does not zoom page to view
- Ensure global colour edits update live
- Select Same Name should only select objects with user supplied names
- New clearer icons for stroke properties (cap, join, align)
- Localisation updates
---
To be notified about all future Windows beta updates, please follow this notification thread
To be notified when this Publisher update comes out of beta and is fully released to all Publisher customers, please follow this release announcement thread
 

Removing the logo will make the Asset invisible in the Asset panel, but you can do it.
It is not possible to automatically load and update the bump map, unfortunately. 

Thank you very much. Really great asset.
Is it possible to speed up the process a little bit more by automatically deleting the logo and loading the bump map?

Hi All,
Well, it’s been a pretty crazy week since the launch of V2!
This has been a real labour of love for us over the last year or so, and I can’t even begin to describe how hard the development team have worked on it. Not only getting the V2 apps launched, but also of course finally bringing Publisher to iPad. 
With this being our first paid-for upgrade there has understandably been a lot of feedback / questions around future updates and our pricing policies. I thought it was worth addressing / clarifying our position on some of these personally...
Updates to V2 moving forward
Buying V2 not only gets you all the new features you have seen, but we have various updates planned – including many more new features and improvements – which you will get for free. This will continue until such a time that V3 is released. We’re not sure exactly when V3 will be, but I can confirm we are not going to move to anything as regular as an annual upgrade cycle as has been speculated.
It’s worth saying too that V2 does include many under-the-hood changes to our underlying technology, and we have also been investing in several new areas of research recently. Some of these haven’t manifested themselves into new features yet, but overall V2 does give us a better platform to develop on moving forward and I’m sure you will be pleased with the updates V2 will receive.
Updates to V1 moving forward
While we did say on the FAQ that V1 would no longer receive any updates, I want to clarify that was about new feature updates. We will be updating V1 to fix any critical problems caused by operating system updates in the future. So if the next version of macOS breaks V1 we will endeavour to fix it. There will be a point in time when continuing to maintain V1 in this way will not be tenable, but certainly for the foreseeable future we will continue to patch. In fact, we have an update to V1 queued up for release very shortly with some fixes for Ventura and issues caused by a recent Windows security / quality update. 
We will update our FAQ shortly to make that clearer for everyone.
Offer period
In case you didn’t see, I’m pleased to confirm we have decided to run this initial launch offer until 14th December to give everyone the best chance possible to get it if they wish / have a decent amount of time to trial it. 
Upgrade pricing
It’s been really hard to see some of the comments about us not looking after our existing customers – we’re pretty devasted that anyone feels like that to be honest. But the fact is we felt our hands were tied somewhat with being able to offer upgrade pricing in a fair way. The main reason for this was App Store customers (which make up around 35% of our userbase). The problems with that are two-fold: firstly, we didn’t have a way from within V1 to validate an App Store purchase receipt to reliably ensure customers who were entitled to an upgrade could get one; and secondly, we could not find a good way for people to get that discount via the App Store. Us pushing upgrade customers to go exclusively via our own site (including customers who were previously acquired via the app stores) may also have put us in violation of App Store Ts & Cs which we were obviously concerned about.
I’m not saying that these issues were completely insurmountable, but any solutions we came up with would be messy, and most importantly could have resulted in some bona fide V1 customers struggling to get validated and claim their discount. We certainly don’t have the support resource here if we ended up needing to manually validate tens of thousands of receipts for example.
The only option we felt was safe to move forward with was a general launch offer, which would guarantee that every V1 customer could get the discount, whether they purchased directly through us or the App Stores. We knew a side effect of that would mean some new customers would end up receiving that same discount – but we felt that was a better option than V1 customers missing out. It’s also worth saying that while there has been some good press about V2, all our main marketing has been via email and through social media to our followers. In other words, we felt ok about it because we knew the vast majority of people who would find out about it or take advantage of the offer would be existing customers. I would be surprised if over the offer period customers upgrading from V1 didn’t make up more than 90% of our sales.
Overall I do believe us giving a 40% discount, along with the addition of the new Universal Licence of course, is offering fantastic value for money for those who want to upgrade. 
However, taking on board some of the feedback there is something extra we can do – we will offer a new free bundle of content exclusively for V1 customers upgrading to V2 as an extra thank you for your support. I’ve seen this suggested by a number of customers and it’s a great idea as it does remove the App Store conflict entirely. 
We’ll need a little time to put something together, but all customers who previously registered or purchased V1 and have since upgraded to V2 will receive a voucher code for this via email as soon as we can.
A comment on no subscription
I do want to say that some of the points above are exactly the reason why software companies move to subscription. Whatever you do with upgrade pricing, you still have the issue of customers who bought the previous version 3 months ago vs. those who have had it 2+ years. Offering perpetual licences also gives the additional overhead of needing to maintain the previous version longer than you would if everyone was on subscription / generally always on the latest version.
We are a small team so some of these complications are not ideal — all we really want to do is focus on developing our latest codebase, push out regular updates and continue with our mission to make great creative software accessible to everyone. 
But it does need to be funded somehow. We know you love our no-subscription model, but there also needs to be a level of appreciation that the alternative is having paid-for upgrades from time to time. That unfortunately comes with its own problems.
All of that said, I have to say we have been blown away with the response to V2 - around 3 times as many people have upgraded in the last week than we expected - and we really can't thank you enough for the support you have shown. More than anything the success of this upgrade puts us in a great place to continue investing heavily in development which is ultimately what it's all about, and we’re super excited to crack on with some great updates coming next year!
All the best,
Ash
This is a duplicate post of a thread that is now locked and moved to the questions forum

And many will pay happily because it works for them.
Best regards!

You eventually will be, when the hardware you have no longer supports the newest versions and you need to buy new hardware to run them.  Apple was originally a hardware company, and they have in part become a services company, but they have never really been a software company - they make their money on their hardware and now on their services, and provide the software to support what actually brings them income.
Serif on the other hand is a software company, so that is their primary source of income.  They need to charge for it at some point or they won't be able to continue as a company.
The fact that they are charging for version 2 is not in any way surprising or unexpected - they have told us all along that they would do that, and even now in the FAQs on their site, they spell out that the updates from 2.x to 2.y are free, but there will be a charge again when version 3 comes out.
This is a common practice among most software companies, and is extremely fair.

Export the styles before deleting and import them after that.

is it possible to have the option to export avif along with jpg and webp?

Hi, I'm trying to transition from InDesign to Publisher and one thing I've been sorely missing so far is the ability to place multiple pages of a linked PDF into an AFPUB document.

In InDesign, there's a "Show import options" checkbox when placing a file, with a consequent dialog window which allows you to choose all pages (or a range) of a PDF file.
So if I want to place a 100 page PDF onto 100 pages of a document, I'll just create a document, add 100 pages, import the PDF, choose all pages and then I can simply scroll and click 100 times to place page after page. Not at all perfect but it works.
Sadly, I haven't found any way to place more than one page of a PDF at a time into Publisher (and I can't even choose which page of a multi-page PDF to place - it always places page 1 which I then have to manually change), which is inconvenient to say the least. Please, can you do something about this?

Maybe because 1-bit does not leave gray artefacts and can be much easily traced by a vector app?

That's absolutely TRUE.

No workarround can replace the flexibility of ID's facing pages spreads.

You can add ! or - or space instead of a letter.

You can also download dictionaries from:
https://www.softmaker.com/en/dictionaries
just change ".sox" extension to ".zip" and unpack it.