Ableton Forum

Thanks for the suggestions.

I also found a post that describes how to install Live without the Push driver:
https://www.kvraudio.com/forum/viewtopi ... 2#p8680442

It might be useful to someone, until there's an official solution.

Same reason all unnecessary software bothers me. It uses additional computer resources and takes some time away from me, when I have to deal with it. Not the end of the world, just annoying. And I'm worried that a driver could cause some other issue on my system, like interfering with other hardware...

It's kinda rude that Ableton installs the driver for Push without even asking.

But if you insist on doing that, at least provide an uninstaller for it.

FWIW, since then I've been installing into Program Files without any problems. :) And if you're doing it for security reasons, you should change the security settings/properties of the Ableton folder, because by default the files inside have write permissions for all users. It's possible that this c...

I'd like to see an alternative view in the MIDI editor, like the Drum Editor/View found in some other DAWs. It makes programming "one shot" events such as typical drum hits easier, because the notes have no length and you can freely place them very close to each other without having to res...

Live 11.2 (beta) is out, still no changes.

This thread hopefully provides some more info.

OP's post is a bit hard to read, but yeah... it looks offline processing (rendering) of VST3 plugins in Live doesn't work as it should. An easy way to test this is with Voxengo TubeAmp , using the "auto" oversampling feature. With the VST2 version the "auto" setting kicks in when...

Meanwhile, I tested three other DAWs and none of them are doing any gating.
If Ableton thinks this is a good default, at least give us the option to completely turn it off, because that workaround is not great.
But I don't think it's a good default. It should be opt-in.

What I wrote above means that, even when using the options.txt workaround, any track content that starts below -100dB won't get played or rendered until it goes above -100dB. Like fade ins, for example. If you want that content to be played/rendered in Live, you first need to play through the whole ...

OK, I figured out why the options.txt setting wasn't working... For that gating bypass to work, audio must first reach a level above -100dB, but in my test setup it was below -100dB from the start (I had a saved Live session for testing). I should have assumed it works like this, due to the "ti...

Agreed, not much else to add. But I'll just add this again: that Options.txt setting does not work. And I do have the Options.txt file set up correctly, because I can successfully change some other settings with it, but -_AudioOffTimeInSamples=691200000 does nothing. In fact, any line that starts wi...

Ok, I just received an answer from the Ableton support : " This is known and expected behavior, there is a built-in gate function that cuts off the audio of plugins below -100dB to save processing power. In certain scenarios, this can have unwanted (not 😊)audible effects, e.g. when intentional...

Interesting.
Well, that Options.txt workaround doesn't work anymore. But this should just be fixed already.

I can reproduce this in both 11.0 and 11.1 using some white noise, Utility and SPAN:

With VST off:


With VST on:


The screenshots should be self-explanatory and easy to reproduce, but I can post the white noise file if needed.