Ableton Forum

Hi Timur,

your observation is correct. You're seeing two issues:

1. Multicore support adds a certain cpu load overhead per audio track input. You can get rid of it by setting "Audio From" to "No input" in all tracks or disable the audio inputs in the preferences. This is due to technical reasons ...

Sorry, I was out of office for some days.


I loaded a set into Live 5 and played it from the spot where it takes 40% of my CPU. Then, by switching all inactive (speaker off, all plugins off) tracks' inputs to AUTO from IN I was able to reduce the CPU load to about 30%

The same set in Live 6 at ...

FYI: Record delay compensation applies only to tracks that are directly connected to external input.

After some investigation I found that muting a speaker buttons may not always disable audio calculation in the following tracks. Could you try to add a utility device at the end of each track and automate its Mute button instead of the track's speaker button? It should be especially useful for ...

Maybe you have a hyperthreading single-core processor like Pentium 4?
Live does not use hyperthreading since it may result in bad audio performance. For multicore support you need a 'real' dual core processor like Pentium D or Core Duo.

Regards,
Andreas

Hi Phelios,

arming / disarming a track may cause clicks for technical reasons (it may involve changes in delay compensation which are currently not faded).

As a workaround you can disable Delay Compensation in the Options menu. This needs to be done for each document, so you might want to save it ...

Hi,

please check the plugin buffer size setting (it's located on the 'CPU' page in the preferences). Generally it should be set to "As audio buffer".

A VSTi plugin will cause a delay of that buffer size, for example if you're running Live at 44.1 kHz and have 8192 samples of plugin buffer size you ...

Such delays often result from feedback routings (for example if you would route a group track somehow back to one of the channels).
Maybe you created a feedback routing, possibly by accident?

Hi,

how do the cpu loads compare when you use a copy of your set, but without the Reason input tracks? Which kind of audio interface / driver do you use?

Regards,
Andreas

Hi,

some of Live's devices will consume a little cpu load even when bypassed, probably that's what you notice. Currently there is no way to completely disable a track so that it uses no cpu. It was always like that in all versions of Live.

Regards,
Andreas

Hi digitalex,

do you mean the monitor buttons disappear even though the track's "Audio From" chooser is set to anything but "None"? If so, can you tell me more exactly what you did? I cannot reproduce it.

Regards,
Andreas

Hi FloatingPoint,

some third-party plugins might not fully support multiple cores or even interfere with Live's usage of multiple cores. This may result in lower overall performance. It depends on the technical details of the plugin implementation. Please your plugin's documentation, maybe ...

When you have midi mappings for slots or knobs, Live will send midi to the controller to tell it about the slots' / knobs' state. This should generally not affect the audio performance, but I wanted to exclude a bug in this area.

Now I think it would be best if you sent me a bug reporting snapshot ...

I do however have settings in the audio tab in the channel Configuration, but if I change those I get no audio at all.

Generally it is a good idea to enable only the audio output channels you really need. We have been reported that the channels numbers the MOTU driver reports to Live may not ...

MODDER1 wrote:Yeah that's how mine was when I started... with all the midi output ports disabled, so this wont make a differenc for me.

Ok, and did you try deleting the midi mappings in your set? Did that change anything?