On July 30, 2026, Ravine DSP shipped a free update for its Inter::State plug-in host, and it could permanently change how Windows producers wrangle effects. Version 1.3 adds Slot Scenes, a system that captures up to eight complete parameter snapshots for any hosted VST3 or AU effect. Instead of copying a plug-in twelve times across your arrangement and automating bypasses, you can now store a clean pass, a distorted blowout, a telephone filter, and five other states directly inside a single slot—then switch, blend, or crossfade between them with a click, a MIDI note, or a tempo-synchronized curve.

No extra automation lanes. No duplicated instances chewing CPU. Just the effect, and its eight personalities, waiting to be performed.

What Actually Arrived in Version 1.3

Inter::State has always been a three-rack effects host that wraps your existing plug-in collection inside a unified routing view. You could already build serial chains, parallel splits, multiband setups, and send-style paths without leaving one insert slot. Version 1.3 extends that container concept with Slot Scenes, and the implementation is both deep and DAW-friendly.

For each hosted plug-in slot—whether it’s a single compressor, a reverb, or an entire chain—you can now save eight parameter snapshots. Those snapshots optionally include the slot’s mixer settings, so a scene can change gain staging and panning at the same time it reshapes the effect’s character. The headline, though, is how you move between scenes. Ravine DSP gives you three distinct transition modes:

  • Selector: Instant recall. Tap a scene and the plug-in jumps to its stored parameters immediately. No glide, no blend—ideal for A/B comparisons or hard effect changes that happen on a beat.
  • Morph: A continuous blend between adjacent scene slots. If Scene 1 holds a subtle room verb and Scene 2 a cathedral wash, Morph sweeps the parameters gradually as you move the control, letting you find every texture in between.
  • Crossfade: Tempo-synchronized transitions that lock to your project’s BPM. You set a musical duration—quarter note, two bars, whatever—and Inter::State fades from the current scene to the destination over that span, with the crossfade position tied to the transport.

Tucked behind all that scene-jumping is a zero-latency Auto-Gain system designed to keep level spikes in check. When you morph from a thin, scooped EQ to a bass-heavy distortion, Inter::State aims to prevent sudden volume jumps that could clip your output or throw off a live set. It’s a utilitarian safety net that makes Slot Scenes viable for on-the-fly tweaking rather than something you’d only trust during sound design.

Why This Matters for Your Workflow

If you’ve ever duplicated a reverb plug-in on three different return tracks just to toggle between short, medium, and long decays, Slot Scenes are aimed straight at you. The same goes for producers who stack multiple EQs on a vocal bus to audition different tonal balances, or anyone who keeps a folder of “print” tracks with frozen versions of a single effect at different settings. That approach wastes CPU cycles, bloats project files, and turns recall into a hair-pulling exercise. Inter::State 1.3 folds all those variants into one tidy container.

For home users and hobbyists, the upshot is simplicity. Imagine a guitar chain where a single amp sim hosts scenes for “clean intro,” “crunch rhythm,” and “lead with boost.” Switch on the timeline with a Program Change message or an automation lane controlling the Scene Selector, and you’ve replaced three duplicated plug-ins and a maze of automation with exactly one insert. Similarly, a synth buss can cycle through filter scenes without duplicating FilterFreak or Volcano instances. You spend less time managing plug-in counts and more time making music.

Power users and professional producers will see an immediate benefit inside complex templates. Orchestral templates often run dozens of instrument tracks, each with its own compression and EQ settings for different articulations. Prior to 1.3, maintaining those variations meant either separate instances per articulation or heavy automation. Now, one Inter::State instance per section can store scenes for legato, staccato, and pizzicato processing, with crossfades that follow tempo changes. In the mix stage, a mastering chain loaded with a limiter, an EQ, and a clipper can store scenes for loudness targets, referencing presets, and dynamic EQ profiles—all recallable without rebuilding the chain.

Live performers on Windows get a particularly interesting tool. Because Slot Scenes can be triggered via MIDI and the transitions can be beat-synced, a single MIDI controller can move an entire effect rack from verse to chorus processing, with crossfades locked to the downbeat. No laptop required beyond the DAW that’s already running your backing tracks.

How We Got to Scene-Based Effects Hosting

VST and AU plug-in hosts aren’t new. Metaplug-ins like Blue Cat’s PatchWork, DDMF’s MetaPlugin, and Plogue’s Bidule have let users chain and route effects inside a wrapper for years. What’s changed is the sophistication of state management. Most hosts can save “presets” that capture the entire wrapper’s configuration, but toggling between settings inside a single hosted plug-in usually meant either loading different presets on the host (which can introduce audio dropouts) or using parameter automation—which gets messy fast when you’re dealing with 50-parameter synths or reverbs.

Ravine DSP’s approach mirrors how modern sampler instruments store multiple articulations under one key switch. By attaching eight snapshots directly to the hosted plug-in slot and providing performance-friendly transitions, Inter::State 1.3 effectively makes the effect into an instrument with playable timbres. It’s a continuation of the trend toward fluid signal chains that blur the line between mixing and performance.

The inclusion of zero-latency Auto-Gain also reflects a growing awareness that parameter changes in effects—especially distortion and dynamics processors—can cause dramatic level spikes that ruin the moment. Some DAWs offer built-in gain staging tools, but placing this correction inside the scene engine, before the audio hits the next process in the rack, means you’re protected even when chaining multiple scene-capable slots.

What to Do Right Now

Inter::State 1.3 is a free update for anyone who already owns a license. If you haven’t tried it, Ravine DSP offers a seven-day unrestricted trial that includes all the 1.3 features. The Founders Edition is currently priced at $69 or €60, and the developer has announced that the final price will rise to $99 or €85 at a later date—so waiting to buy carries a real cost.

The plug-in runs as a 64-bit VST3 on Windows 10 and Windows 11. Audio Unit support is available for macOS. It plays nicely with Ableton Live, Cubase, Reaper, and other major DAWs. System requirements are light—if your machine can run the plug-ins you want to host, it can run Inter::State.

When you install the update, open an existing project and start by right-clicking any hosted plug-in slot to reveal the Slot Scenes panel. From there you can capture your first snapshot, assign a transition mode, and map MIDI controllers or host automation to the scene parameter. The included Inter::State Bridge plug-in also exposes eight global macro controls that can be shared across multiple Inter::State instances in a project via zero-latency shared memory, which is worth exploring if you want a single knob to morph entire racks across your session.

Pro tip: For the cleanest crossfades, engage Auto-Gain and test the extremes. If a morph still produces a noticeable bump, you can insert a dedicated gain plug-in as the last processor in the slot and include its level in the scene snapshots, giving you per-scene output trim independent of the auto-gain algorithm.

What We’re Watching Next

Ravine DSP has positioned Inter::State 1.3 as the update that pushes the tool from a routing utility into a creative performance environment. The obvious next question is whether future versions will expand the number of scenes per slot beyond eight, or introduce macro controls that can blend multiple slots’ scenes simultaneously. With the Bridge system already enabling project-wide control, a scene-sequencing engine that steps through snapshots in a user-defined order—similar to clip-launching in Ableton Live—would be a logical evolution. For now, Windows producers tired of drowning in duplicate plug-in instances have a concrete, immediately usable way to slim down their sessions and open up new performance possibilities.