When a sound sits in the wrong place, more reverb, more width or another EQ move often fixes one symptom and creates another. Field Engine puts every sound on one field, so you decide where it should sit relative to the others, then check it by ear.
macOS and Windows · AU, VST3 and AAX on macOS, VST3 on Windows
For desktop use. Install on your Mac or Windows PC.
You can hear that something is in the wrong place: the lead is too far back, or two parts crowd the same spot. But the fix is not obvious. Turning it up makes it loud without making it close, and reaching for reverb or width can trade one problem for another.
What you want is a placement. What comes forward, what sits behind it, and how wide the picture can be without losing its centre.
Field Engine gives that decision one shared view. Every sound in your session appears as an object on a single field, with depth and width in the same place. You move an object, listen to what changes, and keep the move only if your ears agree.
Field Engine is one product. Field Feed is the small track-side component that places each track on the field. It is installed with Field Engine and is included in the price.
Field Engine works with the same perceptual sense of depth and distance you know from Depth Engine (how close or far away something feels, not just its level) across your whole mix at once, with width in the same field as depth. Try the demo in a real session before deciding whether it belongs in yours.
Every object in your mix is placed on the field. Position expresses the relationship: depth, width and how the parts belong together — not just a level or a pan number.
Assign objects to groups, catch them together, and switch between saved views of the field as the session moves from rough balance to detail work.
Put Field Feed on the tracks and buses you want to control, open Field Engine, and the field reflects your session immediately. Field Feed comes with Field Engine.
The same sense of distance behind Depth Engine — how close or far away a source feels — sits at the core of Field Engine too. Here it works alongside width, for every object, in one shared field.
The most useful way to judge Field Engine is not a feature tour. Take one short passage where a depth or width relationship feels unclear, and make a single deliberate change.
The question is whether seeing the relationship helped you reach a better decision with less searching.
The walkthrough shows the workflow in a Logic Pro session: sounds placed on the field, one selected, groups and views. You make the before/after comparison on your own material with the free demo.
Every object in your session appears on the field. Selecting one brings up its Spread, Smear and Gain controls, and its group and view assignment — the same relationship you see is the one you hear.
How could a mixing interface reflect the way people imagine a musical scene?
The idea began around 2003–2004, when Morten Büchert imagined a three-dimensional chessboard on which musical elements could be placed as objects. Their positions would express relationships: depth, width and a visual sense of how the music belonged together.
The intention was to help people explore a balance through listening and placement, without first having to understand every technical step. Distance meant the experience of a sound being further away, beyond a change in level alone.
Büchert approached Steven Gelineck, PhD researcher at Aalborg University, to ask whether the idea could be built, and Jesper Andersen, Associate Professor at the Royal Conservatory of Music in Copenhagen, subsequently joined the collaboration. Research became part of the journey from that initial musical idea towards a practical tool.
The research background includes work on stage-based mixing interfaces: Towards an Interface for Music Mixing based on Smart Tangibles and Multitouch (Gelineck, Overholt, Büchert and Andersen, NIME 2013) and Stage Metaphor Mixing on a Multi-Touch Tablet Device (Gelineck, Korsgaard, Büchert and Andersen, AES Convention 137, 2014).
That history gives context to the design question. The papers describe the research prototypes of the time, not the released Field Engine product. The walkthrough above shows what Field Engine does today.
| Included | Field Engine and Field Feed. Field Feed runs on the tracks and buses you want to control. |
| Plugin format | macOS: AU, VST3 and AAX. Windows: VST3. |
| Platform | macOS 11.0 (Big Sur) or later, or Windows 10 or later (64-bit). |
| Demo | Free demo with no time limit and short periodic audio interruptions |
| Price | €129, excl. VAT. Included in the Buchert Audio Bundle. |
| Version | 1.0.0 |
Field Engine runs in AU, VST3 and AAX hosts on macOS, and has been tested in Logic Pro and Pro Tools. On Windows it runs in VST3 hosts.
Logic Pro tip: with several Field Feed instances in a project, turn off "Only load plug-ins needed for project" (File › Project Settings › General) so every sound appears on the field as soon as the project opens.
Single license. Permanent ownership. No iLok, no dongle, no subscription.
Free demo before you buy · Minor updates within the same major version included · No iLok, no dongle
Field Engine is the shared control surface. Field Feed runs on the tracks and buses you want to control. Field Feed is included with Field Engine.
No. Field Engine includes Field Feed; no separate Buchert Audio purchase is required.
Field Engine runs in AU, VST3 and AAX hosts on macOS 11 or later, and has been tested in Logic Pro and Pro Tools. On Windows 10 or later it runs in VST3 hosts. When you run the Windows installer, Windows may show a 'Windows protected your PC' message. Click 'More info', then 'Run anyway' to continue the installation.
Yes. The free demo has no time limit and includes short periodic audio interruptions, the same model used across Buchert Audio plugins.
Yes. Field Engine is included in the Buchert Audio Bundle, together with Tonality EQ, Warmth Engine, Mass Engine, Depth Engine and Dimension Engine.