getting-started

Getting started

AfterAPro is a non-destructive RAW photo editor. Original files are opened read-only. Every edit is stored beside the image or in the catalog, never in the RAW file. It is free software under the GNU General Public License, version 3 or later (the LICENSE file), with no warranty. NOTICE lists the code and data it contains from other projects. The source of each release is published at https://git.nilorea.net/AfterAPro. This product includes DNG technology under license by Adobe.

Its workflow is inspired by Corel AfterShot Pro. AfterAPro is not affiliated with, endorsed by or sponsored by Corel Corporation or Alludo; AfterShot is a trademark of its owner.

The program browses a folder, culls it with the keyboard, adjusts any frame, repairs parts of it, corrects the lens, and exports what you have chosen as JPEG, PNG, TIFF, WebP, BMP, Targa or PCX with presets and watermarks. The work runs on a graphics card when there is one to use.

It opens RAW files from every camera the decoder knows - forty six extensions, from the Canon and Nikon files most people have to the medium format backs and the dead formats of the nineteen nineties - and JPEG, PNG, TIFF, WebP, BMP, Targa and PCX as well. A file that is not RAW has already been demosaiced and balanced by whatever wrote it, so it starts further along: the temperature control still warms and cools it, from 6504 K, the white of sRGB it was written to, but it says it is relative rather than showing a figure in kelvin that would mean nothing.

A JPEG, PNG, TIFF or WebP with a colour profile in it, Adobe RGB, Display P3, ProPhoto or any other, is converted from that profile as it opens, so it keeps its colours. One without a profile is taken to be sRGB, as every program takes it. A build made without lcms2 reads every one as sRGB.

Everything here is also in the program, under Help > Documentation. The pages are the same files: the build compiles them in, so the help works on a machine that got a single binary and nothing beside it.

The rest of the pages cover the grid and the filters, the adjustments, the repairs and the lens corrections, saving and copying a look, exporting, watermarks, what the program remembers, effects somebody else wrote, what to do when the decoder does not know your camera's colours, and the keys.

Getting help inside the program

Help > Documentation opens these pages in a window: a list on the left, the page on the right, drawn as what it is rather than as its markup, so a heading is a heading and the key tables are tables. The pages are compiled into the program, so it works on a machine that never had the documentation installed. The wheel scrolls the page, and so do the arrows, Page Up, Page Down, Home and End once you have clicked in it.

Help > Your keys, as bound is the one page that is not written down. The program builds it from the bindings it is answering to at that moment, so it is right even after you have rebound something in View > Shortcuts. Each group of actions is a table of the action and the keys bound to it.

Requirements

Linux or Windows, with Allegro 5.2 or newer.

On Debian and Ubuntu:

sudo apt install liballegro5-dev liballegro-image5-dev \
                 liballegro-ttf5-dev liballegro-dialog5-dev \
                 liballegro-acodec5-dev build-essential \
                 libsqlite3-dev libjpeg-dev libpng-dev

Two more are optional and change what the program can do rather than whether it builds: liblensfun-dev for looking a lens up by name, and a graphics driver with OpenCL for developing photographs on the graphics card.

On Debian and Ubuntu there is also a package, and on any recent Linux an AppImage; with either, none of the above needs installing. The package is installed with

sudo apt install ./afterapro_<version>_amd64.deb

which brings in the libraries it needs, puts the program under /opt/afterapro and adds it to the application menu and to "Open with" for RAW files. The AppImage is one file that carries its libraries; make it executable and run it. It uses the lens database of the machine it runs on, if there is one (liblensfun-data-v1 on Debian), and corrects lenses from the program's own profiles if there is not.

Help > About lists every library the program uses with the version it is running with, as each library reports it, and whether it is built in, loaded, not found or not in this build; curl and the DNG converter are programs it runs. Copy versions puts that list on the clipboard, for a bug report.

On Windows, install it. There is nothing else to do: everything the program needs is in the installer. The Windows build has soft proofing but not lens lookup by name or the XMP files beside photographs: the XMP setting is greyed out, the About window says lensfun and libxml2 are not in this build, and lenses are corrected from the program's own profiles and the sliders. It asks which of the start menu entry, the desktop shortcut and the file types you want, the first two for every account on the machine, and the file types are an offer rather than a change: AfterAPro appears in the "Open with" menu for a RAW file and whatever opens those files now goes on opening them. To make it the one that does, choose it in Settings > Default apps, where Windows remembers what it replaced. Building it yourself is docs/dev/BUILDING.md.

Building and running

make
./afterapro

The window opens on four columns: the folders on your disk, the thumbnails of whichever one is chosen, the photograph, and the controls that change it. Any of the three outer ones folds away with the small button at its corner, and the photograph takes the room.

The photograph folds too, with the button in its top right corner or the L key (both in View > Preview). Its room then goes to the thumbnails, or to the folders when the thumbnails are folded as well, which turns the window into a wide grid for going through a shoot. It comes back with its tab, with L again, or by itself when you ask to see a photograph: Enter or a double click on a thumbnail. It cannot fold while the three other columns are folded, since its room would have nowhere to go. The adjustment panel stays, and still follows the frame under the cursor.

The bar along the bottom has two halves. The left one always describes the photograph: in the grid, the folder, which frame of how many, its name and how it was taken (ISO 400 f/2.8 1/250s); in the photograph's column, the camera, the size, the same exposure and the zoom. The right one is the status line: what was just done, or a message. It appears when there is something to say, and the photograph's half takes the whole bar when there is not. A message is about the photograph on show when it was said, so moving to another photograph clears it, unless the move is what it is about (1 photograph deleted). A running export says how far it has got on the menu line, between Help and the Tasks button, which says what is running, and then how it ended, until Clear finished leaves no task pending.

Workspaces

A workspace is a whole layout kept under a name: where the dividers are, which columns are folded, the thumbnails' preview size, which sections of the adjustment panel are open, and in which order the panel shows them and which it leaves out. The Workspace menu lists them, and choosing one puts the window back that way.

Three are built in and cannot be changed or deleted:

Workspace > Save the layout as... asks for a name and keeps the layout on screen under it. The name of a saved one replaces it; the names of the built-in three are refused. Up to sixteen can be kept. Each saved one gets the next key, Ctrl+4 up to Ctrl+9, in the order they were saved; the menu shows the key beside each. Workspace > Delete Name... removes one after asking, and leaves the window as it is.

View > Panel sections... arranges the adjustment panel: select a section and move it Up or Down, or Show or hide it, which then moves on to the next section, so a run of them is hidden one press each - a hidden section keeps what it holds and comes back as it was. Default puts back the program's own order with every section shown. The panel changes as you go. Save a workspace afterwards and it keeps that arrangement, so a Develop workspace can have Basic and Curve on top and a Retouch one Local and Regions; the two built in workspaces always have the program's own order. The built-in ones show the thumbnails at the default size. A workspace saved before the preview size was kept leaves the size as it is.

The keys can be changed in View > Shortcuts, under Everywhere. Pressing the key of a place with no workspace says so on the status line. Workspaces are kept in the settings file, so they are the same the next time the program starts.

The layout in use is kept too, whether or not it was saved as a workspace: the dividers where you dragged them, the folds, the preview size and the order of the thumbnails all come back as they were the next time the program starts.

The folder column browses from your home directory and from the root of the disk. Click a folder and its photographs appear beside it. The next time you start, it opens on the folder you were last looking at.

File > Open image opens a single file, and moves the folder column to the folder that file is in. Help > About shows the version, the copyright and licence, the platform and how many worker threads the program uses. In a package, the licence and the notices are the files AfterAPro-LICENSE and AfterAPro-NOTICE, installed with the program: in /opt/afterapro/licenses for the .deb, in the licenses folder beside afterapro.exe on Windows.

Command line

afterapro [options] [file or folder]
Option Effect
-h, --help print the usage and exit
-v, --version print the version and exit
--accel=BACKEND auto, cpu or opencl. Default auto
--no-opencl never use OpenCL, whatever --accel asks for
--threads=N worker threads. 0 derives the count from the processor
--log-level=N 0 emergency to 7 debug. Default 5, notice
--selftest-shot=PNG render one frame into a PNG and exit
--selftest-about open the about window before that frame

There are more --selftest- options than these two. They are checks the program runs on itself, used when building it, and --help lists all of them. You do not need any of them to edit photographs.

A RAW file given on the command line is opened in the loupe. A folder is opened in the browser.

The acceleration options are accepted now and take effect when the pipeline lands in M7. The CPU path is always present and is the reference result; the other backends are optimisations that can be switched off at any time.

Colours

View > Settings has nine schemes to draw the program in, from Dark to Light through Solarized, Nord, Dracula and the rest. Light (dimmed) is Light a step darker, for a room that is not bright. Picking one changes everything at once and is remembered.

Every scrollbar in the program is drawn the same way, in the scheme's own colours: a flat track with a rounded bar in it. Put the pointer on one and the bar inside it turns the scheme's accent colour, so you can see what you are about to drag, and it goes back when the pointer leaves. The wheel moves whichever one the pointer is on, so it pans sideways over a horizontal bar and scrolls down the list anywhere else. The bar beside the folder tree, the one beside the thumbnails and the ones around the photograph are all the same width and answer the same way.

When you open a folder, the program reads the rest of its previews in the background while you look at the first one, so coming back to that folder later is immediate. It appears in View > Tasks and can be paused or stopped there, and switched off in View > Settings. Only one folder is filled at a time; opening another stops the first, and nothing is wasted because whatever it managed is already kept.

The last few photographs you looked at are also kept ready in memory, so going back to one is immediate rather than opening it again from scratch. How many is in View > Settings; each costs around ninety megabytes, so it is a small number, and 0 keeps none.

What is kept on disk has a size limit and an age limit, both in View > Settings, applied when you leave the program. There is a button there to empty it now, and a box to keep it somewhere other than the usual place. Everything in it is rebuilt from your photographs, so losing it costs time and nothing else.

The area around the photograph is not part of that. It stays a neutral grey whichever scheme you pick, because a warm or cool surround changes how the colour of the picture inside it reads, and you would end up correcting the border rather than the photograph. The crop rectangle and the marks for local corrections keep their own colours for the same reason.

Where your files go

What Where
Settings the standard per user settings directory, ~/.config on Linux
Catalog: ratings, labels, flags catalog.db in the per user data directory, ~/.local/share/afterapro on Linux
Adjustments a .apro text file beside each photograph you have adjusted
Presets one file each, in the settings directory
Thumbnail cache, converted DNGs a cache directory beside it
Your photographs wherever they already are. Nothing is copied or moved

Deleting the cache is always safe: it is rebuilt from the originals and holds no work of yours. The catalog is not: it holds every rating and label you have applied, which is why it sits beside the cache rather than inside it.

The cache can be moved in the settings. When it moves, the old folder is left alone and a button offers to delete it. That button, the size limit and the age limit only ever remove the cache's own files, whose names are 32 letters and digits; anything else in the folder is kept, and so is the folder itself if anything is left in it. The size limit and the age limit also cover the DNGs made of RAWs the decoder does not know, one budget for both, applied when the program closes.

Keyboard

The full list is in keyboard-shortcuts.md. The ones to know first:

Key Effect
Ctrl+Q quit
Escape close a popup, or go back to the grid
1 to 5 rate the frame under the cursor
P, X pick, reject
Enter open the frame in the loupe
G back to the grid

Escape with nothing left to close proposes leaving, and proposing is as far as it goes: what a stray key press meets is a question with Cancel in it. Losing work to one is not a thing a photo editor should do.

Leaving always asks, whichever way you ask for it - the key, the menu, or the window's own close button. Pressing quit a second time while the question is up answers it, so closing the program from the keyboard never needs the mouse.

When work you started is still going, the question names it and says that quitting cancels it: "Quitting cancels 2 exports and an HDR merge.", with how many photographs are not written yet. It counts every task: exports, galleries, contact sheets, HDR merges, back ups, moves, imports, model and camera profile downloads, and auto settings being worked out; filling the cache is not counted, it is only a head start. Quit anyway stops them where they are, a noise reduction model half way through a photograph included, and what was already written stays. Show the tasks opens the tasks window instead, to let them finish.