Ableton Forum

In large projects these functions are PAINFULLY slow. It is sometimes faster to record to resampling in realtime...
doesn't make sense, waste of CPU - all daws have moved beyond this

+1

+1

Makes much time for cigarettes and Pepsi max breaks.

any max4live wizard?

+1
Yeah, this is pretty painful in my larger projects towards the end of the album I'm working on. For me, it's currently faster 9/10 times to re-record or resample thing than it is to bounce or freeze.

There was a few posts that popped up in the beta test forum regarding hyperthreading and the use of multiple cores/cpus to do certain tasks.

A few things were said but we were basically told:

'Hyperthreading is not supported - only 'real' CPU's are used for several reasons....'

'HT just isn't the best thing for real time audio. Also, you might experience performance issues with VST's and/or low latencies...'

'Clearing up this thread: Live does support hyper threading if it 'happens' / is activated for several cores. If you only have one core, HT is not supported because the order of the process threads is calculated parallel and therefore it could happen that e.g. the GUI thread is prior the audio thread - this would lead to undesired results...
Also, as a reminder: Live's CPU measurement does and can only show the audio threads. (see the manual pages for details) And: Track process calculations are distributed per Core.
I hope this helps.'

Nothing was ever said in reply to the questions regarding non real time audio use of multiple cores/cpus though - which is what this post is about, and mirrors some of the questions I brought up in the beta. When not performing real time audio tasks, these cores/cpus SHOULD be utilized to their fullest potential to give a smooth and slicker feel to some of Live's most mundane tasks such as rendering/freezing/etc..

Here's the topic on the beta forum - http://beta.ableton.com/abl01/topics/do ... rthreading
It seems you must be registered to read it though.

manasseh wrote:In large projects these functions are PAINFULLY slow. It is sometimes faster to record to resampling in realtime...
doesn't make sense, waste of CPU - all daws have moved beyond this

I always found that audio BTD more reliable than exporting/freezing.

btd?

cotdagoo wrote: When not performing real time audio tasks, these cores/cpus SHOULD be utilized to their fullest potential to give a smooth and slicker feel to some of Live's most mundane tasks such as rendering/freezing/etc..

Definitely. Another one of these issues that seems odd that it hasn't been addressed. Freezing/bouncing/rendering is incredibly slow next to any other program on the market today, VERY frustrating when you are trying to get work done...

miekwave wrote:

manasseh wrote:In large projects these functions are PAINFULLY slow. It is sometimes faster to record to resampling in realtime...
doesn't make sense, waste of CPU - all daws have moved beyond this

I always found that audio BTD more reliable than exporting/freezing.

Then let's make it faster and more reliable to export/freeze.

BTD = Bounce To Digital?

Disk.


BTW Logic introduced multicore rendering in a point update I believe, so it's not umpossible to do.