Morpheus user manual
This is the manual that ships with a build, for every target Morpheus can compile to. It covers installing what you made, starting it, and the warnings each platform puts in front of unsigned software — because that is the part that looks like a broken download and is not.
Web App
============================
Your project — user manual
============================
What this is : a Web App build, compiled for you by Morpheus
Generated : 2026-10-18
This file travelled with your download. It covers installing the app, starting it, and
the things that platform does to unsigned software. It is written from what Morpheus
knew at compile time — for what the app does once it is running, see the project's own
notes at the bottom.
INSTALLING IT (Web App)
You downloaded a static web build (.zip). Unzip it and serve the folder — it is plain files.
npx serve <the folder>
or upload the folder to any static host.
STARTING IT
Open the served address in a browser.
IF IT WILL NOT OPEN, OR WILL NOT START
A blank page with no errors is usually a build that expects to be served from the root of a domain.
CONNECTING IT TO MORPHEUS
Some compiled apps can sign in to Morpheus from inside the app, so the work they do is
billed to your own account. That is a device login: the app shows a short code, you
approve it in your browser on the Morpheus site, and the app picks up a token scoped to
one capability. If the app has no such screen, it does not need one.
--------------------------------------------------------------------------
THE PROJECT'S OWN NOTES (none shipped)
--------------------------------------------------------------------------
This project did not ship a README, so there is nothing here to quote. Morpheus will
not invent one: it has not read the app's interface, and a manual that describes menus
that do not exist is worse than a short one. What the app does when you open it is the
authority.
--------------------------------------------------------------------------
End of manual. the app itself is the authority on what it does.
Android APK
============================
Your project — user manual
============================
What this is : a Android APK build, compiled for you by Morpheus
Generated : 2026-10-18
This file travelled with your download. It covers installing the app, starting it, and
the things that platform does to unsigned software. It is written from what Morpheus
knew at compile time — for what the app does once it is running, see the project's own
notes at the bottom.
INSTALLING IT (Android APK)
You downloaded an Android .apk.
1. Copy it to the device (or open the download on the device itself).
2. Your browser or Files app will ask to install an unknown app — allow it for that app only.
3. Android will warn that it cannot check the app for harmful behaviour. That is Play
Protect reacting to an unsigned build, not a finding about this app.
STARTING IT
Open it from the app drawer once installed.
IF IT WILL NOT OPEN, OR WILL NOT START
"App not installed" usually means an older build with a different signing key is already present — uninstall that first.
CONNECTING IT TO MORPHEUS
Some compiled apps can sign in to Morpheus from inside the app, so the work they do is
billed to your own account. That is a device login: the app shows a short code, you
approve it in your browser on the Morpheus site, and the app picks up a token scoped to
one capability. If the app has no such screen, it does not need one.
--------------------------------------------------------------------------
THE PROJECT'S OWN NOTES (none shipped)
--------------------------------------------------------------------------
This project did not ship a README, so there is nothing here to quote. Morpheus will
not invent one: it has not read the app's interface, and a manual that describes menus
that do not exist is worse than a short one. What the app does when you open it is the
authority.
--------------------------------------------------------------------------
End of manual. the app itself is the authority on what it does.
Python Package
============================
Your project — user manual
============================
What this is : a Python Package build, compiled for you by Morpheus
Generated : 2026-10-18
This file travelled with your download. It covers installing the app, starting it, and
the things that platform does to unsigned software. It is written from what Morpheus
knew at compile time — for what the app does once it is running, see the project's own
notes at the bottom.
INSTALLING IT (Python Package)
You downloaded a Python package (a wheel or a source archive).
pip install <the file>
Then run the module or entry point the project documents.
STARTING IT
A virtual environment (python -m venv) is worth it if you do not want it system-wide.
IF IT WILL NOT OPEN, OR WILL NOT START
A failed install names the requirement it could not satisfy.
CONNECTING IT TO MORPHEUS
Some compiled apps can sign in to Morpheus from inside the app, so the work they do is
billed to your own account. That is a device login: the app shows a short code, you
approve it in your browser on the Morpheus site, and the app picks up a token scoped to
one capability. If the app has no such screen, it does not need one.
--------------------------------------------------------------------------
THE PROJECT'S OWN NOTES (none shipped)
--------------------------------------------------------------------------
This project did not ship a README, so there is nothing here to quote. Morpheus will
not invent one: it has not read the app's interface, and a manual that describes menus
that do not exist is worse than a short one. What the app does when you open it is the
authority.
--------------------------------------------------------------------------
End of manual. the app itself is the authority on what it does.
Windows EXE
============================ Your project — user manual ============================ What this is : a Windows EXE build, compiled for you by Morpheus Generated : 2026-10-18 This file travelled with your download. It covers installing the app, starting it, and the things that platform does to unsigned software. It is written from what Morpheus knew at compile time — for what the app does once it is running, see the project's own notes at the bottom. INSTALLING IT (Windows EXE) You downloaded a .zip. Unzip it first — running an .exe from inside a zip does not work. Then double-click the .exe inside the extracted folder. STARTING IT Windows may show "Windows protected your PC" (SmartScreen). Choose "More info", then "Run anyway". This appears for any program that is not signed with a paid certificate. IF IT WILL NOT OPEN, OR WILL NOT START Nothing on screen after launching: this app may have been built without a console window, so it prints nothing and a crash is silent. Look for a log file next to the .exe or under %APPDATA%. CONNECTING IT TO MORPHEUS Some compiled apps can sign in to Morpheus from inside the app, so the work they do is billed to your own account. That is a device login: the app shows a short code, you approve it in your browser on the Morpheus site, and the app picks up a token scoped to one capability. If the app has no such screen, it does not need one. -------------------------------------------------------------------------- THE PROJECT'S OWN NOTES (none shipped) -------------------------------------------------------------------------- This project did not ship a README, so there is nothing here to quote. Morpheus will not invent one: it has not read the app's interface, and a manual that describes menus that do not exist is worse than a short one. What the app does when you open it is the authority. -------------------------------------------------------------------------- End of manual. the app itself is the authority on what it does.
Linux Binary
============================
Your project — user manual
============================
What this is : a Linux Binary build, compiled for you by Morpheus
Generated : 2026-10-18
This file travelled with your download. It covers installing the app, starting it, and
the things that platform does to unsigned software. It is written from what Morpheus
knew at compile time — for what the app does once it is running, see the project's own
notes at the bottom.
INSTALLING IT (Linux Binary)
You downloaded a .tar.gz.
tar xzf <the file>.tar.gz
chmod +x <the binary inside>
./<the binary inside>
STARTING IT
If it exits at once, run it from a terminal so you can see why.
IF IT WILL NOT OPEN, OR WILL NOT START
A missing shared library names itself in the terminal output; install that package.
CONNECTING IT TO MORPHEUS
Some compiled apps can sign in to Morpheus from inside the app, so the work they do is
billed to your own account. That is a device login: the app shows a short code, you
approve it in your browser on the Morpheus site, and the app picks up a token scoped to
one capability. If the app has no such screen, it does not need one.
--------------------------------------------------------------------------
THE PROJECT'S OWN NOTES (none shipped)
--------------------------------------------------------------------------
This project did not ship a README, so there is nothing here to quote. Morpheus will
not invent one: it has not read the app's interface, and a manual that describes menus
that do not exist is worse than a short one. What the app does when you open it is the
authority.
--------------------------------------------------------------------------
End of manual. the app itself is the authority on what it does.
macOS App
============================
Your project — user manual
============================
What this is : a macOS App build, compiled for you by Morpheus
Generated : 2026-10-18
This file travelled with your download. It covers installing the app, starting it, and
the things that platform does to unsigned software. It is written from what Morpheus
knew at compile time — for what the app does once it is running, see the project's own
notes at the bottom.
INSTALLING IT (macOS App)
You downloaded a disk image (.dmg).
1. Double-click it — Finder mounts it like a USB stick.
2. Drag the app onto the Applications shortcut sitting next to it.
3. Eject the disk image (the eject arrow beside it in Finder).
STARTING IT
The menu bar for a Mac app is at the TOP OF THE SCREEN, next to the logo — not inside the
window. If a window looks empty, click it once and look up there.
IF IT WILL NOT OPEN, OR WILL NOT START
NOT SIGNED: this app is not signed with a paid Apple Developer certificate, so macOS will
probably refuse the first launch — "Apple could not verify ... is free of malware", or the
older "...is damaged and can't be opened. You should move it to the Bin." It is not damaged.
Fix: open Terminal (Applications -> Utilities) and run, with the path to YOUR app:
xattr -cr /Applications/YourApp.app
Then open it again. Or: System Settings -> Privacy & Security, scroll down, and click
"Open Anyway" after the first attempt.
CROSSED-OUT ICON (a circle with a line through it): that means the build is for a different
kind of Mac, not that the file is broken. Download the other one — "intel" for an Intel Mac,
"apple-silicon" for an M-series Mac. Apple menu -> About This Mac names your chip.
CONNECTING IT TO MORPHEUS
Some compiled apps can sign in to Morpheus from inside the app, so the work they do is
billed to your own account. That is a device login: the app shows a short code, you
approve it in your browser on the Morpheus site, and the app picks up a token scoped to
one capability. If the app has no such screen, it does not need one.
--------------------------------------------------------------------------
THE PROJECT'S OWN NOTES (none shipped)
--------------------------------------------------------------------------
This project did not ship a README, so there is nothing here to quote. Morpheus will
not invent one: it has not read the app's interface, and a manual that describes menus
that do not exist is worse than a short one. What the app does when you open it is the
authority.
--------------------------------------------------------------------------
End of manual. the app itself is the authority on what it does.
iOS App
============================ Your project — user manual ============================ What this is : a iOS App build, compiled for you by Morpheus Generated : 2026-10-18 This file travelled with your download. It covers installing the app, starting it, and the things that platform does to unsigned software. It is written from what Morpheus knew at compile time — for what the app does once it is running, see the project's own notes at the bottom. INSTALLING IT (iOS App) You downloaded an iOS .ipa. An .ipa only installs on a device it was signed for. On a normal iPhone this needs a Mac with Xcode (or a sideloading tool) and a signing identity that includes your device — Apple does not allow installing unsigned apps. STARTING IT The first launch of a sideloaded app is refused until you trust the developer in Settings -> General -> VPN & Device Management. IF IT WILL NOT OPEN, OR WILL NOT START "Unable to Install" almost always means the signing identity does not cover this device. CONNECTING IT TO MORPHEUS Some compiled apps can sign in to Morpheus from inside the app, so the work they do is billed to your own account. That is a device login: the app shows a short code, you approve it in your browser on the Morpheus site, and the app picks up a token scoped to one capability. If the app has no such screen, it does not need one. -------------------------------------------------------------------------- THE PROJECT'S OWN NOTES (none shipped) -------------------------------------------------------------------------- This project did not ship a README, so there is nothing here to quote. Morpheus will not invent one: it has not read the app's interface, and a manual that describes menus that do not exist is worse than a short one. What the app does when you open it is the authority. -------------------------------------------------------------------------- End of manual. the app itself is the authority on what it does.
Raspberry Pi Distro
============================ Your project — user manual ============================ What this is : a Raspberry Pi Distro build, compiled for you by Morpheus Generated : 2026-10-18 This file travelled with your download. It covers installing the app, starting it, and the things that platform does to unsigned software. It is written from what Morpheus knew at compile time — for what the app does once it is running, see the project's own notes at the bottom. INSTALLING IT (Raspberry Pi Distro) You downloaded a disk image for a Raspberry Pi. Write it to a microSD card with Raspberry Pi Imager (or balenaEtcher) — pick "Use custom image" and choose this file. Then boot the Pi. STARTING IT The first boot takes several minutes while it resizes and sets itself up. IF IT WILL NOT OPEN, OR WILL NOT START A Pi that never appears on the network: re-check that the image was written to the card, not to a file. CONNECTING IT TO MORPHEUS Some compiled apps can sign in to Morpheus from inside the app, so the work they do is billed to your own account. That is a device login: the app shows a short code, you approve it in your browser on the Morpheus site, and the app picks up a token scoped to one capability. If the app has no such screen, it does not need one. -------------------------------------------------------------------------- THE PROJECT'S OWN NOTES (none shipped) -------------------------------------------------------------------------- This project did not ship a README, so there is nothing here to quote. Morpheus will not invent one: it has not read the app's interface, and a manual that describes menus that do not exist is worse than a short one. What the app does when you open it is the authority. -------------------------------------------------------------------------- End of manual. the app itself is the authority on what it does.
Linux Distro (PC/Server)
============================ Your project — user manual ============================ What this is : a Linux Distro (PC/Server) build, compiled for you by Morpheus Generated : 2026-10-18 This file travelled with your download. It covers installing the app, starting it, and the things that platform does to unsigned software. It is written from what Morpheus knew at compile time — for what the app does once it is running, see the project's own notes at the bottom. INSTALLING IT (Linux Distro (PC/Server)) You downloaded a disk image. Write it to a USB stick or disk with balenaEtcher, or boot it directly in a virtual machine. STARTING IT Nothing is installed on your computer until you run the installer from the booted system. IF IT WILL NOT OPEN, OR WILL NOT START A machine that will not boot it usually has Secure Boot enabled — turn it off for the install. CONNECTING IT TO MORPHEUS Some compiled apps can sign in to Morpheus from inside the app, so the work they do is billed to your own account. That is a device login: the app shows a short code, you approve it in your browser on the Morpheus site, and the app picks up a token scoped to one capability. If the app has no such screen, it does not need one. -------------------------------------------------------------------------- THE PROJECT'S OWN NOTES (none shipped) -------------------------------------------------------------------------- This project did not ship a README, so there is nothing here to quote. Morpheus will not invent one: it has not read the app's interface, and a manual that describes menus that do not exist is worse than a short one. What the app does when you open it is the authority. -------------------------------------------------------------------------- End of manual. the app itself is the authority on what it does.
Arduino Firmware
============================ Your project — user manual ============================ What this is : a Arduino Firmware build, compiled for you by Morpheus Generated : 2026-10-18 This file travelled with your download. It covers installing the app, starting it, and the things that platform does to unsigned software. It is written from what Morpheus knew at compile time — for what the app does once it is running, see the project's own notes at the bottom. INSTALLING IT (Arduino Firmware) You downloaded firmware for a board. Flash it with the tool the project documents (avrdude, esptool, or the Arduino IDE's "Upload" with the binary). STARTING IT Most boards need a reset (or a double-tap of the reset button) to enter the bootloader for flashing. IF IT WILL NOT OPEN, OR WILL NOT START A board that reports no port is usually a missing USB serial driver, not the firmware. CONNECTING IT TO MORPHEUS Some compiled apps can sign in to Morpheus from inside the app, so the work they do is billed to your own account. That is a device login: the app shows a short code, you approve it in your browser on the Morpheus site, and the app picks up a token scoped to one capability. If the app has no such screen, it does not need one. -------------------------------------------------------------------------- THE PROJECT'S OWN NOTES (none shipped) -------------------------------------------------------------------------- This project did not ship a README, so there is nothing here to quote. Morpheus will not invent one: it has not read the app's interface, and a manual that describes menus that do not exist is worse than a short one. What the app does when you open it is the authority. -------------------------------------------------------------------------- End of manual. the app itself is the authority on what it does.
Audio Plugin — macOS (VST3 · AU · CLAP)
============================
Your project — user manual
============================
What this is : a Audio Plugin — macOS (VST3 · AU · CLAP) build, compiled for you by Morpheus
Generated : 2026-10-18
This file travelled with your download. It covers installing the app, starting it, and
the things that platform does to unsigned software. It is written from what Morpheus
knew at compile time — for what the app does once it is running, see the project's own
notes at the bottom.
INSTALLING IT (Audio Plugin — macOS (VST3 · AU · CLAP))
THIS PLUGIN IS FOR MACOS ONLY. It will not load on Windows or Linux — there is no Audio Unit
outside Apple's platforms, and the .vst3 and .clap in this download are macOS bundles. If you
or your collaborators are on Windows, this is not the build for them.
You downloaded FOUR zips because a plugin is four files in four different places, and a DAW
only looks in its own. Unzip them and move each one to its folder — the USER one only needs
your account, the SYSTEM one needs your password and is shared by everyone on the Mac.
VST3 -> ~/Library/Audio/Plug-Ins/VST3/
AU -> ~/Library/Audio/Plug-Ins/Components/
CLAP -> ~/Library/Audio/Plug-Ins/CLAP/
standalone -> anywhere you like; it is an ordinary app, double-click it.
If the folder does not exist, make it: open Finder, press Shift-Command-G, paste the line
above without the trailing slash, and create it.
STARTING IT
THE BLOCKS AND THEIR ORDER ARE YOURS. The plugin runs the signal path you arranged in the app —
the COMPILE panel's SIGNAL PATH button — and that arrangement is saved in morpheus.plugin.json as
the "board" key, so the file you are reading the rest of this from says what this plugin does.
A MODEL MAKES IT AN AMP. Put a .nam file in the project — models/ is the usual place, or name one in
morpheus.plugin.json as "model" — and rebuild. The model is baked into this download, so there is
nothing to install beside it. Without one the plugin is a stereo gain stage, which is what you have if
you are reading this and expected an amp sim.
A CABINET MAKES IT SOUND LIKE A RECORDING. A .nam is usually the amplifier; the speaker is a
separate convolution. Put a .wav impulse response of your cabinet in the project — models/ is the
usual place, or name one in morpheus.plugin.json as "cab" — and rebuild. It is baked into the
download the same way, so there is nothing to install beside it.
A DAW scans its plugin folders at startup, so QUIT AND REOPEN IT — a plugin installed while
it was running usually will not appear.
Ableton, Reaper, Bitwig and Cubase take the VST3. LOGIC, GARAGEBAND AND MAIN STAGE TAKE ONLY
THE AU — they cannot load a VST3 at all, so install the .component for those.
The plugin is listed under the vendor name from its manifest, not under "Morpheus", unless
that is what you put there.
IF IT WILL NOT OPEN, OR WILL NOT START
NOT SIGNED: this plugin has no paid Apple Developer certificate, so macOS may quarantine it
and the DAW will not see it even though the file is there. That is not a broken plugin.
Fix: open Terminal (Applications -> Utilities) and run, with the path to YOUR plugin:
xattr -cr ~/Library/Audio/Plug-Ins/VST3/"Your Plugin.vst3"
Do the same for the .component, then reopen the DAW.
NOT LISTED IN LOGIC: Logic only reads Audio Units. If you installed the .vst3 only, install
the .component as well. If it is installed and still missing, run
auval -v aufx SUBT MANU
with the four-character codes from morpheus.plugin.json — it reports what Logic objects to.
TWO PLUGINS WITH THE SAME NAME: the AU registration codes in morpheus.plugin.json must be
unique. Change auSubtype, rebuild, and reinstall — a duplicate makes one of them invisible.
INSTALLED THE WRONG ARCHITECTURE: this build is universal (Intel and Apple silicon), so it
should load on either. If an older copy is still installed, delete it before installing this one.
CONNECTING IT TO MORPHEUS
Some compiled apps can sign in to Morpheus from inside the app, so the work they do is
billed to your own account. That is a device login: the app shows a short code, you
approve it in your browser on the Morpheus site, and the app picks up a token scoped to
one capability. If the app has no such screen, it does not need one.
--------------------------------------------------------------------------
THE PROJECT'S OWN NOTES (none shipped)
--------------------------------------------------------------------------
This project did not ship a README, so there is nothing here to quote. Morpheus will
not invent one: it has not read the app's interface, and a manual that describes menus
that do not exist is worse than a short one. What the app does when you open it is the
authority.
--------------------------------------------------------------------------
End of manual. the app itself is the authority on what it does.
Audio Plugin — Windows (VST3 · CLAP)
============================
Your project — user manual
============================
What this is : a Audio Plugin — Windows (VST3 · CLAP) build, compiled for you by Morpheus
Generated : 2026-10-18
This file travelled with your download. It covers installing the app, starting it, and
the things that platform does to unsigned software. It is written from what Morpheus
knew at compile time — for what the app does once it is running, see the project's own
notes at the bottom.
INSTALLING IT (Audio Plugin — Windows (VST3 · CLAP))
THIS PLUGIN IS FOR WINDOWS ONLY. It will not load on macOS or Linux. There is also no Audio Unit in
it — only Apple has those — which is why this download has three files where the macOS one has
four. If you are on a Mac, build the MACOS AUDIO PLUGIN route instead.
You downloaded THREE zips because a plugin is three files in two different places, and a DAW only
looks in its own. Unzip them and move each one to its folder — the "Common Files" folders are
shared, so copying into them needs administrator rights.
VST3 -> C:\Program Files\Common Files\VST3\
CLAP -> C:\Program Files\Common Files\CLAP\
standalone -> anywhere you like; it is an ordinary .exe, double-click it.
If a folder does not exist, create it. The name must match exactly, because the host looks for the
path and not for the file.
STARTING IT
THE BLOCKS AND THEIR ORDER ARE YOURS. The plugin runs the signal path you arranged in the app —
the COMPILE panel's SIGNAL PATH button — and that arrangement is saved in morpheus.plugin.json as
the "board" key, so the file you are reading the rest of this from says what this plugin does.
A MODEL MAKES IT AN AMP. Put a .nam file in the project — models/ is the usual place, or name one in
morpheus.plugin.json as "model" — and rebuild. The model is baked into this download, so there is
nothing to install beside it. Without one the plugin is a stereo gain stage, which is what you have if
you are reading this and expected an amp sim.
A CABINET MAKES IT SOUND LIKE A RECORDING. A .nam is usually the amplifier; the speaker is a
separate convolution. Put a .wav impulse response of your cabinet in the project — models/ is the
usual place, or name one in morpheus.plugin.json as "cab" — and rebuild. It is baked into the
download the same way, so there is nothing to install beside it.
A DAW scans its plugin folders at startup, so QUIT AND REOPEN IT — a plugin installed while it was
running usually will not appear.
Ableton, Reaper, Bitwig, Cubase and Studio One take the VST3. CLAP is supported by Reaper, Bitwig
and a growing list of hosts; if your DAW does not list it, install the VST3 as well.
The plugin is listed under the vendor name from its manifest, not under "Morpheus", unless that is
what you put there.
64-BIT ONLY: this build is x64. A 32-bit DAW cannot load it, and that is the most common reason a
plugin installs and never appears.
IF IT WILL NOT OPEN, OR WILL NOT START
NOT SIGNED, AND ON WINDOWS THAT MATTERS LESS THAN YOU WOULD THINK: plugins load unsigned in every
DAW, so a VST3 or CLAP that does not appear is almost always in the wrong folder or was skipped by
the scan — check the path above first.
SMARTSCREEN: the standalone .exe is unsigned, so Windows may show "Windows protected your PC" the
first time you run it. Choose "More info" and then "Run anyway". That is the unsigned-file warning,
not a detection.
NOT LISTED: check that the .vst3 is directly in the VST3 folder and not inside a subfolder created
by unzipping. A VST3 on Windows is a single FILE, so a folder containing one is not installed.
TWO PLUGINS WITH THE SAME NAME: the id in morpheus.plugin.json is what hosts key on, and two plugins
sharing one shadow each other. Change the id and rebuild.
CONNECTING IT TO MORPHEUS
Some compiled apps can sign in to Morpheus from inside the app, so the work they do is
billed to your own account. That is a device login: the app shows a short code, you
approve it in your browser on the Morpheus site, and the app picks up a token scoped to
one capability. If the app has no such screen, it does not need one.
--------------------------------------------------------------------------
THE PROJECT'S OWN NOTES (none shipped)
--------------------------------------------------------------------------
This project did not ship a README, so there is nothing here to quote. Morpheus will
not invent one: it has not read the app's interface, and a manual that describes menus
that do not exist is worse than a short one. What the app does when you open it is the
authority.
--------------------------------------------------------------------------
End of manual. the app itself is the authority on what it does.
Audio Plugin — Linux ARM (VST3 · CLAP)
============================
Your project — user manual
============================
What this is : a Audio Plugin — Linux ARM (VST3 · CLAP) build, compiled for you by Morpheus
Generated : 2026-10-18
This file travelled with your download. It covers installing the app, starting it, and
the things that platform does to unsigned software. It is written from what Morpheus
knew at compile time — for what the app does once it is running, see the project's own
notes at the bottom.
INSTALLING IT (Audio Plugin — Linux ARM (VST3 · CLAP))
THIS PLUGIN IS FOR LINUX ON ARM (aarch64) ONLY — a Raspberry Pi 4, Pi 5, or another ARM64 Linux
machine. It will NOT load on an ordinary Intel or AMD Linux desktop: a plugin is compiled for one
instruction set, so a build for a Pi and a build for a laptop are different files even though both
are "Linux". If you are on an x86-64 Linux desktop, this is not the build for you.
There is also no Audio Unit in it — only Apple has those — so this download has three files where
the macOS one has four.
You downloaded THREE zips because a plugin is three files in different places, and a host only looks
in its own. Unzip them and move each one to its folder:
VST3 -> ~/.vst3/ (just you) or /usr/lib/vst3/ (everyone, needs sudo)
CLAP -> ~/.clap/ (just you) or /usr/lib/clap/ (everyone, needs sudo)
standalone -> anywhere you like, but make it executable: chmod +x <name>
The VST3 is a FOLDER, not a file — copy the whole <name>.vst3 directory, not the .so inside it.
If a folder does not exist, create it: mkdir -p ~/.vst3 ~/.clap
STARTING IT
THE BLOCKS AND THEIR ORDER ARE YOURS. The plugin runs the signal path you arranged in the app —
the COMPILE panel's SIGNAL PATH button — and that arrangement is saved in morpheus.plugin.json as
the "board" key, so the file you are reading the rest of this from says what this plugin does.
A MODEL MAKES IT AN AMP. Put a .nam file in the project — models/ is the usual place, or name one in
morpheus.plugin.json as "model" — and rebuild. The model is baked into this download, so there is
nothing to install beside it. Without one the plugin is a stereo gain stage, which is what you have if
you are reading this and expected an amp sim.
A CABINET MAKES IT SOUND LIKE A RECORDING. A .nam is usually the amplifier; the speaker is a
separate convolution. Put a .wav impulse response of your cabinet in the project — models/ is the
usual place, or name one in morpheus.plugin.json as "cab" — and rebuild. It is baked into the
download the same way, so there is nothing to install beside it.
A host scans its plugin folders at startup, so RESTART IT — a plugin installed while it was running
usually will not appear.
THE STANDALONE NEEDS A DESKTOP. Its window is X11, so it runs on Raspberry Pi OS with the desktop,
and it does NOT run on a headless Pi OS Lite image — there it fails with a display error, which is
not a broken build. On a headless Pi the format to use is the VST3 or the CLAP, loaded by a host.
The plugin is listed under the vendor name from its manifest, not under "Morpheus", unless that is
what you put there.
THE PI NEEDS ENOUGH OF IT: a Pi 4 or 5 runs the plugin comfortably; a Pi Zero or a Pi 3 will load it
and may not keep up, which sounds like crackling and dropouts rather than an error.
IF IT WILL NOT OPEN, OR WILL NOT START
NOT LISTED: almost always the folder. Check that the .vst3 FOLDER (not the .so inside it) is directly
in ~/.vst3, and remember that a host launched from a different user account sees a different home.
WRONG MACHINE: if you copied this to an Intel or AMD Linux box it will not load, and the error names
the file rather than the reason. Build the LINUX ARM route for a Pi and use a Linux x86 route for a
desktop — they are different downloads on purpose.
NOT SIGNED, AND ON LINUX THAT BARELY EXISTS AS A CONCEPT: plugins load unsigned here. A plugin that
does not appear is in the wrong folder or was skipped by the scan — not blocked by the system.
A HOST THAT LOADS NEITHER FORMAT: LV2 is the other common plugin format on Linux, and this build does
not produce it. Check that what you are loading into takes VST3 or CLAP before rebuilding anything.
TWO PLUGINS WITH THE SAME NAME: the id in morpheus.plugin.json is what hosts key on, and two plugins
sharing one shadow each other. Change the id and rebuild.
CONNECTING IT TO MORPHEUS
Some compiled apps can sign in to Morpheus from inside the app, so the work they do is
billed to your own account. That is a device login: the app shows a short code, you
approve it in your browser on the Morpheus site, and the app picks up a token scoped to
one capability. If the app has no such screen, it does not need one.
--------------------------------------------------------------------------
THE PROJECT'S OWN NOTES (none shipped)
--------------------------------------------------------------------------
This project did not ship a README, so there is nothing here to quote. Morpheus will
not invent one: it has not read the app's interface, and a manual that describes menus
that do not exist is worse than a short one. What the app does when you open it is the
authority.
--------------------------------------------------------------------------
End of manual. the app itself is the authority on what it does.