Request for scene change via LTC.
5 Likes
Request VUs on DCA/LINKS
5 Likes
Fader caps or whole fader change colors to match Gang assignment in MyMon
Or some other easy way to see what channels are assigned to what Gang when on the Faders tab of MyMon.
2 Likes
Align colors in the Channel Color pop up.
Perhaps in columns from light color to dark color.
i.e light Green
Medium Green
Dark Green
3 Likes
User buttons and Mute Groups/ Layers stay visible when on channel view
4 Likes
Latching talk back button Option.
In the talk back setting it be great to choose if it was momentary or latching. In past videos Iv seen where double tapping the talkback latched it but this seems to have gone away.
2 Likes
Custom Colors for User Keys on lv1 classic.
Flashing User button when User Key is selected.
Or a more clear way to tell that User Key is selected vs Channel Select.
Also Stream deck integration for User Key would be a game changer.
Option to Store & Recall at the same time when making new or updating Scenes
Option for scene notes to pop up for a selectable amount of time. With a very large X button
Subscene or snap shots to be able to change multiple scopes with one scene change.
Touch and Drag in the scene scope window
Custom layers begging apart of scene would be HUGE
Recall names and colors on channel presets.
2 Likes
It would be great to have an online version of the Session Editor.
I know you can control it on iPad, but I would really like to see it on desktop as well. It would be useful if someone’s using it both for front of house and broadcast, and someone wants to sit in another room with the mix controls pulled up on a computer. I believe the Avantis and DLive both have online desktop apps, it would be great to see that come to LV1 as well.
1 Like
Here is some plugin request for eMotion LV1 :
- Drum Trigger plugin with 0 latency like aptrigga3. It would be very nice
- Impulse Response Live loader plugin like Cabinetron
1 Like
Here is our list:
- either having more AUX Busses (like 32…40 instead of the current 24) or change to flexible busses (like many other consoles on the Market) where the SubGroups and MTX-es could be used as AUX Busses as well
- Plugin Inserts in two different Insert points. (Like for example Pre and Post Fader, or just for making possible to use AUX sends points from between Plugins in the signal chain)
- Making possible that all Busses have direct inputs for easy cascading two (or more) consoles. Also implement some features for this special usecase for cascading the solo (cue) BUS and the solo clear function etc.
- Implement FLIP mode for BUSSes as well
- Implement FADER BANK function where two (or three) FIT controller could follow functions like FLIP mode (Sends on Fader) at the same time (makes Monitor mixing easier)
- Add the option to use an extra display just for the overview of all channels (ALL level meters are now part of Mixer1 and Mixer 2 view, but to move this to an extra screen would make things easier)
Thanks,
Tamas
1 Like
Which drivers you use?
I’d love to have a way to favourite certain plugins, that would then appear either at the top of the menu or in its own breakout (rather than the alphabetical groupings). I still like the breakdown by type, as I’m usually thinking “need EQ” or “need a gate” already, but having to then figure out which one I want before seeing the list really slows me down.
Somewhat related, it’d be nice to see an indication of which plugins are going to adjust latency compensation before adding them. When I’m trying to deal with things during a show, the last thing I want is an audible gap in every other channel because I accidentally picked something with latency. (But if I could mark favourites, I’d just not mark any that do this, so this part is just nice to have if the other existed.)
2 Likes
This is almost a complete copy and paste from my annual update in this thread. I realize Waves can’t accommodate every request but I find it frustrating that some features have been requested since LV1 was released and they still haven’t been addressed or implemented. For me, the LV1 platform has been solid, reliable, and it sounds great. I have both a scaled down fly rig and a full tour rig. The ability to put a card in the bands monitor board and do the split digitally in the SoundGrid network saves time and weight while allowing me to send my talkbacks and select processed channels to and from both boards. When people ask me how I like the LV1, I mostly tell them the above. In addition, having the consistency between my main and fly rigs is amazing. For about the last two years though, I’ve been following that up with if I wasn’t so heavy invested in the waves rig, I would probably buy a DLive. And I think that sucks. I like the LV1 platform. But, as a high level professional user, I don’t think waves is putting enough effort into it. I find Waves tech support second to none which is a big reason I’ve stuck with it for as long as I have, as well as having a palate of processing I’m very familiar with and know exactly what to reach for in almost any situation. However, productions are evolving and have higher and higher demands. I just don’t feel like Waves is as dedicated to this platform as they should be. I’ve been a waves user since v6 and I currently have licenses for everything they make. No subscriptions, no endorsements. I’m very familiar with Waves products and have generally been very satisfied with their products but for the first time I feel like my support for them is wavering. Hopefully releasing the classic will light a fire under them but my hopes aren’t very high these days.
That being said, here is a continuation of my running list of LV1 feature requests. Hopefully we’ll see some of them in the near future. Some essential, some nice to haves.
*Label talkback presets (I like that you can now see the the names assigned to busses but I still want to label the presets such as talk to band, drum tech, artist, band and artist, everybody, etc.)
-
Label Mute Groups
-
Scene Crossfades - This needs to be a priority and we have been asking for this since LV1’s inception. We really only need main faders and sends. My 01v was capable of this in the 90’s and just about every other console on the market has this capability. Not sure what the hold up is, especially for a console that is now approximately $8,000 to start.
-
Assign FX to Groups - the feed forward design is frustrating and limiting. Without a total redesign it is what it is but, maybe you could reorder the architecture so the groups are later in the chain. Or, find a way to let us define the order.
-
Option to have the mutes in the FX busses control the input rather than the output so when I mute the FX at the end of the song it doesn’t kill the reverb tail.
-
Similar to EQ and dynamics, designate certain plugins as Effects and make that a selectable option in scene scope and recall safe
-
Allow direct midi or keyboard shortcuts to all functions that can be assigned to user define keys - I’m finding a need for this more and more especially with the FIT and Classic sharing user define and select keys. OSC would be a great solution as would support for metering.
4 Likes
Am I missing something or are these both here already? Groups have a “Pre Fx”/“Post Fx” button that is entirely unexplained, but when switched to Post FX it seems to reroute just that group so that it can take FX inputs but can’t be sent to FX busses anymore.
I might be wrong on the second one, but I use the fader set to control the input. Maybe that doesn’t change the mute and I’ve never noticed? Of course, if you’re sending FX back into groups and muting the group then it’s getting muted anyway, so maybe this just needs some clever routing.
Yes please. Big big big yes please.
1 Like
Am I missing something or are these both here already? Groups have a “Pre Fx”/“Post Fx” button that is entirely unexplained, but when switched to Post FX it seems to reroute just that group so that it can take FX inputs but can’t be sent to FX busses anymore.
I knew about the Pre/Post update on the groups but I didn’t realize that’s what it did. If that’s true that’s awesome. I’ll have to give it a try.
EDIT: I just tried this. You do indeed gain the ability to send FX to the group but you lose the ability to send the group to another group. For example, if I send snare top and bottom to a group, and feed that group to an fx bus with a tight verb that I want to become part of my snare sound, I can put the group in post mode and this accomplishes what I want, a group that I can process SN top, SN bottom, and SN short verb as a whole. The problem is that now, I can’t send that to my Drum Group. Nor can I send that group to my overall Kit verb.
I’ve been using the monitor busses to do this and it works fine but it seems like I should be able to use groups for this. I feel like the group busses on this console are fairly useless. Maybe the solution is to get rid of them all together and create 8 more monitor busses with the ability to set them as variable or fixed. Similar to the Avid consoles.
I might be wrong on the second one, but I use the fader set to control the input. Maybe that doesn’t change the mute and I’ve never noticed? Of course, if you’re sending FX back into groups and muting the group then it’s getting muted anyway, so maybe this just needs some clever routing.
The way it currently seems to work is I can put the FX bus in Mixbus Fader mode and it allows me to do delay throws as the fader controls the input rather than the output. However, when I have my vocal verb and short delays on a mute group, it appears to mute the output so I het a sharp cutoff of the reverb tail.
3 Likes
I thought you could send it to a later group if that group is also post-FX? But yeah, it’s all pretty complex, and I don’t understand why we can’t just have arbitrary routing (I’d love to be able to assign “external” inserts to internal channels, for example). Familiarity for people who are used to feed-forward routing is a fine reason, but it’s already so much more complex than that it hardly seems worth keeping the “simplicity”.
2 Likes
Hi,
here‘s my list:
- Midi Control for User Keys or direct integration of StreamDeck (in LV1 modular it was possible to do it via HUI/Mackie Control which isn‘t available in LV1 classic) → and no: using mRecall isn‘t a real solution, as it is via WLAN and a smart device has no haptics to the buttons!
- configuarable meters: no the change von green to yellow at -12dBFS, which is too hotel for many modeling PlugIns (like SSLChannel, SSLCom, Sheps73, etc.), they expect -18dFS, so meter is always mitleidig
- keep gain-control in flip-mode: doing monitors I mostly live in flip mode. But I always need to leave, of I need to do some gain changes.
- input solo reverts to output solo: doing monitors I permantly cue the artists mix. Is I need to check a channel, therefore cue it, I want to return to the last mix I cued. Works on many consoles, but not with LV1.
- „link“ mode for Mixer 1 and Mixer 2: in general, of doing FoH and monitors from the same console, the functionality with two independent Mixers is really cool stuff! But it I‘m just doing one or the other I‘d like to combine my LV1 classic with my FiT - but then (as one is on Mixer 1 and the other on Mixer 2) the not really interact. F.E. in Monitors I often have the mixes on the right, inputs on the left and work in flip mode. So I want to cue a mix on the right (mix masters) and the left should follow showing this mix in flip. No the Mixer 1 doesn‘t follow, so there is (allmost) no benefit having more real estate (faders).
Peter
5 Likes
- Snapshots triggered by incomming timecode
- Better granularity in the scope (see avid s6l)
- Events/macros (also able to trigger from smpte timecore or osc or midi or user keys)
2 Likes
- Very simple, when you recall a channel preset it should also recall the name of the channel from when the preset was saved!
- Presets for Montors should also recall the mix for that monitor and name of the monitor.
- A more easy to understand recall scope.
- Link/DCA to show a sum meter of the channels in it.
- The ability to spill a group like you spill a dca.
- Recall-able custom fader banks, custom fader banks in the sense scope.
- A scope for sessions/templates.
- Ability to have LR feed Center & Mono or the ability to lock the fader together (links works until you try to move a DCA fader. Now that DCA is a link and your LR,C,M link just became a DCA
- The ability to choose a DCA and lock it as a DCA and the ability to Lock a Link as a Link! So frustrating.
- Stream deck/companion control.
- User defined on screen buttons stay visible when in channel view.
- Custom colors for user defined keys
- Name mute groups.
- Sense CROSS FADE!!
4 Likes
Only one major request.
Ability to move channel strips around and have them change number. Much needed if your rider has one additional ftom all of a sudden.
And no, its not the same as custom pages. The Old avid venue had this and it was perfect.
4 Likes