kalee

Ldina, I gave your macro a quick run on a couple of 50 year old negs I have played with before. It works fine as a quick and dirty process for me - and you can quickly dump another image on top to see if the tweaks work on that one the same. I hate old colour negs, as I usually shot slides and B&W, but this combination is all I need. I do not compensate for light source, as these are already scanned, but will keep it in mind for future scans. Thanks again.

Thank you for your efforts, Mike. You have produced a very useful reference. Although I have already produced a large illustrated book using Publisher, there are areas of the program I am not comfortable with.

Ldina, I think your rev A workflow, which pretty much nails the process. It is not too dissimilar to how I had been trying to process some of my old negs. Thankfully I do not have too many! You have produced a well thought out tutorial, which is nice to see. Selective colour adjustment is, to me, one of the most useful tools - used carefully The thing I miss most about Affinity is the lack of black, grey and white eyedroppers, which I used for many years in PS. At least Affinity is very flexible in how one does the adjustments. Thank you for your work, as it will really come into its own when I next end up converting negs - and forgot how I did it!

I have the same problem with Publisher on win10. It had previously run well on v 10.4, until adding another page recently (never a problem before with this file) Updated to 10.5, and still crashes out when adding another page - with or without a master page attached.

Certainly not my experience in win 10. Using CTRL-J will copy and paste to a new layer. CTRL-C and CTRL-V will also copy and paste the selection.

I am using Publisher 10.4 on windows 10 to produce a book, which also contains over 300 photographs. This is nearing completion, so I am interested in whether the 'Fixed possible rendering issues with Raster elements' plus any other tweaks in the latest release is going to be beneficial to commercial print output via press-ready PDF? Naturally I am nervous at updating the software at this stage, as 10.4.1198 is stable. For info, all of my images are flattened before insertion into Publisher. Many thanks, Kalee

To me, the panorama tool would seem to be plenty good enough. Of more concern are core functionality items. Currently, every time I look on the forum, it is people demanding more an more items to be incorporated - because it is on adobe. The raw converter is pretty poor, and is something that really does need addressing. With a better raw processor, you would also likely get better panoramas as a result?

I cannot help but think that you expect too much from the panorama function. Personally I have been quite impressed by the Affinity stitching. Expecting it to handle extreme light levels with one button seems unrealistic. I would not be happy with your lightroom example, and would expect to replace, or work on the sky.

That sounds like a good tip to remember, if the file size suddenly goes stupidly high. Thanks for sharing the workaround.

Not actually dimensions. The image was exported nominally at 90mm x 60mm at 300dpi All of the images were exported with that same procedure, but with different dimensions, as required. On exporting from Photo, the dimensions showing up would stray slightly from the nominal size chosen (following earlier cropping to format), so that would indicate to me that the 300dpi was the overriding factor. However, when importing into Publisher there can be this anomaly.

I am putting together a heavily illustrated book for print using Publisher 1.10.4 and I am seeing inconsistent dpi readings for the photos I am placing. For some reason, a good number of pictures are showing 299 dpi instead of 300 dpi, despite selecting 100% image size, and manually adjusting the dpi figure. Sometimes it is either horizontal or vertical readout that is wrong, while the other is correct. I am concerned that this may impact when offset printing. Has anyone else experienced this practically? Maybe it doesn't really matter, but I do not know. All of the images were processed in Aff Photo, and output at 300 dpi, so there should not be an issue with the images themselves. I have attached a screen grab showing a typical readout, and the placed dpi reading in Resource Manager. Any thoughts?

I am thinking that this problem has been pretty much dealt with for linked images, given the file sizes I am experiencing currently - but will find out how slow it all becomes when I add in all of my finalised pictures.

That could be useful. I could replicate my problem at the time, as well.

I did have an issue with file size bloating on windows 10. There are over 300 images in my book, and they are linked. Many of the images are mostly placement size. The file size suddenly went from around 17MB to over 80. Had a play around at the time, and found it was obviously an image that the program did not like. Can't remember if it was a PSD file or a Canon Raw file, but changing it to a jpg sorted the issue for me at the time. Hopefully, when I eventually load all of the full size file, I can still work on the file! Currently it is holding at around 20MB for a 200+ page book.

That is what it seemed to me, Lagarto. The option to convert to this profile only appears if you load a suitably profiled image. As long as it works, it will solve one of my problems, thankfully!

I have been struggling to achieve K-only greyscale images in a book I am writing, which is heavy in both colour and greyscale pictures. Previously I produced one when I used Photoshop, but dot gain profiles are not included with Affinity, and I see no obvious way to import them. This is a pain, as I am a long way down the line in laying out the book. Do any print experts know if the relevant dot gain profiles are actually available? Now here is the odd part - but is it a solution? With an image I want to convert, only the D50 option is available in 8bit grey - but if I load an old image converted using the dot gain I want into AFPhoto, the 15% dot gain conversion option I need becomes available in the program! Following this conversion, loading it into Publisher sees it recognised as the DG15% ICC profile in a grey colourspace. Is this a useful find? I do hope so. K

It is not an affinity bug, as cloning darker colour onto an empty layer does not work in my book, because there is nothing on that layer for it to be darker than.

I had a look at this problem, and you need to think a different way. Add an empty pixel layer for cloning, if you need to - but set it to darker colour. Now just do the cloning with the mode set to normal. Problem solved.

Basically Dan, I think I just had to turn the graphics acceleration off to stabilise the system, as per previous releases. No real issues with this release in recent times, other than the usual hoping for certain additions to the software. 🙂 Keith

Yes Alfred. Just checked, that is correct, thank you.

There is always more than one way to skin a cat. This works for me, and your ligature comment did not work for me. When time is tight, you do what works. Well, I do!

After reading of this problem, I too thought there must be a problem with Affinity, as I appeared to be able to replicate the issue.. HOWEVER, the problem would seem to be a case of not using the help file! You need to use kerning for the f and l characters, which means that you need to click between the two characters - and can then easily adjust the spacing.

Hi, I have just updated to 1.9.2, running win10, and Photo has crashed twice when using a curves adjustment. v1.9.1 was running fine, but all I had done to the image was a crop with slight rotation prior to the curves adjustment.

Thank you very much, Gnobelix - I would never have found that in years if you had not posted that screenshot! My 15 inch display does not show the protect alpha setting. Had I not then clicked the double arrows at the end of the toolbar, I would never see brought it into view. Being as the other two programs function normally, I was going down the wrong track in my thoughts. Thanks again.

I am running the latest 1.9.1 suite on windows 10. In photo, I realised that I could not use the brush tool on a layer mask, to either mask or unmask the layer. This is repeatable on an existing or new document. I have uninstalled, and re-installed from a fresh download - same result! As I have 1.9.0 on another machine, I tried that one, and all is fine. Updated it to 1.9.1, and all is still working. Going back to my original laptop, I then tried the same thing in both Designer and Publisher - and the brush behaves as it should do on a mask, but not when I went back to Photo. I have since realised that my paint brush does not work in Photo on a blank pixel layer in normal paint mode. It needs a fill layer to actually function1 This has got me baffled, so any help appreciated. Unfortunately I have no idea how long this problem has existed, but wonder if there is some odd interaction between the three programs? It is not a case of blend mode stupidity - it is all set to black or white in normal mode, with brush parameters checked.