For those of us using Live to choreograph and run large Live sets with virtual MIDI buses running audio, video, and DMX lighting, the limitation of only being able to MIDI-map a single virtual MIDI port becomes a limitation.
I'd like to be able to MIDI-map multiple virtual MIDI ports.
MIDI-mapping with multiple virtual MIDI ports
-
Kevin Hamler
- Posts: 26
- Joined: Tue Nov 23, 2010 8:32 am
- Location: California
MIDI-mapping with multiple virtual MIDI ports
(The artist formerly known as hambone1)
-
Crystal Jack
- Posts: 5
- Joined: Thu Jan 15, 2015 7:06 am
Re: MIDI-mapping with multiple virtual MIDI ports
Ableton, can we get a response to this please? This is a significant limitation specifically with Ableton for trying to conserve CPU, whether you're doing orchestra or not.
Since Ableton doesn't provide any way to completely disable tracks, we are forced to rely on 3rd-party M4L devices like Mudo, but this is still not sufficient because it requires loading Mudo itself on each track which must remain enabled and also takes some CPU itself.
You've effectively blocked every opportunity to conserve CPU when either doing orchestra music requiring a large number of instruments, or when trying to build a template of curated sounds for EDM or any other genre.
This is a long-time active issue with support from many many customers. Several other major DAWs support this functionality, and it makes no sense for VSL and VEP to change it. This is something that needs implementation in the DAW, to support multiple ports.
Without either this or completely being able to disable a track to conserve CPU, you are seriously impeding my workflow and productivity.
Please give us a response, please make this a priority.
Thanks
Since Ableton doesn't provide any way to completely disable tracks, we are forced to rely on 3rd-party M4L devices like Mudo, but this is still not sufficient because it requires loading Mudo itself on each track which must remain enabled and also takes some CPU itself.
You've effectively blocked every opportunity to conserve CPU when either doing orchestra music requiring a large number of instruments, or when trying to build a template of curated sounds for EDM or any other genre.
This is a long-time active issue with support from many many customers. Several other major DAWs support this functionality, and it makes no sense for VSL and VEP to change it. This is something that needs implementation in the DAW, to support multiple ports.
Without either this or completely being able to disable a track to conserve CPU, you are seriously impeding my workflow and productivity.
Please give us a response, please make this a priority.
Thanks