Skip to content

Move from krites

Install LoupeKind once by hand, then open it. Your shoots, verdicts, edits and settings carry across by themselves. LoupeKind is what krites became, and a krites install can't update itself to it.

  1. Quit krites. In the studio, use Shut down in settings. A krites studio left running isn't seen by LoupeKind.
  2. Install LoupeKind. Follow Getting started.
  3. Open LoupeKind. Then open your shoots as usual.
  4. Delete the old app. Remove Krites.app from Applications, or ~/.local/bin/krites. LoupeKind doesn't remove them for you.

What moves, and when

What From To When
Settings and the shoot library ~/.krites/ ~/.loupekind/ First run
A shoot's verdicts and edits <shoot>/.krites/ <shoot>/.loupekind/ When that shoot is first opened
Downloaded models <user cache>/krites/ <user cache>/loupekind/ First run
AI review keys Keychain service krites Keychain service loupekind First use of the key
Studio theme, grid size and layout Browser storage Browser storage First load, if the studio's address is unchanged

Each move is a rename, so it is quick and needs no spare disk space. Your original photos aren't touched.

What doesn't move

  • Environment variables. KRITES_* is no longer read. Rename each to LOUPEKIND_*, as in LOUPEKIND_FACE_ENABLED. LoupeKind warns about any it finds still set.
  • The AI review confirmation. The first review asks you again, because it sends images off your machine.
  • Config files outside your home folder. Move /etc/krites/config.yaml to /etc/loupekind/config.yaml, and rename a project's .krites.yaml to .loupekind.yaml. LoupeKind warns about these too, when it can see them.

If a shoot names two folders

That means the shoot has both a .krites and a .loupekind folder, for example because you ran krites on it again after moving. LoupeKind doesn't merge them, because that could lose verdicts. The library shows the two paths on that shoot. Keep the one you want, move or delete the other, and open the shoot again.

If ~/.krites comes back the same way, LoupeKind keeps using ~/.loupekind and warns you, leaving both alone. If your settings or shoots look missing, quit LoupeKind, move ~/.loupekind aside and start it again, and ~/.krites carries across. Check that everything is there before you delete either.

If the app doesn't open

If LoupeKind can't move ~/.krites, it stops rather than starting empty. This applies to every command, including update. Double-clicking the app then shows nothing: the icon bounces and the app quits, because the message goes to the terminal, which Finder doesn't show.

To read the message, open Terminal and run /Applications/LoupeKind.app/Contents/MacOS/loupekind --version. It names the folder and what's wrong. The usual causes are:

  • ~/.krites is a link to a drive that isn't connected. Connect the drive and open LoupeKind again.
  • Your home folder isn't writable. Fix its permissions and open LoupeKind again.

If it says it can't rename a folder, check that the drive is connected and writable, then try again.