David in Яuislip

If you can demonstrate that the Photo correction is different for the same lens used on a full frame body and a crop body then carry on trying to modify the profiles to cope with both. I think that it would be a pain to select the right profile during development but then I'm not doing it. If you are serious about lens correction I recommend a trial of PhotoLab. I use it with Viewpoint, it's easy and produces superb results. If I only had Affinity Photo for raw development I would go back to shooting rgb files from the camera Hopefully a Serif expert will be along soon I have nothing further to add, good luck

Gotta think of the forum server space 8,533 GradMap.afphoto 4,618 GradMap.psd

Try a gradient map, a little fussy to create but you get to choose where the tone splits are rather than rely on posterise which I've never had much luck with. The gradient map is in the psd as they can't be exported, at least I don't know how to GradMap.psd

Your previous raw for the EF 28mm shows conflicts in the exiftool report: Cropped Image Width : 3960 Cropped Image Height : 2640 Focal Length : 28.0 mm (35 mm equivalent: 27.2 mm) -- my note: 27.2/28=0.971 Scale Factor To 35 mm Equivalent: 1.0 Sensor Width : 3960 Sensor Height : 2640 Sensor Left Border : 0 Sensor Top Border : 0 Sensor Right Border : 3959 Sensor Bottom Border : 2639 I suspect that it's being caused by using the crop mode, you could ask on the exiftool forum or use Canon's raw developer and see what that shows You could experiment by changing the lens xml to <camera> <maker>Canon</maker> <model>Canon EOS 5D Mark III</model> <mount>Canon EF</mount> <cropfactor>0.971</cropfactor> </camera> <lens> <maker>Canon</maker> <model>Canon EF 28mm f/1.8 USM</model> <mount>Canon EF</mount> <cropfactor>0.971</cropfactor> etc </lens> but I think you'd be wasting your time and this would screw results using the same lens in full frame mode 35 mm equivalent is only stated as a convenience, I doubt that any software uses it so whether it's right or wrong doesn't matter As it's a full frame lens on a full frame body I'd use a crop factor of 1 and ignore metadata

I watched the video but still don't understand what you need to achieve. The video discussed document resize, canvas resize, sharpening and allsorts If you can state where you are starting from are all images the same size, if so what size source colour profile and where you need to go destination dimensions destination colour profile output for print or screen? then maybe someone can help. Did you try my suggestion above using a New Batch Job, if so what problem did it cause? It may be useful if you export your macro from the macro panel and post it here. Generally after a resize an image will need sharpening. If you use a New Batch Job to resize then you cannot apply a sharpening macro during that process, you will need a second New Batch Job on the resized images to apply final sharpening using a macro. For reasons best known to the programmers any macros applied to the images are run before the resizing The images below were done two ways i) resize manually and apply a sharpening macro ii) New Batch Job applying the same sharpening macro and resizing to the same size Stacking these two outputs and using Difference Blend mode on the top shows that they are very different Photo macros are pretty limited in what they can do and can be frustrating, they are not like Photoshop actions and usually imagemagick is a better solution

Open the file in a text editor and delete the first line <?xml version='1.0' encoding='ascii'?> or you can change ascii to UTF-8

I don't understand your meaning so I guessed I certainly understand that concerning macros If you need to do this job on various different sized images that are to be resized to 2160 high then I would record the macro to flatten convert format/ ICC profile duplicate but use it in a New Batch Job where you can specify either height or width with the A box ticked

Aha, cannot change dimensions if resample is off so Plan B Use the transform panel with the Lock aspect ratio chain clicked on Type *2<enter> in the width box then Document/Unclip Canvas Both approaches work here

Make sure that Resample is ticked in the resize document dialog

Make sure All Pages is selected in the Export dialog Here I have a file PhotoWords.afpub which has 3 pages After export 3 files are shown dir /b PhotoWords*.png PhotoWords_1.png PhotoWords_2.png PhotoWords_3.png Cannot help with the font problem

Affinity csv import doesn't allow sep=; at the top. I tried it earlier to test here but it assumes there's another record name;date of birth "John Doe, xyz";"15. September 2015" should've worked, as it doesn't I would check the encoding, if it's not UTF-8 then convert it, if it is then I give up Tsv might be an alternative but I've never got that to work

String fields with commas must be enclosed within quotes. LibreCalc does this automatically but there are many flavours of csv, it should look like this in a text editor name,date of birth "John Doe, xyz",15. September 2015 "Bill Smith, abc",29. November 1963

Ja natürlich You can create a customised list style Look at what I've done in the attached file, check the style under Bullets and numbering To use it, click with the Art text tool, type a space, assign the style Then click again, type space and the next number will appear If you want the units columns to align then you'll need more styles but that's probably a bit fussy FiguresNumbered-2.afpub

<gemitus> O cara, o cara, altera cara! </gemitus>

My use of Latin was limited to quod erat demonstrandum and I don't use that much these days Accipio auctoritatem tuam - fidem Google

My previous experience with hyphenation dictionaries in the user area is that they have no effect The program comes with hyph_la.dic as Mike notes It's the only file in C:\Program Files\Affinity\Publisher\Resources\Dictionaries\la I have added la.dic, la.aff & hyph_la.dic to C:\ProgramData\Affinity\Common\1.0\Dictionaries\la\ I created a new style based on Body but with the Language and Hyphenation set to Latin As standard the word suspiramus hyphenates thus: su- suspi- suspira- suspiramus After adding sus5p5iram5us to user hyph_la.dic it now does this: sus- susp- suspiram- suspiramus Quid mirum But apart from that is it correct to hyphenate Latin at all? The language was pretty dead by about 700 AD and Gutenberg didn't print his Bible until 1455

I create a circle and duplicate it To the bottom circle I add art text Same for the top circle Now I can only select the top text unless I turn that layer visibility off If I change the order of the text layers then I can select either one with both layers visible, no need to keep changing the layer order Same behaviour in V1 Photo and Publisher

I think that this is displaying the embedded preview, you'll have your work cut out getting this result from the raw

I suspect that the raw files contain metadata indicating the film simulation. This will be applied by those programs that recognise it otherwise you just get the raw data. I doubt that Photo will ever be able to process all of the various simulations of all of the cameras out there

It imports ok into V1.10.6, not that I will ever use it, it would be like going back to a dial-up modem

'Course it ain't. Use the Help to understand the difference between Masking (raster) and Clipping (vector) then just do it 🙂 Don't use Photo for the pen work, I used Publisher because Photo pasteurises the pen line, I expect that Designer will work as well

Trace around the item with the pen, fill with a solid colour and nest the shape into the clipping position. For the cutouts make separate paths and combine with the main outline using Layer/Geometry/Merge curves, here's a quick example Reactor.zip

ImageMagick info: abridged report Format: TIFF (Tagged Image File Format) Geometry: 1280x730+0+0 Resolution: 1x1 Colorspace: sRGB Type: Grayscale Endianness: Undefined Depth: 32/16-bit Channels: 3.0 Channel depth: Red: 16-bit Green: 1-bit Blue: 1-bit Channel statistics: Pixels: 934400 Red: min: 0 (0) max: 230614 (3.51895) Green: min: 0 (0) max: 0 (0) Blue: min: 0 (0) max: 0 (0) The only way I can get that as 32bit into Photo is to do magick 32bitBedDepth.tiff 32bitBedDepthIM.exr which produces a monster file so here's a 16bit png which looks the same, zipped to avoid forum mangling 32bitBedDepth.zip

As a guess, when you want to replace an existing profile it must be in its own file. If you want to add lenses then they can be combined as you did, it's all voodoo Vignetting correction looks excellent, hope you'll send this to lensfun as it's far superior to the crap they have at present CanonEF28mmf1.8USM.xml

I'd advise a trial of DxO Viewpoint, also integrates with Photolab, dead easy and superb results