walt.farrell

In Photo (1.6): Document > Color Format > Grayscale (8 bit) or Grayscale (16 bit)
In Photo (1.7): Document > Convert Format/ICC Profile...  and set Format to Gray/8bit or Gray/16bit
By throwing away the color information I would expect the file to become smaller, but I haven't tried it and won't predict how much smaller it might get.
Note that there are many ways of converting a color document to b/w, and some will work better for some photos than others. So to get the best b/w image you might want to use a different approach than simply converting the document to grayscale.

Hopefully this can clarify the issue and also clear up the concerns that Photo is discarding or throwing away anything outside of sRGB:
RAW files opened in Develop go through an image processing pipeline, during which the colour information is extracted and processed—the colour space used for these operations is ROMM RGB because it provides a suitably large resolution and enables colour values to be saturated and manipulated without clipping to white. This choice of colour space was introduced in version 1.5 where there was a marked improvement in RAW files with intense colour values (e.g. artificial lighting).
However, the actual document profile is in sRGB—this means the final colour values sent to the screen are restricted to sRGB. Is this deficient? Yes, and there have been discussions about how to tackle it without risking further complication for people who don't use wide colour profiles.
There is a silver lining though. RAW files are developed in an unbounded (float) colour space, which means all the values that fall outside of sRGB are not clipped or discarded. If you were to then set your output profile to a larger colour space like ROMM RGB, these out of bound values can be accommodated by the larger resolution of that colour space. Essentially, you can avoid clipping values outside of sRGB when clicking Develop, and you can get them back once you're in the Photo Persona: the issue is that you can't see these values within the Develop Persona.
I've experimented with one of my photographs of some intense lighting to back this up, and have attached it to this post for people to experiment with. I've also compared the results versus Photoshop CC 2019 (where you can set the colour space and it will actually affect the view transform) and, minor processing differences aside such as sharpness and lens distortion, have been able to match the intensity of colours. For Photoshop I also used ROMM RGB and increased saturation directly in the Camera Raw module.
Here's the RAW file for you to try out:
_1190462.RW2
Steps for this experiment:
Enable Shadows/Highlights and drag the Highlights slider to -100%. Avoid any colour or saturation adjustments, add other adjustments to taste (e.g. noise reduction). Enable the Profiles option and set the output profile to ROMM RGB. Click Develop. Once in the Photo Persona, add an HSL adjustment and increase Saturation all the way. You'll be able to dramatically saturate the image without losing resolution. If you close and re-open the RAW file and try to increase the saturation within Develop, you'll notice that the colour values are restricted to sRGB—however, even with values at the limit of sRGB, you can still set the output profile to ROMM RGB and then increase them further once in the Photo Persona. And below are two images, one still in ROMM RGB, the other converted to sRGB. I'm not sure how they will display on the forum (and whether the forum software will process and convert the colour profile—hopefully not!) but feel free to download both and view them in a colour-managed application or image viewer. If your display is capable of reproducing wide colour gamuts, you should see a noticeable difference between the two.
[Edit] OK, that didn't work, the forum software converts to sRGB and ruins the comparison. Here's a Dropbox link to the JPEGs and RAW file where you can download the original files: https://www.dropbox.com/sh/aof74w94f6lm3d2/AABXE2OJMfk__kjA_jb6vwmia?dl=0


 
Hope that helps!
James

See this thread for absolute values, back in 2014/2015, I don't think it has changed
https://forum.affinity.serif.com/index.php?/topic/951-document-size-limit/
 

Were some of them, perhaps, pixel brushes? If so you won't see them unless you're in the Pixel Persona.

All except your first two posts have been made on what is the weekend for Serif (who are located in the UK, primarily).
The first two are somewhat unfortunately timed, as they occurred shortly after Serif returned to work after a company Christmas break that ended on January 2, so they're probably still catching up.

If that asset is an empty picture frame then "replace image" should not be needed, as it won't have one. Just use the Place Image tool to select the initial image, and click in the frame with the cursor, as usual.

You seem to be equating quality with sharpness.
From what I've read, some images will benefit from becoming sharper, but others will suffer. I think the user really needs to make the choice when additional sharpening is being added.

Walt. I'm on Windows 10, printing to an HP Laser Jet Pro MFP M225 PCL 6. I previously used an HP Laser Jet 5. I cannot find any print preview Function in the printer properties. The predecessor to Affinity Publisher was Serif PagePlus, I had PagePlus X9 which might have been the last iteration of that product, and it contained a full screen print preview that was as good as a proof print. Until Affinity publisher has something like that, I can't see using it.
!!! I checked my Canon color inkjet, and that DOES offer a nice preview. (This is news to me!) But my HP LaserJet does not.

Hello @ekweb,
there is no known time schedule if and when this will be added. But I assume they are working on something in that direction.
Currently it is not possible to place a picture frame on a master page that then has different content on different pages that share the same master page. Master page items are common to all pages.
If you want to create some kind of standard frame that can quickly be applied to many pictures you can use Assets. Create a picture frame with all the decoration you want and add it to an asset library. Then you drag this on your page, switch to the Picture Frame Tool and click on 'Replace Image'. Perhaps you have to adjust position and size of the image. That's it.
Additionally you could have guides on your master page to exactly position the picture frames on all pages.
An alternative way would be to place a picture frame with all the styling on the master page and place the picture(s) themselfs on top of the master page in the layout. As long as the picture frame does not have features that need to be visible above the image this could work also.
I admit, both ways are workarounds 
d.

If you purchased from the Windows Store, then as long as you logon to the Windows Store on your desktop, using the same Windows identity as you used on your tablet, you should be able to download it again. After signing in, click the "..." icon on the upper right, choose My Library, then click on Owned, and you should find it available in that list to be installed.

Welcome to the Affinity forums.
The Mac and iPad versions are sold and licensed separately. You will need to purchase the iPad version if you want to use the application there.
Via Google Translate:
 

Yes, assuming it is a brush type compatible with all the software. Affinity Photo, for example, does not support vector brushes.

PSD is not really a standard; its format and major features are merely understood by many different applications. It's really owned by Adobe, and there are features in it that only Adobe understands and that are not documented for others to use.
Edit: For example, editable text layers are not fully documented, which is why Affinity can't create them.

I think you'll find that you can Export a TIF from Affinity Photo and it will maintain almost all of the Affinity data, including those layers, but only Affinity will be able to read them. Other applications will just see a flattened copy of the image.

Not completely true. If you Open a .jpg, .tif, or .png file you can edit it in Photo and Save it (overwriting the original file), as long as you have not created any new layers, or have flattened any that you created. What you cannot do is Save As and end up with a file of another name and the same file type. For that you must Export.
For your 16-bit TIFF question: It will be saved as 16-bit, as that is what it is. It will be saved as compressed, because Affinity compresses all TIFF files, but the compression is lossless. You will not lose any image data or fidelity.
In the 1.6 versions of Affinity the compression is LZW, which may actually make your 16-bit TIFF files larger when "compressed". Serif has changed the compression method in the 1.7 versions (now in beta) to a different lossless version that they believe will be compatible with more programs as it's the one that Adobe uses. They still give the user no choice about whether to compress, but I suppose they may, someday.

The Affinity programs use Hunspell, and you should be able to install any Hunspell-compatible dictionaries yourself.
For example, you could download the LibreOffice Croatian dictionaries (hr_HR.aff, hr_HR.dic, hyph_hr_HR.dic) and use them. If you look at your Affinity Preferences, Tools panel, you should see at the bottom a line that says "Additional dictionary folder". Just open that folder, create a new folder in it named hr_HR, and place those 3 files into the new folder.
Once you've done that you should be able to specify Croatian for both spell-checking and hyphenation.

How about Preferences, Miscellaneous, Reset Brushes? (Or pressing Ctrl while starting and choosing Reset Brushes.)
If those work (as I suspect they would) that would be simpler than mucking about in the file system.
(Of course, it will also reset the pixel brushes, which perhaps you were trying to avoid.)

Your use of "Develop persona" suggests that you're talking about Affinity Photo, but Affinity Photo does not use sidecar files. (You're right that the original RAW file is not changed, though.)

Yes, assuming it is a brush type compatible with all the software. Affinity Photo, for example, does not support vector brushes.

As you say "upgrade" I presume you already own both applications. In that case the upgrade to 1.7 is free. All upgrades in the 1.x range are free. We will only need to pay when Serif releases something in the 2.x range that we want to buy.

No, Publisher does not offer that capability today.

Lines are a kind of object that you draw. A stroke is a border around an object. You do not draw a stroke; you generate it around the object.
As they are different things, used differently, they deserve separate terms to avoid confusion when discussing then.

Serif staff have said that they will prepare a roadmap for Publisher after it leaves beta.

Lines are a kind of object that you draw. A stroke is a border around an object. You do not draw a stroke; you generate it around the object.
As they are different things, used differently, they deserve separate terms to avoid confusion when discussing then.

Serif staff have said that they will prepare a roadmap for Publisher after it leaves beta.