KHORLO — Windows install
=========================

Khorlo is free. This is a beta: it works, and it is still being finished.


WHERE THE FILES GO
------------------

Copy the folders in this zip into these locations. Both are the standard
Windows plugin folders; every DAW looks in them.

  Khorlo.vst3  ->  C:\Program Files\Common Files\VST3\
  Khorlo.clap  ->  C:\Program Files\Common Files\CLAP\

Copy the WHOLE Khorlo.vst3 FOLDER, not the file inside it. It looks like a
folder because it is one — that is what a modern VST3 is.

You need administrator rights to write into Program Files. Windows will ask.
If you would rather not, these also work and need no admin:

  %LOCALAPPDATA%\Programs\Common\VST3\
  %LOCALAPPDATA%\Programs\Common\CLAP\

Then rescan plugins in your DAW. Most only scan at startup or when you press a
"rescan" button in preferences; restarting the DAW is the reliable way.

Use ONE format. Installing both VST3 and CLAP means Khorlo appears twice in
your plugin list, which is confusing but harmless.


WHAT ELSE YOU NEED
------------------

  WebView2 Runtime — for the interface only.

Khorlo's interface is drawn with Microsoft's WebView2, the same component Edge
uses. Windows 11 has it. Windows 10 usually has it, because many applications
install it, but not always.

Without it you get sound and a message where the interface should be. If you
see that message, install the runtime — it is free, from Microsoft, about 2 MB:

  https://developer.microsoft.com/microsoft-edge/webview2/

Nothing else is required. Khorlo carries its own C++ runtime, so you do NOT
need any Visual C++ Redistributable. (Builds before 0.9.02 did, and if you have
been told Khorlo "isn't recognised" by your DAW, that was almost certainly why —
this build fixes it.)


IF YOUR DAW CANNOT SEE IT
-------------------------

Work down this list. It is in order of how often each one is the answer.

  1. Is it in the right folder? The most common cause by far is unzipping to
     Downloads and going no further. See WHERE THE FILES GO above.

  2. Did you copy the whole Khorlo.vst3 folder, with its Contents folder
     inside? Copying only the file from within it will not work.

  3. Has your DAW rescanned? Restart it.

  4. Is your DAW 64-bit? Khorlo is 64-bit only. Any DAW from the last decade
     is, but very old versions of some hosts are not.

  5. Does your DAW support VST3 or CLAP? Khorlo ships no VST2. Hosts from
     around 2011 and earlier are usually VST2-only and will never see it —
     Sonar X1, for example. Nothing can be done about that from our side.

  6. Some DAWs keep a "failed plugins" or "blocklist" from an earlier scan.
     If Khorlo failed once for another reason, clearing that list and
     rescanning is often what finally shows it.


IF SMARTSCREEN WARNS YOU
------------------------

Khorlo is not code-signed yet — a certificate costs money a free plugin does
not have. Windows may say "Windows protected your PC".

  More info  ->  Run anyway

That warning means "we cannot confirm who made this", not "this is harmful".
If that is not good enough, that is a completely reasonable position; the
source is public at github.com/jxsxnskx/Khorlo.


IF THE INTERFACE DOES NOT APPEAR
--------------------------------

You will get a message saying so, and the sound engine keeps working — nothing
in your project is at risk.

  * Install the WebView2 Runtime (above). This is nearly always the answer.
  * Give it a moment. On some machines the interface takes 20 seconds or more
    the first time. If a message appeared and the interface then loaded behind
    it, you have a build older than 0.9.02; this one recovers on its own.

Either way, please send the log — it usually contains the exact cause:

  %APPDATA%\Khorlo\ui-debug.log


SOMETHING ELSE WRONG?
---------------------

Tell me. Beta reports have already fixed several things that only showed up on
someone else's machine, and every one of them was found by a user rather than
by a test.

  info@jas-i.com
  https://jas-i.com

What helps most: your Windows version, your DAW and its version, whether you
used VST3 or CLAP, and the log file above.
