PRODUCTS
ABOUT
PRODUCTS
ABOUT
INPUT THEORY
There has to be a better way.
There has to be a better way.
There has to be a better way.
We build software for problems that should have been solved already.
Input → Theory → Solution.
Input → Theory → Solution.
Input → Theory → Solution.
Understand the problem. Challenge the assumptions.
Engineer the solution.
Find the problem. Engineer the solution.
Engineering solutions is what I do.
Engineering solutions is what I do.
Engineering solutions is what I do.
Throughout my career—and just as often in my free time—I keep finding myself doing the same thing: noticing something that doesn’t work as well as it should and figuring out a better way to do it.
Throughout my career—and just as often in my free time—I keep finding myself doing the same thing: noticing something that doesn’t work as well as it should and figuring out a better way to do it.
Sometimes that’s technology or infrastructure. Sometimes it’s a workflow. Sometimes it’s a tool that almost solves the problem. Sometimes it’s something that simply doesn’t exist yet.
Sometimes that’s technology or infrastructure. Sometimes it’s a workflow. Sometimes it’s a tool that almost solves the problem. Sometimes it’s something that simply doesn’t exist yet.
The domain changes. The process doesn’t.
Input Theory gives that process a home.
Input Theory gives that process a home.
THE FIRST INPUT THEORY PROJECT
Plugin Oracle
Plugin Oracle
Plugin Oracle
After years of making music, accumulating plugins, and moving between systems, I kept running into the same problem: I no longer really knew what I had.
After years of making music, accumulating plugins, and moving between systems, I kept running into the same problem: I no longer really knew what I had.
Plugins were duplicated. Some were outdated. Some I’d forgotten about entirely. Sometimes I’d go looking for something new without realizing I might already own a plugin capable of doing exactly what I needed.
Plugins were duplicated. Some were outdated. Some I’d forgotten about entirely. Sometimes I’d go looking for something new without realizing I might already own a plugin capable of doing exactly what I needed.
I had plenty of ways to install plugins and plenty of places to buy more. What I didn’t have was a good way to understand the collection I already owned.
I had plenty of ways to install plugins and plenty of places to buy more. What I didn’t have was a good way to understand the collection I already owned.
So I started building one.
EXPLORE PLUGIN ORACLE →
Plugin Oracle is the first project.
Plugin Oracle is the first project.
Plugin Oracle is the first project.
It won’t be the last.
It won’t be the last.
It won’t be the last.
Different problems. Different domains. The same process.
Different problems. Different domains. The same process.
Find the problem. Engineer the solution.
Stay in the loop.
Stay in the loop.
Plugin Oracle updates, release news, and new Input Theory products.