didn’t have this problem. it rescanned plug ins but had no issues finding anything. i loaded a blank template first and let it rescan w/that before loading a project/work in progress.
Yes, it’s very annoying. Since 12.1b11 this is happening, 12.1b12 should fix that but that’s not the case. I see in the settings>plugins that scanning them is during about 15 minutes before I can use Live 12. And this is happening every time I start Live 12
I already submitted a bug report. Hope you did the same.
1 Like
Yep, I sent one on. A lot of people are dealing with this. I always load a blank template and I let it scan. Then I load my project and it can’t find any of the plugins. Just maddening.
I’m going to slim down the plugin list to just vst3, no Audio Units or vst anymore. It’s the worst thing ever to have to go in and reload 50+ plugins and completely retweak them all and try to remember wtf my settings were.
1 Like
These do require integration with Uni enrollment, you might get a one-off if its a magnet school and can swing it, but “i have a kid in school!” probably won’t 
1 Like
I’m on Windows 11, and only use VST3. I have around 35 plugins in total. Hope Ableton will fix it in 12.1b13. It’s annoying but I can not complain, that’s the risk of using a beta version.
1 Like
Curious if anyone can venture a guess as to why we don’t have warp markers for MIDI clips like we do for audio clips?
I would love to be able to go through MIDI files that were played in free time and define bars and beats without altering the original timing. And like with audio clips, be able to assign those warped/tempo mapped clips as the ‘tempo leader’ in the arrangement view.
I know about the MIDI note stretch capability in Live, but I can’t seem to tempo map a clip this way without totally mangling the original timing. For that kind of application it’s a very crude tool. And there’s no way to undo that kind of stretching/warping the way you can for audio clips by just deleting warp markers.
3 Likes
because midi warps around ticks, the mechanism altering it even in repeated fashion is sometime called swing. And warping it in general is as easy as taking out 0xf8 bytes or placing some extra on a serial stream of pieks which express midi bytes. Internally ‘midievents’ are indeed a bit more complex yet as of midi standard the ticks are generated directly proportional to audio buffer sample rate, disconnecting this relationship would mean to get rid of the reference events are based on. So if you really want to warp midi, you would simply decrease tempo or increase tempo. Simple as that…
by the way Max for Live has mechanisms for just that, even changing the dependent clock and therefor its tick on the fly, even running multiple clocks. The MaxMSP C API offers a scheduler, concept with which you call functions and even allow to code entirely independent event cycles. Warping on steroids. The main difficulty is here that machinery expecting a steady tick clock to rely on and midi bytes to be on the same serial stream can become a challenge. But you can simply use a metro object (or others) and change its speed and this way slowing down or speeding up an artificial tick cycle internally used to parse events accordingly, which is what warp in some way also does…
7 Likes
Thanks for the response! I’ve posed this question in several places and this is the first substantive answer I’ve gotten. Thank you.
I wish I understood more of what you wrote, but I will keep re-reading it and hopefully more will make sense 
I will just add that I’ve discovered that warping MIDI in this way is possible in Cubase. There, you select a moment in the timeline and drag it to the corresponding event in the MIDI file. This creates a new tempo event in the timeline. However, after the clip is warped, the tempo map can then be deleted or altered, but events stay locked to the ‘warped’ bar/beat positions. I think this is a great implementation.
2 Likes
if you are familiar with some of the major programming languages of the past 20 years… (java/c++/C/javascript) you are ready to go with Max because it offers access to all of them even mixed up accessing each others implemented capabilities based on the same principles which is what actually MAX is.
The main problem is usually getting used to read the documentation, which is a bit lengthy, true. And MaxMsp is not the same as Max for Live in detail, but on the surface it is. Some MaxMsp objects are specifically adapted to work in the Live environment, in example the transport object (which does keep track of tempo and ticks or time measures). But nothing to be bothered too much. Just start digging… its fun.
also a nice starting point for research regarding max for live 11 capabilities…
here Live 11 and Max for Live: A Glimpse of Whatâs Possible | Ableton
3 Likes
I don’t think the technical details (although interesting) have anything to do with why this isn’t an option in Live, I think technically it would be quite easy to warp MIDI (easier than audio for sure) but for whatever reason they’ve not built it as a feature. It’s possible that there’s just not been much demand for it, as it’s so easy to move the notes around by hand instead. One of the new MIDI Tools in 12 lets you draw a speed up/slow down curve for your MIDI which I guess is in the same space but not as integrated in the UI as warping.
3 Likes
Have you thought about rendering your MIDI to Audio and then applying the tempo map to that instead? Shouldn’t that in turn pull everything on the MIDI Timeline towards the tempo map warping that’s occurring? I’d think you should then be able to mute the audio that you rendered, after you are done with the mapping, and carry on working with the MIDI.
Honestly, I don’t know if that will work, but it’s something I would try.
1 Like
That’s a great idea!! Will have to try it out later. Thank you!
1 Like
For any Live users who have a UAD audio interface that utilizes the UAD Console, there’s a new Elizabeth Homeland plugin that you should check out. It offers direct control of the Console from within Ableton without having to invoke the Console app. It looks very slick.
5 Likes
This is genius. Really impressive.
I’m not really familiar with Cubase these days, but as you’re described it this sounds like something Live’s groove tools can do pretty easily as opposed to warp markers in midi.
Probably closer is the clip functionality where you can select a bunch of notes and a use the handle that pops up to resize them. Not exactly the same thing as it only affects the notes you selected and not those that come before/after, but it’s very much in the same territory.
Edit - actually if you select time rather than notes the way it works is very close to warp markers but not 100% identical, it does move other notes in the clip but it doesn’t warp them against a specified start/end point, just moves them forward or backwards without affecting their length/relative timing. Before the (killer) note dividing functionality was added in 12 this used to be the easiest way of putting together more complex tuplets in clips.
1 Like
Now we must turn our attention to “Move”…
5 Likes
2 Likes
what’s that? there’s no info there except coming soon
If this turns into even 1% of the Tonverk thread…
Anyway, looking forward to Ableton’s first wearable.
2 Likes
I’m going to guess (aka wish for) an OP-1-sized Push.
1 Like