Detached interfaces
Creative decisions scattered across overlapping plugin windows.
Independent audio software
Tools that keep you in flow.
Ravine DSP is a one-person software company founded by Craig Lopez, building focused tools for faster, more tactile music workflows.
Why it started
I wanted to have the same kind of fun using a controller on a full mix that I have using a two-channel mixer when I DJ.
I wanted plugin chains to feel playable.
Powerful tools. Fragmented workflows.
After using Cubase since the mid-90s and plugins since their earliest days, the same barriers kept appearing between the idea and the result.
Disposable mappings
Custom control setups that only make sense once.
Too much friction
More time managing the setup, less time playing it.
The response
Inter::State is my answer to that.
Ravine DSP is not about replacing the tools you already know. It is about helping them work together better.
Less window management. Less repeated setup. More direct control over the effects you already own.
Why Ravine?
It sits between the giants.
“Because things that flow deep, flow quietly.”
The company
Ravine DSP is developed by me, Craig Lopez.
Being a solo developer means I can build products I genuinely want to use myself: no committee, no trend-chasing, direct support, and a long-term interest in making software that earns its place.
Some people will know me from Tutorial[ism], the YouTube channel that evolved into Ravine DSP.
Early in development, I worked with Manish Verma, who helped get the project off the ground. Inter::State is now developed by me, and I remain grateful for that early contribution.
What guides the work.
Focused software should make a complex workflow more coherent without getting between the musician and the result.
Use what you own
Connect and control existing tools instead of demanding a replacement ecosystem.
Make it playable
Turn detailed software workflows into tactile, expressive control.
Keep it direct
Build useful products, provide direct support, and improve them through real use.
See what that philosophy built.
Explore Inter::State or watch the workflow in action.
