Reggie1958

Hi Fraser, I have made such a collage ... no expert mind I was asked by a friend to crate a collage of photos she took with alphabetical letters as her insperation .. that's the English alphabet, be interesting trying to get the letters Ö Ä Ü in photographic form .. now there's a project. Anyway..... I had a bunch of RAW files from her and used Affinity photo to create the collage; I found working in 32bit (HDR) colour format for each file made for a truely massive .afphoto best to export to 8 bit JPEG highest quality .. still big files .. or 16 bit Tiff files if you have the computer to handle the massive files. I worked in the highest resolution my computer could handle with the converted RAW filies into 16bit Tiff files then I created my collage .... we are talking a simply huge .afphoto file .. then when done I exported the final document as an 8bit jpeg file best quality. Thus the workflow was to maintian the highest resolution until the end export for printing .. that's another story .. Hope that helps and if there are any experts out there who want to give thier wisdom I'd be grateful :-D Reg.

Just to recap and to be pedantic .. if you open a jpeg file -> use the develop / photo persona to change things -> and hit save, yes the orignal jpeg file is overwritten with a new jpeg file with the changes you did in the develop / photo persona .. no warning it just does it. if you open a jpeg file -> use the develop photo persona -> and hit save as you can only save as .afphoto file type Other means of saving are available ... i.e. export persona; however if you try to overwrite your jpeg in export persona with the same filename you do at least get a warning and request for action. I'm sure there are other combinations I haven't come across yet, perhaps we need a matrix of the combos to make it clear for folks .. addition to the manual perhaps ... or have I missed it? Cheers Reg,

3 RAW files: one PEF file (Pentax K3 full size) One DNG file (Pentax K3 Full size) one ARW file (Sony A580 Full size) Various lenses. Hope they help :-)

Indeed so, the quote from my post was in fact a summary of someone else's post and not my words or opinion, however yes my post does in effect back up what you have quoted

Me too, a menu option to close all would be great :-D

+1 me too, Close all would be nice :-D

Hi Affi, Welcome, and I wish you a happy new year. To paraphrase your post: You hope that Serif will increase the size of the affinity development teams to help speed up development, to include many more major features as well as improving the current functionality's robustness, reliability and usability. Version 3.0 you say? Can I ask what are you expecting in version 3? also when do you expect version 3? We are still on version 1.6.x and has 1.x versions bring significant change I can't really imagine what version 3.x would have. My opinion of increasing the size of development teams is that it helps in the short term but there is a point of demising returns on investment. Is this a sensible strategic business plan for Serif? I can't tell but I do know that the opposite is true. That is diminishing the team to a certain point would render it ineffective for new feature development too. The balance of team resource strength versus commercial achievement is a tricky one for the business to get; but of course this also depends on the actual level of funding the business has at its disposal; which might not methinks be as much for say Apple or Adobe. There is no harm in asking for features, in fact it is healthy but I also think we need to keep in mind the size of the company too. By the way what exactly do you want for RAW development? You say Massive RAW development; I'm just interested what that might be. Best regards Reggie

Err isn't nichts German for nothing? just saying ...

Great brushes, thank you :-D

@MEGraphicDesign Yes I'm looking forward to that too, the last I got from the team was yes it is in pipeline. Yes I too would like the software to be kind of along the lines of Bridge in the sense it doesn't have to maintain a database. Update: I've seen a post on another thread posted yesterday that confirms that the team are actively working on an asset management app.

@Ben Hi Ben I can share your feelings fully and add my support to your sentiments: being a software developer for over 30 years for companies such as Motorola, Smiths Aerospace, Cardinal Health - Carefusion (Medical technology) etc.. people casually making sweeping disparaging remarks because of a single point of functionality (which might be important to them) is painfully and outrageously unfair, especially if it's on a Beta release. Like my fellow developers in the Affinity team, in all my time we have always been super careful about releases, the amount of testing and retesting in all phases of the development cycle is staggering. This is hard work especially if you have a small team (we can't all have the resources of Motorola, Apple, Microsoft, Adobe ... to name a few ). Software engineering is not just about coding, Architectures, Frameworks, design (yes it really is designed), their are standards to conform to, then there's unit testing, integration testing, system testing ... and oh talking of testing all this done for testing frameworks and tests too ... then there is the constant software configuration issues .. so yes I can understand your frustration and I think you are doing great work.

Hi RJ21, I have used Affinity photo for a number of years now and I have never looked back as far as Affinity photos is concerned. I have recently purchased Designer too, there is a little cross over but they excel in different things so I say do it. The selection tools in both apps are very good if used correctly I find. The macro feature of Affinity Photo is excellent too, I use it frequently and have made many a macro to make life easier. Cheers Reggie

@MEB Wow quick response :-D No probs MEB as long as it's still logged. I feared it might have been a fix that has over time been unfixed by such things as the magic of software configuration management or some such machination of software development ... yep been there .... small team and a zillion demands with prioritisation always keeping lower impact issues under the radar. You are doing a great job, thank you.

Hi @MEB and @sinbad Looks like we still have the same issue peeps. I was doing the same thing as Sinbad but for AD 1.6.1 Beta: That's December 2017 ... oh merry Christmas and a happy new year by the way :-D I have the same issue so I am glad I found Sinbad's report so we can at least keep these related issues together. I was following the beginners tutorial as Sinbad was and came up with the same issue .... Yes using the work around worked; that is, converting the nodes to Smooth nodes did work. Indeed a bit awkward and you wouldn't twig the solution by intuition either. However, still a bug? I'm happy to share files with full history saved if it helps. Regards Reggie

Hi Evtonic, No a Beta is not just for new stuff, a Beta is simply a phase of testing to identify issues in the user domain, people who agree to taking a Beta are essentially user domain testers, rather than internal formal software unit, integration, regression etc testing. In a candidate software build internally, there would be at the start of the project, identified issues (bugs), or new features to which the team has been committed. The beta is a useful tool in the testing phase and we as contributors are Beta testers and on the way we may pick up not previously identified issues. When we report these issues to the team we are helping not only to improve the products but also give a confidence level to the quality, robustness and reliability of the product. It is only of any use of course if report the issues.