glenbarrington

Microsoft and I are not headed in the same direction. I was a fairly happy ACDSee DAM user in Windows. My mac Mini 4 won't arrive for another 5- 10 days or so. But I'm contemplating Software. I'm probably going to use Affinity Photo for Mac, but I know I need a DAM, I'm too used to the conveniences of a full featured DAM but I refuse to use Adobe anything, so Lr is out, and I don't like it's raw development all that much anyway. I thought Affinity Photo for Windows V1 did an OK job on Raw, but it shone bright as a bit mapped editor. I'm hoping many of the V1 issues will be resolved in V2. There just aren't many non subscription alternatives to Affinity Photo out there. Luckily, it's a pretty good product overall. How do the successful Affinity Photo users deal with the lack of a front end photo manager/DAM? What do you all use? Are there any things I need to look out for on the Mac? Or, possibly, integrating Affinity Photo for Mac with a True DAM. If you have a DAM with Raw Development, do you tend to use its raw tools, or Affinity's raw tools. Any comments and advice is greatly appreciated. This is a major question in my mind, I've got too many photos to use a photo browser, I need something with a halfway decent database attached to it. Either an SQL or Hierarchical Data Base would work for me. Thinking about the following "Front End" products based on my Windows experiences: On1 - an 'OK' photo manager with some extra stuff,but not a true DAM, IMO. ACDSee Photo Studio for Mac - It's just the DAM and the Raw developer, and I assume it will allow me to use my prior knowledge. If it has "reasonably" good integration with Affinity Photo 2, it might work for me. DXO PhotoLab (superb output quality esp raw, but in many ways, it's more a manager than it is a true DAM. Capture One - superb output quality esp raw, but in many ways, it's more a manager than it is a true DAM. Anything you can add would help very much.

I've started working my way through the book. I'm the sort who likes a structured learning environment and this is quite good at that. I've learned quite a bit by just reading about the user Interface even though I consider myself quite experienced when it comes to figuring out a UI. Highly recommended.

Thanks I wondered about that, but i'm pretty sure you've had my CC info since PhotoPlus 7, no problems yet. BTW, I miss that old informal, not always for business, user's forum from that era. It was a fun destination back then.

Wouldn't they already have your CC info from when you bought an Affinity product?

I'm "reasonably" familiar with the use of brushes in Affinity, but I suspect i am only tapping the surface of how they can be used. Does anyone know of any tutorials or articles that address this? I'm looking for material that helps stimulate my creativity as much as I am in increasing specific skills. So I guess I'd be open to elearning sources for software other than Affinity Photo so long as what is taught can be applied to Affinity Photo.

Perfect answer in my eyes! Thanks. As an aside, in spite of the fact that Affinity Photo is most definitely NOT perfect, I am growing quite fond of it as an editor. The user interface can be a bit intimidating when you first see it, but once I jumped into the thing, I realized it's not THAT different from other graphics products with a tabbed user interface.

Does this still apply for Affinity Photo for Windows?

Mark, I am now unable to reproduce the issue at this point. Though I clearly had the issue twice. At the time, I had Chrome, ACDSee Ultimate 10, Affinity Photo for Windows, and PaintShop Pro X8 running contiguously. Just having them up and running doesn't seem to trigger the issue, there must have been some sort of combination of steps and processes having been run in a particular order that triggered it. I doubt I could recreate all the steps at this point. So I doubt this is anything that needs to be prioritized as a fix. My apologies for raising a false alarm.

I was writing an article on comparing Affinity Photo's HDR utility to Photomatix Pro 5.1 and PaintShop Pro X8's HDR utility (an honorable third place) and discovered a bug. I tried to send a SINGLE raw photo through to the Affinity HDR utility, and it locked up the entire program, I had to go through the Windows 10 task manager to kill Affinity Photo. It's OK not to be able to handle single raw photo, but I think the proper behavior should be to trap for a single photo and not let the HDR utility go any further until the user either backs out or adds another photo (sometimes people's mouse fingers get 'twitchy'!) Just do a Google search on "Glen Barrington My Dynamic Range" if you're curious about what I wrote.

Then Affinity is doomed. It might struggle along for a few years but it will become a 'me too' product. If you intend to break free of the hegemonic stranglehold Adobe has on the computer graphics software industry, you NEED the support of Apple, Google, Microsoft, ACDSee, and the other software publishers to create the mindset of inevitability and superiority. Your decision is just plain dumb.

It's good that the Beta Does NOT replace the 'official' commercial version but instead creates a separate installation. I wanted to try the Beta, but didn't want to risk screwing up my 'official' version, and I can :)

Again Thanks!

Everything I've found on the Affinity pages directs me here. I had a problem with Malwarebytes 3 that I didn't notice until after I installed Affinity Photo 1.5. So the logical thing to do was to uninstall Affinity Photo to see if that helped. It did not, so now I want to reinstall Affinity Photo but the install utility won't accept my Product Key. I have a screenprint proving the product key registered to me, and the the key I entered are the same, but obviously I would not post it here, since there isn't a secure and private way to share that with the tech support people. Can some Serif/Affinity people help? Never mind! It was a moment of stupidity on my part I had a copy of Designer loader on my HD that I originally mistook for Photo. The installation appears to work fine now. I have since deleted the Designer loader to avoid that mistake in the future. BTW I know I'm not the only one who gets those titles confused from time to time. It might not be a bad idea to develop some sort of design convention to help give those products a bit more 'separation' in people's minds!

Thanks guys! I think I might change the color engine in ACDSee to Microsoft ICM and see if that brings them any closer together. Unfortunately Little CMS and Microsoft ICM are the only two color engines ACDSee supports. Does anyone know what engine Affinity uses? They, (ACDSee and Affinity) aren't radically different from each other, I doubt if I would have even noticed them not matching if I hadn't gotten a wild idea to officially check, but once I did, I thought ACDSee was a bit 'crisper' and brighter in color and tonality.

Most plugins wont auto install themselves into Affinity Photo, it's too new. So you have to tell Affinity where to find the plugins yourself. Under "Edit|preferences|Photoshop Plugins", in the text area labeled, "Plugin Search folders", add the following text: "C:\Program Files\Topaz labs\Topaz DeNoise 6" "C:\Program Files (X86)\Topaz labs\" Don't add the dot in the front or the quote marks. The first will take care of DeNoise 6, which was rewritten last year, and the second takes care of the rest. Warning, if you have installed them in a non default location (i.e. somewhere else), you would enter THAT location. For the inevitable NIK Tools question enter the text below: "C:\Program Files\Google\Nik Collection"