I only upgraded to 10 Suite (from 9 Intro) when it was on sale and that was when they brought in VST3 support and I don't think it was there when 10.0 came out.antic604 wrote: Sat Nov 14, 2020 5:29 pm I think it was more expensive because it took 5 years (instead of 3) and it contained a lot of under-the-hood stuff which wasn't flashy, but important and paved the way for high-DPI support, MPE, VST3 and probably other stuff we're only starting to see now.
Ableton Live 11
-
WatchTheGuitar WatchTheGuitar https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=440193
- KVRAF
- 13256 posts since 30 Apr, 2019
-
- KVRAF
- 12084 posts since 2 Dec, 2004 from North Wales
Yeh, I remember it seemed really expensive for what was apparently on offer (especially as Live wasn't the DAW I used most often) and I didn't upgrade until; the 40% off sale, the 10.1 update was more useful to me!
Anyway, I guess that's history now, the 11 update is back on track for both features and cost as far as I am concerned.
Anyway, I guess that's history now, the 11 update is back on track for both features and cost as far as I am concerned.
X32 Desk, i9 PC, S88MK3, S1, BWS, Live + PUSH 3, Osmose, RedShift 6 Pro3, Tempera, Syntakt, Digitone II, OP1-F, OPXY, Eurorack, TD27 Drums, Guitars, Basses, Amps and of course lots of pedals!
-
WatchTheGuitar WatchTheGuitar https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=440193
- KVRAF
- 13256 posts since 30 Apr, 2019
Yes, that was when I did too.SLiC wrote: Sat Nov 14, 2020 5:43 pm I didn't upgrade until; the 40% off sale, the 10.1 update was more useful to me!
- KVRian
- 1426 posts since 30 Mar, 2014
I keep thinking this release should be a 10.5 release, like how 9.5 was so huge compared to 9.
But then, track comping and MPE seems significantly more difficult to implement than simply adding a few new devices and changing some interface bits. And the devices they added are not insignificant either.
But then, track comping and MPE seems significantly more difficult to implement than simply adding a few new devices and changing some interface bits. And the devices they added are not insignificant either.
- Banned
- 11467 posts since 4 Jan, 2017 from Warsaw, Poland
As I said - 10 "paved the way for...".WatchTheGuitar wrote: Sat Nov 14, 2020 5:43 pmI only upgraded to 10 Suite (from 9 Intro) when it was on sale and that was when they brought in VST3 support and I don't think it was there when 10.0 came out.antic604 wrote: Sat Nov 14, 2020 5:29 pm I think it was more expensive because it took 5 years (instead of 3) and it contained a lot of under-the-hood stuff which wasn't flashy, but important and paved the way for high-DPI support, MPE, VST3 and probably other stuff we're only starting to see now.
For me 10 was HUGE, because it added high-DPI and trackpad gestures support - 2 things that made me leave Live for Bitwig in late 2017. So I guess it's subjective
-
- KVRAF
- 4867 posts since 18 Dec, 2000
Can anyone with the beta see if we can now route midi per channel from a midi plugin to other tracks?
For example, with Nora you can route the midi to another track, in Nora you can set the different channel for different tracks. but Live will not allow you to filter out the different midi channels.
For example, with Nora you can route the midi to another track, in Nora you can set the different channel for different tracks. but Live will not allow you to filter out the different midi channels.
- KVRAF
- 3646 posts since 21 Nov, 2015
Which would actually be a pretty useful update, as Plugins like HY-RPE2 and such, can send out on different Midi - Channels. Maybe we can hope for a 11.xx to fix this in the Future. Or is this already available in the Beta now?
You can be creative in any right place on Earth, and not only in the wealthiest cities. Bring the world feelings from everywhere, and not only feelings of capitalistic or jail environment.
― Aleksey Vaneev
https://linuxdaw.org
― Aleksey Vaneev
https://linuxdaw.org
-
- KVRAF
- 2140 posts since 16 Jan, 2013 from USA
It does not show a channel selector for the output as far as I can tell. Looks just the same.dusted william wrote: Sat Nov 14, 2020 6:01 pm Can anyone with the beta see if we can now route midi per channel from a midi plugin to other tracks?
For example, with Nora you can route the midi to another track, in Nora you can set the different channel for different tracks. but Live will not allow you to filter out the different midi channels.
- Banned
- 11467 posts since 4 Jan, 2017 from Warsaw, Poland
You mean like take only MIDI Channel #1 on one track and MIDI Channel #3 on another, both coming from the same MIDI source? I tried with Hy-SeqCollection but as soon as I chose it as MIDI source on other tracks I couldn't pick MIDI channel anymore from the drop-down.dusted william wrote: Sat Nov 14, 2020 6:01 pm Can anyone with the beta see if we can now route midi per channel from a midi plugin to other tracks?
For example, with Nora you can route the midi to another track, in Nora you can set the different channel for different tracks. but Live will not allow you to filter out the different midi channels.
Unless I'm doing something wrong?
-
WatchTheGuitar WatchTheGuitar https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=440193
- KVRAF
- 13256 posts since 30 Apr, 2019
I don't have 11 Beta yet, but I know what you mean - have the same issue with Chord Potion.dusted william wrote: Sat Nov 14, 2020 6:01 pm Can anyone with the beta see if we can now route midi per channel from a midi plugin to other tracks?
For example, with Nora you can route the midi to another track, in Nora you can set the different channel for different tracks. but Live will not allow you to filter out the different midi channels.
I can stick a source for a track as ChordPotion/ChordPotion, but everything is routed to Channel 1 no matter what channel it was on originally.
There needs to be an option added like source ChordPotion/ChordPotion/<MIDI Channel Dropdown>
or they go the Bitwig route and include a MIDI filter plugin that enables you to filter out, for instance, all but channel 1 or all but channel 2 etc.
-
ReleaseCandidate ReleaseCandidate https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=476930
- KVRian
- 620 posts since 19 Oct, 2020
If you want the same MIDI input to be routed to different channels (e.g. of a multi-instrument Sampler like Kontakt, UVI Workstation, ...) you have to use one MIDI track per channel and route that to the MIDI channels. You need to record arm all tracks, if you want the same notes send to all channels simultanously.
- Banned
- 11467 posts since 4 Jan, 2017 from Warsaw, Poland
You do that in Inspctor Panel of each track.WatchTheGuitar wrote: Sat Nov 14, 2020 8:20 pmor they go the Bitwig route and include a MIDI filter plugin that enables you to filter out, for instance, all but channel 1 or all but channel 2 etc.
The Channel Filter "plugin" is only handy when you capture MIDI from somewhere else using Note Receiver device
-
WatchTheGuitar WatchTheGuitar https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=440193
- KVRAF
- 13256 posts since 30 Apr, 2019
Oh yeah true it’s just that I tend to use note receiver hand in hand with them so I can swap inputs easily e.g. to switch between different Chord Potion instances to get a different patternantic604 wrote: Sat Nov 14, 2020 8:52 pmYou do that in Inspctor Panel of each track.WatchTheGuitar wrote: Sat Nov 14, 2020 8:20 pmor they go the Bitwig route and include a MIDI filter plugin that enables you to filter out, for instance, all but channel 1 or all but channel 2 etc.
The Channel Filter "plugin" is only handy when you capture MIDI from somewhere else using Note Receiver device![]()
-
- KVRAF
- 4867 posts since 18 Dec, 2000
yeah, plugins like chord potion, nora, HY sequencers, ets... are not as powerful when using with Live. sigh...
I hope they add this to version 11
I hope they add this to version 11
-
- KVRian
- 906 posts since 25 Jan, 2014
Where is that save button in 11 ??

