Ableton Forum

After testing several scenarios, it was obvious, that the Qt runtime, which is Live build on, is very slow at first start/initialization/cache. So, the script does not much performancewise. This behavior led to wrong assumptions. Here is a quote from the Qt-developer forum: "Only the first appl...

https://www.youtube.com/watch?v=NXxbUmmiS9Q Latest Turbo Start script excludes VST directories from Defender virus scan. Should do the trick now, but you have to edit the paths. After the last test, Live was usable after 12 seconds. Read the description under the video for more information.

That's all very strange. Sometimes it scans fast (30s), sometimes it takes 10x the time (300s), without changing anything on plugins. In general, the 2 scan processes index+plugin scanner interfere to each other, which overloads my HD (SATA, mechanical) and the program becomes unresponsive. I can't ...

You could use a MIDI instruments/plugin which can handle key zones with different presets assigned. This way, the Emulator 2 sampler was triggered in the 80ies. Another way is to use the Launch tab in the MIDI editor to set the bank/preset per clip, which could theoretically control a multitimrale i...

Made in Live 11 Lite with Drum-Rack-as-a-sampler tricks. In the end, 5 tracks were used, incl. drum guide for sidechain trigger.
https://www.youtube.com/watch?v=qqzFLRmezbw

Made a Short video demonstration with 20 sec. turbo start. The script can be started now simply with a double click, even if you are not an Administrator. Just change the path to your Live executable in the code. Download link to the updated script and some notes are in the Short video description. ...

Same problem here with Windows version 11.2.11. I found out that 2 scanning processes (2 x 25% CPU 2/4 cores+100% HD usage) interfere with each other and get higher priority over the main program: "Ableton Index" and "Ableton Plugin Scanner". The Indexer can be killed using the T...

The automation value range is 0-1.0 with 100 subdivisions, that's right. Normally, instruments use a range of 0-127 for MIDI controllers. However, I would not assume here that Live does not output any interpolation that is calculated between the “visible” values. That's just a guess on my part.

Thanks this works. You need to switch monitoring on the receiving track to "In" or arm the track too to hear it. Solved

Can anyone explain how to connect a VST MIDI output plugin like an arpeggiator to a VST instrument. I didn't find any routing possibility. The MIDI output shows activity, so it works. The arpeggiator I use is always substituted with another instrument plugin on the same track. I suspect that you can...

Had "unknown" crashes with version 12.2.10 Windows on startup too. A second try then worked. New version 12.2.11 seems to run without the issue.

Drum-Rack-as-a-sampler is the right use case. As I use the Lite version, I extend my track limit a little. But as I mentioned, when hopping around with the play head the (longer) samples are not triggered on point. They run differently to each other. In Renoise for instance is a feature, called &quo...

Same issue here with version 11.2.10. MIDI is received, but no connection to an instrument track. The solution was to switch off-on the MIDI driver output in preferences. It seems to fail a correct MIDI driver initialization at startup. However, latest version 11.2.11 seems to work fine.

Is there a way to synchronize longer samples in the Drum Rack with the timeline, while scrubbing? A sample is always triggered from start, no matter where the play head sits, but should be started right on play head position like on audio tracks.

Very good tutorials, especially the tutorial with Ski Oakenfull. (Music Radar/Point Blank Music School)