I'm not totally sure whether Ableton loads all effects and instruments that are actively being used in your project or not when you launch the project. I know they're listed on the interface, but I also know there's a slight lag when you include certain things in a project before you can actually use it. That wouldn't be unusual as that's how most vendors do it in order to not waste resources on things that aren't being actively used, but it may be treated differently if you're using scenes. Because you only intermittently get the lag it suggests that there's a likely jam up with some underlying competition for resources occasionally. Whether that's from Ableton or from the OS is anyone's guess without some deeper performance analysis on the machine.kebabman wrote: ↑Tue May 17, 2022 8:17 amSurely though when I boot up my mac and boot up Ableton it does its thing and loads all wavs and any midi data? The only midi is a 303 plugin (ABL 3) on a couple of songs. Whenever you boot up the live set before a gig you accept its going to take 30 seconds loading wavs and any midi. Once Ableton has loaded all this when I open the live set it's there?DunedinDragon wrote: ↑Thu May 12, 2022 8:41 pmThis sounds far more like your processor is busy doing something and can't get around to launching the next scene for a moment. The question in my mind is what's in each of your scenes? It's entirely possible if you're using MIDI with some of the instruments it's trying to load the instrument plugin because they've been flushed out of memory after the laptop's been shut down and turned off.
I don't every use anything but WAV files in my scenes for exactly that reason. There's nothing to load because the WAV is preloaded with all the scenes and there's nothing they depend on to be loaded in order for the scene to start playing and it's very low cost in terms of memory or processing.
That's why I'm careful to use only a dedicated, very clean laptop with not much else on it for performance and only use simple WAVs to avoid such things.