• More mute groups
• More sub groups
• Ability to cascade servers for more dsp.
• Ability to route a group within a group while retaining latency compensation.
• Option to route any plugin post fader.
• Send the listen function of Plugins only to the cue bus.
• Clear peaks in the small icon of the custom layer tabs.
• Ability for assigned devices to retain their given name.
• A better way to navigate scenes from the drop-down menu with fewer sub menus.
• More mute groups
Yes and more:
- Patch change between scenes (for festivals please !)
- Cue to matrix
- Crossfade between scenes
- Fader to send specific channel to aux
For scene, a load before recall will be cool
Adding to this,
1- More User Defined Keys were available (F1-F8 could be F1-F12)
2- Session structure like the Digico workflow where you can assign busses/matrixes etc from a list rather than 16/32/64 I/o presets.
3- Redundant Servers could be used alongside rather than as a spare… (maybe FX processing only as a start? or Rack A attached to 1 server, and Rack B attached to the other?)
4- HUI was supported, allowing XTouch’s to receive Metering Data
5- possiblility of making the User Defined Keys more script editor based like Digico’s macros. Or have more than one use assigned to each button.
6- OSC / More Key commands were included in the software
7- Secondary displays could have more than one screen open on it in the same tab, rather than having multiple windows open. eg, channel, patch and scene all on one screen, with mixer 1&2 and setup on the other.
8- Move faders off the screen to allow more space for Aux/Rack, etc, when using a controller
9- Scaleable GUI for LV1, even if its just 1080p rather than a full range of options.
@DanBamberAudio about what you said:
- Yes, a lot of user defined keys and maybe potar could be cool, with keyboard shortcuts and Mackie commands
- Could be great but it change completely the workflow and the licences. It will be a HUGE update, complete rethink of LV1
- That’s what @nikolakogr said about cascade server for more DSP. Today extreme server is too weak to handle 64 channels and 16 monitors with lot of processing.
- YES !
- Yes, and/or keyboard shortcuts, for devices like streamdeck that can emulate keyboard
- Why not, i only use one screen, but i know what you mean
- Why not just go to channel window when you use a controller ?
- Maybe one day…
I think Waves does an incredible work with this console but today, some little things limit its use cases. By example, I’d love to put it on a festival, where a lot of sound guy could discover it but the patch is lock to one session…
I understand that the dev take time, and the console is young.
It will be cool if users could directly propose improvements to the Waves team and see the progress of the project, as MusicGroup with the X/M32
It will be incredible if users can have access to Beta version of the soft, not for production, but for REX.
Totally love all this requests here
More mute groups
More sub groups please!
Fade times between scenes and more specific “scope “ of scenes
Allowing to recall only specific slots on specific inputs
Ex only plug in slot 3 on one channel is recalled.
The rest of the channel is safe
3- Redundant Servers could be used alongside rather than as a spare…
The ability to run the console on one server and do all the plugin processing on a second server would solve a lot of issues. I hardly run into any issues when using super rack but run out of horsepower quickly in LV1.
on “sends on fader” use the same color coding on the “send select” buttons (top row on fit) instead of the factory ones (f.e. I use different colors for InEar vs. Wedge monitor and for FX send Aux)
bus to bus routing : f.e. I normally group my drums and have a NY-style parallel group. Rest of the band is routed to another bus (maybe a touch of overall shaping on that group, more kind of ProTools like approach of mixing)
FX to group routing: f.e. I group my vocals and drums and band in extra groups, therefore gives me ability of overall tone shaping this groups. Also doing fast releveling - therefore I route my respective FX to the same group (f.e. vocal verbs and delay to the vocal group, so setting different level in the group doesn’t affect the ratio dry/wet)
headphone correction curve in the cue section → using headphone in live situation is kind of normal, but loud headphones (like the old trusty HD25 or SRH840) aren’t pretty linear. We use an love this tools in studio mixing (like NX and the respective corrections), so I won’t need the emulation of the room/space, but just near to linear headphones.
a trigger module: just a simple plugin like a SmackAttack,but with the ability to blend in a sample (f.e. to fatten toms, where massive cymbal-bleed is all day issue in live situation).
ability to accumulate the power of a second server - as someone already stated: it is pretty clear that routing audio to different servers is a big thing in terms of latency, phase coherency (where LV1 does a pretty damn good job!) etc. But maybe having just the mixer itself - the “backbone” so to speek - on one server and the plugins slot on another server (like an lv1 internal superrack) could be a better to realize option?
The biggest thing for me is scene fading. I love so much about how LV1 works. But having a fader level value snap is rough. It would add so much functionality to the system if they allowed crossfading of these values. I don’t even need it for plugin parameters. Just faders. I’m considering getting creative with HUI or MIDI input to make this happen.
Strong Second. We have 2 LV1’s and they are really great with DigiGrid IOX’s. The main ask to be totally happy with this platform would be to have the Show capabilities expanded.
I really think the server idea is brilliant. Would be more useful to have a more capable stable system than a backup to switch to. After 4-5 plugins on each channel and Extreme gets taxed after 20-24 channels.
Some of these have been posted by others already but here is my running list that I’ve been keeping:
- Ability to label Mute Groups
- Ability to label Talkback Presets
- MIDI and/or keyboard shortcut control of Mute Group On/Off
- MIDI and/or keyboard shortcut control of talkback presets On/Off
- Crossfade time when recalling scenes
- CUE Bus as input to Matrix
- Ability to route Groups to Groups
- Ability to route FX Channels to Groups
- Update screen resolution to at least 1080p
- Map plugin controls to FIT Controller encoders
Here are some additional feature and fix requests for LV1
-Add ability to delete/modify channel presets
-Fix FIT controller not remembering MIDI port I/O on startup
-Add global tuning key for Waves Tune Real-Time
-Make scene recall time faster
-Add ability to delete session files from inside LV1
-Add fade time to scene changes
-Fix LV1 not recalling saved channel count on mounted SoundGrid Driver device
-Add DSP usage level on individual plugins/racks
-FIT controller scribble strip too hard to read
-Fix input lag time on FIT controller layer change and fader flip buttons
-Fix some plugins not fitting inside LV1 plugin window
-Fix pan/stereo width pot controls not being easy to manipulate either with touchscreen or mouse
-Fix plugin slots not always responding accurately to touchscreen press in mixer window
-Add option to require mute group buttons to be long pressed before turning on/off to avoid accidental presses on touchscreen
Given what little I understand of the DSP server in LV1 I don’t think ‘cascading’ works. I think they would need to create a cluster with servers linked by 10Gbit (or higher) RDMA on the backend.