Loading the starting session
Built from factory default sessions.
Waves publishes a free eMotion LV1 Session Editor for working on sessions away from the console. It's a separate tool from this one, and it requires a Waves account.
Download LV1 Session EditorUse your own .emo file if you already have a session built.
Or click to browse
Not affiliated with or endorsed by Waves Audio. Always keep a backup of your original scene file.
This reads a fixed set of command shapes rather than free-form language, and always shows what it understood before applying. Anything it cannot parse it refuses instead of guessing.
add 6 stereo tracks channels after the guitarsadd 4 mono vocal channels at channel 20make matrix 2 a lobby feed that includes all groupsname matrix 3 broadcastsend all groups to matrix 2send drums and vocals to matrix 4remove tracks from LRmake channels 10-12 stereomake the drums redBuses can be named or numbered: matrix 2, mtx 2, Broadcast, LR. Sources can be all groups, all channels, a group name, a family like guitars, or channels 4-9.
Switching rebuilds the scene from the factory default for that configuration, then re-applies your channel names, stereo settings, colors and bus assignments wherever those channels still exist.
Channels that do not exist in the new configuration lose their settings. Plugin racks from a loaded file are not carried across.
Your channel names and bus assignments are written to every scene in the file.
| # | Name | Note |
|---|
Record the computers and I/O boxes this rig uses. The totals are checked against your chosen configuration.
| Category | Model | Qty | Inputs each | Outputs each |
|---|
Anything you want saved into the file alongside the inventory: patch quirks, who to call, what the spare channels are for. It shows up in the session notes on the console.
A workbook pre-filled with your current channel list. Fill in names, stereo, colors and bus assignments offline, then upload it below. It also carries a sheet for your system inventory and a reference sheet listing every valid value.
Accepts .xlsx, .xls and .csv. A workbook downloaded above is recognized automatically and imports names, stereo, colors, buses and inventory in one go. Any other spreadsheet falls back to choosing columns by hand.
One name per line, in channel order. Blank lines skip a channel and leave it untouched. Prefix a number, like 20: Lead Vox, to place a name out of order. Add (stereo) or (st) after a name to make that channel stereo, or (mono) to force it back. The marker is stripped from the name.
Only channels active in this configuration are shown. Colors are set automatically from the channel name unless you pick one yourself.
| # | Type | Inputs | Mode | Source | Color | Name |
|---|
Names groups 1 to 8 Drums, Drums PC, Guitars, Keys, Aux Inst, Tracks, Vocals and Speaking, then assigns every named input channel to the group its name suggests. Drum shells also go to the parallel compression group; hi hats, overheads and cymbals do not. Click is never grouped, because every group here feeds the mains.
A channel lands in one family only, tested drums, aux inst, keys, guitars, speaking, vocals, then tracks. So "Bass Drum" is a drum, "Bass Trombone" is aux inst, "Bass Synth" is keys, and "Bass DI" is a guitar. "Tom 1" is a drum but a bare "Tom" is a person. Anything that fits neither guitars nor keys, like a violin or a trombone, goes to Aux Inst. Anything that matches nothing but reads like a person's name is treated as a vocal, which is a guess and worth checking below.
Which destinations each input channel feeds. Click a column heading to toggle the whole column.
Your file is ready. Before you take it, here's an offer worth about an hour of my time and nothing of yours.
Send me a multitrack of one of your services. I'll load it into this exact scene on my own LV1 Classic, mix it, and send you back a video walking through what I did and why: where your groups are fighting each other, what the vocal actually needs, what I'd change about your input list. You get a real second opinion on your own service, not a generic tutorial.
Your session is never sold, never passed to anyone else, and never used to train anything. The one question I have to ask is below, and your answer is binding either way: say no and the mix stays strictly between us.
Clips of the mix in a teaching video or on social. Answer either way, both are fine.
Drop the scene file you're about to download into the same folder as the multitrack. Then I'm mixing on exactly what you built, and the walkthrough matches what you see on your console.
Not sure how to share a large folder? Open the one you use.
On a Mac
On Windows
Multitracks are large. If the zip is over a few gigabytes, upload it overnight or send a link to the folder rather than the files.