Hangman

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

That's exactly what I did and those are the results above... all three using the exact same settings...

The downside perhaps of going down the TIFF route is the amount of pre-processing required, together with file size for no obvious advantage vs using RAW files straight out of camera...
A quick test of all three below with no post processing... The RAW files still have the edge when it comes to shadow and highlight detail with this particular image which can only really be seen when zooming in to specific parts of the original merged files...
Uncompressed 16 Bit Tiff Files - File Size Per Image - 121.1 MB

 
Uncompressed 32 Bit Tiff Files - File Size Per Image - 322.9 MB

 
RAW Files - File Size Per Image - 21.2 MB

Okay I see. Thank you! That's a bummer, but at least the profile was free. I'll see if it works in some of the other programs I have.

It's the options towards the bottom though there appears to be no Default Lens Profile or Noise Reduction options for iPad, though Noise Reduction should be an HDR Merge option...

Only on Desktop as I don't currently have access to an iPad though I'm sure someone else can test on an iPad to see if they experience the same issue and report back...

Hi @MartinN and welcome to the forums,
If you take a look at the ruler settings in your document you can see that the document itself isn't 14.557 x 10.417 inches but rather 10.925624 in x 7.81275 inches and hence when exporting as a pdf using Whole Document these are the exported dimensions.
You also have an Artistic Text element with a width of 232.183756 inches which should ideally be looked at, corrected or deleted if not required...

It looks as though something, somewhere has been scaled and is causing the discrepency between the size in the Document Setup and the actual document size.
I would create a new document at the size required, i.e., 14.557 x 10.417 inches and then copy paste the elements into you new document, scaling as appropriate and taking care of the items sitting way off the page at the same time and then export the file which should then give you what you need.

Hi @Alexandra Péchabadens and welcome to the forums,
Without seeing one of the images in question it's difficult to comment, are you able to upload one of your images so we can take a look. Could you also let us know which printer you are printing to?
I print directly from Affinity Software to an Epson SureColor P600 without issue and with zero pixelation so my initial thought is that the issue isn't with the Affinity software but a look at one of your files will hopefully help in understanding where the issue may lie.

Therein lies the problem, if you have a 10 inch square canvas and you want to add a 0.25 inches to all four sides of the canvas then logically in the Resize Canvas dialogue, with the chain active and the anchor centred, you'd enter 10.5 for the width and hit the tab key expecting the height to auto update to 10.5 but it doesn't...
Original Canvas Width = 10 inches
Original Canvas Height = 10 inches

New Canvas Width = 10.5 inches
New Canvas Height = H * ((W+0.5 inch)/W)
New Canvas Height = 10 * ((10+0.5)/10)
New Canvas Height = 10 * ((10.5)/10)
New Canvas Height = 10 * (1.05)
New Canvas Height = 10.5 inches
In fact any decimal value entered for the width won't update the height value accordingly. My assumption, rightly or wrongly is that this is because Photo is insisting on whole pixel values and despite 10.5 inches equating to a whole pixel value, you only appear to be able to achieve the above when using the pixel unit so e.g.,
Assuming a 300 dpi document, in the Resize Canvas dialogue with the chain active and the anchor centred, switch the units to pixels and enter 3,150 px for the width, hit the tab key and the height will likewise update to 3,150 px. Switch back to inches and the document is now correctly shown as 10.5 inches x 10.5 inches.
Likewise repeat with a 72 dpi document, switch to pixels and enter 756 px for the width, hit tab and the height updates to 756 px, switch back to inches and you have your 10.5 inch x 10.5 inch document.
Whether this is correct behaviour or a bug however I'm unsure as it's always worked this way since V1.

@AS3: In case it helps, here's a copy of your file (minus the broken PDF on page 24) that 2.0 should be able to open
wf-file-recovery2.afpub

Thank you @Hangman, that makes a lot of sense. And thank you as well @MickRose, I think you still misunderstood what I was trying to do but I really appreciate you taking the time to help.
Yeah, this is using the workaround above, because I couldn't find a better one.
This is exactly what I want, and it's really sad it's not possible to make it work. I feel that playing with the color is not really a good solution, because there is not perfect matching between what the text shows and what the image below it has, so I guess for now I'll have to continue using the 1% opacity trick.
But given your explanation of what PDFSandwich does, maybe I can create a tool that will preprocess an existing file and just replace everything with a glyphless font + CIDToGIDMap in the same way, I'll have to brush up on my PDF knowledge, but that should be doable (for next projects, as I mentioned I had to provide something for my client ASAP).
Thanks again!

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

Nice figured I had something messed up in there thing has to be pretty spot on doesnt it no room for error. Thanks for the assitiance on fixing the issue.

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,
Excited to say this week's build is what we consider to be our first release candidate for 2.1. This means we are now at a stage where we are avoiding making any significant changes the code before release (unless we find some critical issue which must be fixed of course).
Fixes since the last beta build are in this post.
Thanks,
Ash
 

Hi @TomAng,
This is a known bug in the current Beta which will be fixed in the next Beta release. You can use Publisher and Photo independently but you can't currently use Edit in Photo or, as you've already experienced, click the Photo Persona within Publisher.
There is a temporary workaround if you need to use this feature which involves a simple edit to the Info.plist file in the Affinity Photo 2 Package Contents. This does however restrict the ability to use the File > Open Recent option but files can still be opened directly from the Finder.

Hi @Metz Apparel and welcome to the forums,
Are you able to upload the file in question so we can take a look?

Thanks. All good. I'm good with altering the linked file and have it updated in Publisher.
I was working on a template where it'd be easier to tweak images as they came in to Publisher, but I can always return to the public releases. 

Thanks for clarifying. That is my expectation as well. My comment was me just getting mixed up by reading this thread in bits and pieces over several weeks and reacting to the post of Max Danger demonstrating a case where it is not working (which your team is looking into) and Hangman’s post that we should not expect balanced dash strokes to work in exported PDFs (which he has since corrected). I see we are on the same page, so I am sorry to complicate the thread.

Ah thanks, I did not know this setting existed!

@Graham Phillips, is it possible that you have the Initial Advance set to Fixed in the Text Frame settings? If not, could you upload a sample file demonstrating the issue so we can take a look...

Hi @EmT,
Okay, thanks for the clarification...

@Hangman
Thanks for that, I've passed it over to the devs to see if the tabbing can be improved with Keyboard Navigation enabled. 
In regard to the query about why Vector files do not have zoomable preview. It's due to how the Vector previews are generated, it is quite a complex feature as vectors can draw differently dependent on their intended final use. It may be something that is implemented in a future version. 

Thanks, I'd certainly be interested to know as I can't think of any practical reason for Vector files not to be zoomable, more so because they currently are with no obvious detrimental effect.
Perfect, disabling it fixes the issue thank you...