glenbarrington

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"

I'm trying to figure out how to integrate Affinity Photo into my ACDSee Ultimate 10 workflow. And the default values for color management makes the color and tonality fairly close between the two, but they aren't really the same. I prefer the rendering in ACDSee a bit better than Affinity. Color management has always been a big gray area for me, I never feel comfortable in anything I do along those lines. And any changes I made to the Affinity Panel didn't seem to make a difference, so I am reluctant to go any farther and screw things up any more! Can someone review the two color management panels in the screen print below and make suggestions on how to bring the two a bit closer together?

Ahhh! Thanks!

The Mac based tutorial demonstrates the use of an automated inpainting tool from within the panorama 'wizard', but I haven't been able to get it to work. I have been able to use the inpainting brush from within the editor though (VERY Cool!). Has anyone else had trouble with this?

Well, fast is nice, but I'm willing to wait a bit in order to catch as many errors and omissions as possible!

Without explaining this ON THE SCREEN, you are going to lose an enormous number of sales. I almost gave up and only then decided to check this forum out. Otherwise you are just going to sell your product to people who enjoy solving cryptic puzzles.

This was already posted on DPR I've just started testing the image stacking tools in Affinity which are the reasons I've been excited most about the promise of Affinity. All I've got right now, are some HDR suitable photos, I'm going to need to shoot some focus stacking suitable images sometime this week, but with the Thanksgiving holiday coming up in the USA next week, I'm not sure I will get to it as promptly as I would like. The HDR utility isn't what I had hoped it would be. I haven't been able to get it to accept raw images directly, it seems to want me to develop them first and convert them to a tiff (or jpg, I guess, but I never use jpg for HDR). I've found developing raw prior to invoking the HDR utility to be a chancy thing in terms of making a good consistently developed series of raw images. I'd rather be able to submit my raw files to the HDR utility directly and let the HDR utility do the conversion. I've found it easier to do that development/conversion step in ACDSee, and convert the photos to tif files from within ACDSee, then invoke Afinity NOT as an external editor, but from the desktop, and load the photos manually into the Affinity HDR utility. It would be nice to be able to send the selected photos directly to the stacking load area from within ACDSee. (and without the ability to SEE the raw thumbnails from within Affinity, an all Affinity workflow is impossible for me) It's kind of kludgy and isn't a smooth flow of work even from within Affinity itself. PSP's HDR utility is a much better and smoother workflow implementation even though it doesn't play all that well with ACDSee as an HDR tool either but it's much easier to work with raw HDR series from within PSP itself. The easiest way for me to deal with HDR, so far, continues to be with Photomatx Pro 5.1 I just select the 3, 5 or 7 raw files in sequence from within the ACDSee 'Manage' tab, right click the selected group and send the raw files to Photomatix set up as an external editor. I process the photos in Photomatix, and send back an HDR in tif form to ACDSee. I think there are certain HDR 'looks' that I prefer to use PSP's HDR utility for. It's a little more complex there, but still a lot easier than Affinity's workflow. In that case, I exit from ACDSee, launch PSP X8, go to the PSP manager tab, select the raw sequence I want to work with, and then invoke the PSP HDR utility. Right now, I would like better interface with third party organizers and viewers, and a smoother, better thought out HDR utility. I'm also not too impressed with the Affinity raw development, but at this point, I am assuming it is my lack of knowldge and skills with the Affinity toolset that is the cause. But I have to admit, I like ACDSee better for raw. I think as a bit mapped editor, Affinity is pretty nice. For me that has been its strongest most pleasant functionality so far. I'm looking forward to testing the other components. By the way, the panorama stitching was fast and easy It isn't Hugin (and doesn't need to be), but it's better/easier than ICE

Man, I've wondered if Win 10 is ready for a production environment. I to can supply E-M10 raw files if the Developers need some known photos that are 'problematic'

Well I tried to load a codec into windows 10 (sagethumbs) and while Windows Explorer now displays E-M10 files, Affinity still will not display the thumbnail in the file manager open menu The image looks fine once it is opened, and I'm reasonably certain Affinity is processing the Raw E-M10 file. Using ACDsee Ultimate as a front end to Affinity works well, so it isn't a major issue for me personally, but I think there is going to be a problem there for other workflows.

It supports my old E-30 orfs, and my old dng files, but not the orfs from the E-m10 (MK 1!). It displays the 'empty' generic ORF icon. This does not occur on the E-30 orf files. However, oddly, I do seem to be able to open the files, but I'm not sure what is being edited, the embedded thumbnail or the actual raw file.