casterle

What I was getting at was that perhaps a different algorithm should be used in cases where the problem occurs, such that these puzzling issues do not occur.

Excellent tutorial. I'd given up on getting displacement maps working in AP.

Perhaps that is the problem?

Looks like Andrew Sullivan when he had hair.

I've not seen that one before. What I use is a bit different, a MIDI controller - if you open the post you can see the controller, it's cropped out of the image in the link below. I selected the X-Touch Mini because it was inexpensive ($60 on Amazon but the price fluctuates - I bought a used one in excellent condition on Adorama for $47 delivered). It's got encoders (knobs) which can be used to control brush size in AP (and more once more keyboard shortcuts are added) as well as buttons. You might wonder how I can set a numeric value (brush size) after complaining about the lack of an API to allow access to numeric fields. You don't need the API as long as there is a keyboard shortcut that increments/decrements the value of interest, like the [ and ] keys for adjusting brush size. Unfortunately, brush size is the only brush value with a shortcut - as more are added I'll be able to control them with an encoder knob as well. How to set this up is documented in the attachment to my post.

Using something like AutoIt isn't really programming, but it does require a technical understanding of some aspects of the OS. The bottom line is that unless and until Affinity provides external access to their internals (an API) there is no non-fragile approach of which I am aware. Nothing to do with macros, but do you use a MIDI controller?

I haven't looked into Macro Express but I have to wonder how you would get calculated values inserted into the proper numeric input fields since Affinity has yet to provide an API. Do you have a good approach? Also, there are powerful free alternatives like AutoIt that may do all you need.

Thank you, that's a great technique!

I learn so much in these forums, but a tip on group psychology was an interesting surprise. Thank you!

I've still got an old Ensoniq SQ-80 from my playing with MIDI programming days in the mid-80's. I've probably got the old MIDI card and cables lying around as well. Things have changed and I think USB has been the catalyst for MIDI growth outside the music world. Being able to use a cheap MIDI controller easily (no special hardware or cables) makes all the difference. Now I've got a quality graphics tablet with 9 knobs and 22 buttons (counting those on the tablet itself) for under $150. I've spent the last week or two playing with the new Blender UI and am teetering on the edge of a very deep dive. I imagine the X-Touch Mini will be useful there as well, especially with the sequencer.

Exactly. From my research (I've never used LR) it appears that LR exposes an API that supports reading/writing values. MIDI2LR (https://rsjaffe.github.io/MIDI2LR/) takes advantage of this and provides direct adjustment of values via MIDI encoders. The X-Touch Mini has a light ring around each encoder knob which can be configured in various ways. My understanding is that MIDI2LR can be configured to update these rings when the associated value is changed in LR. The X-Touch Mini also has 2 'layers' so that you can switch between, changing the function of the various controls and providing 16 encoder knob functions. I don't know if this can be supported via MIDI2LR, but 8 encoders and 16 buttons is still pretty awesome.

It's pretty amazing how much a MIDI controller can speed up things that have nothing to do with music. MIDI controllers are now so inexpensive (I got my used X-Touch Mini in like-new condition for $47 from Adorama) and add so much convenience I'm surprised more folks aren't using them. Oh, and as it turns out, it's not a new one (although it was to me until recently). Turns out LR users discovered them long ago, perhaps because LR offers much better integration via an API. But you can make them work with any app that has keyboard shortcuts.

Well then, this should make you happy. Everything you need, although if you're on a Mac the MIDI translator program I use isn't free.

+1. Draft if possible.

Thank you. You've got a new subscriber.

As @firstdefence noted, the software does not provide this functionality (yet). If you're on Windows and are comfortable with the process, it's not hard to do this manually.

If you have a license for the release version you can download the beta version now. Both versions can be installed at the same time, and do not interfere with each other. Note that files saved by the beta are no longer compatible with the release version.

Nice job. I found your accent not only understandable but enjoyable, and thought the pace was fine.

I like it - I get a peaceful, easy feeling...

I understand. Mucking about with these files is certainly not for everyone. I was trying to say what Walt said better .

I like the suggestion in your OP, but I don't understand this comment. Are you miffed because no one from Affinity has replied?

I think the trial is the same version as the release, but I"m not sure: 1.6.5.135. The exe is dated 9/24/2018.

I'd missed that. Thank you.

All these images are wonderful, but I find this one grabs me like none of these others. Now for the dumb question. I'm not a photographer so I wonder, are infrared images captured with a special infrared camera? My understanding of infrared is light outside (below) the visible spectrum so it seems special hardware would be required...

The export/import functions are great, but there are many settings that aren't covered by this mechanism. On Windows, and I suspect on Mac as well, most of the settings are stored in .XML files. Here is a list of the settings files for both the release and beta folders (the filenames in red are different between the two folders): .: These files are just text, so you can examine them and copy settings from one to another. If you are comfortable with text editors (as opposed to word processors ) you can copy settings from one file to another, or copy the entire file from the release version to the beta and see what happens. As long as you follow Walt's excellent advice and back up the files you want to change first you can always get back to where you were when things go wrong. I've did this extensively when I first started playing with the beta without problems (I haven't used the beta in some time as I'm still in heavy leaning mode with AP). Note, however, that I am a retired software developer and thus very familiar with these things. If you are not confident in your abilities I would recommend you not proceed down this path.