Ableton Forum

how disable delay copensation?

instead of worrying about being the first host to work with the new powerbooks ableton should have fixed this major bug.its been going on since they released ver.5.if they spent the same amount of time working on the audio glitch problem as they did with rewriting live to work with mac intel im sure it would be fixed.

Dj-Grobe wrote:how disable delay copensation?

It's in the 'Options' menu, item #5.

john gordon wrote:instead of worrying about being the first host to work with the new powerbooks ableton should have fixed this major bug.its been going on since they released ver.5.if they spent the same amount of time working on the audio glitch problem as they did with rewriting live to work with mac intel im sure it would be fixed.

and the dumb thing is the problem will probably still be there on the new power books!!!

having a faster processor / more memory does not hide bad programming.
c'mon the ideas behind live 5 are great, but the implementation leaves much to be desired...

dpel wrote:

martin808 wrote:I don't mean to sound patronising here but are your power properties definetly set to "always on" and is hyper threading turned off. Just tell me to STFU if thats the first thing you did!!

what do you get in the live performance test? I get 38% with a 3.2ghz P4m and 1024mb ram

no worries martin808. i'm definetly set to "always on" i looked for hyper threading in bios. nothing there. then i read on a pc forum (i googled "how do i turn off hyperthreadin on a HP R4000) and i read a post from someone saying hyperthreading is only on Intel chips (not AMD, they have their own version and is apparently not accessable)

BUT...

i just turned off all of my networking (LAN and Wireless) services. so far sso good. i'll report back...

thanx martin808
thanx everybody.

After turning off LAN and Wireless, most services and startup items,
I still have the odd spike/glitch and paralized arrange grid.

...oh well!

justin wrote:

john gordon wrote:instead of worrying about being the first host to work with the new powerbooks ableton should have fixed this major bug.its been going on since they released ver.5.if they spent the same amount of time working on the audio glitch problem as they did with rewriting live to work with mac intel im sure it would be fixed.

and the dumb thing is the problem will probably still be there on the new power books!!!

having a faster processor / more memory does not hide bad programming.
c'mon the ideas behind live 5 are great, but the implementation leaves much to be desired...

i just want to be able to play live without audio glitches.i would pay 50 bucks if i were guaranteed this one thing.

http://synthmaker.com/wiki/index.php/Us ... _for_Audio
A few optimization links I've collected.

john gordon wrote:instead of worrying about being the first host to work with the new powerbooks ableton should have fixed this major bug.its been going on since they released ver.5.if they spent the same amount of time working on the audio glitch problem as they did with rewriting live to work with mac intel im sure it would be fixed.

and how do you know how much time they spent porting the universal binary?

AdamJay wrote:

john gordon wrote:instead of worrying about being the first host to work with the new powerbooks ableton should have fixed this major bug.its been going on since they released ver.5.if they spent the same amount of time working on the audio glitch problem as they did with rewriting live to work with mac intel im sure it would be fixed.

and how do you know how much time they spent porting the universal binary?

well for that 49.00 upgrade i hope they spent a good time on it and i hope for the people that are planning on buying the new powerbook that its super stable.

I've been with Live since version 2. I'm running 5.2 on a iMac 2.0ghz duo core. I'm not a DJ. I depend on Live for recording audio as well as soft synths and Impulse. I'm getting glitches and stuttering that is not indicated on the CPU meter. It is not all of the time but enough to piss me off. I'm using a Rosetta 200 w/ an x-FireWire card w/ that makes the 200 my only interface. Nothing running in the background except for the Apogee FireMix software for low latency. The buffer is set at 1024 samples and I'm still having glitches with only one midi track w/ Impulse and 8 audio tracks. I can't depend on this. I've been very patient with the betas. This is fast becoming nothing but an expensive fucking drum/soft synth module that I can Rewire into another DAW that actually works like it is supposed to. I can't depend on this for basic audio so I guess I'll have to shell out the bucks for Logic or DP. I've got plenty of horsepower as far as CPU. I need to bump up the RAM a bit (512) but I should be able to get better performance than what I am getting. I've just about had it.

Before I start griping, I AM finding 5.2 a bit better than 5.0.3.

I just have this awful sinking feeling that there won't be a substantial and permanent improvement in the audio engine until the (paid-for) update to v6. Just wait and see!

The crazy thing is that old buggy Logic 5.5.1 (from 2001, I think?) on the PC STILL is more reliable with handling multiple audio tracks and VSTs than Live from 2006!!

....same frigin thing here.
- Ableton version 5
- m-audio firewire audiofile
- 1GB RAM
- 2.8GHz
- XP fully twaeked for audio
- harddisk 80%^ empty and defragmented
- One, yes I even tried ONE clip at a time.

I tried caching it all to RAM , etc. increasing latency, etc...Nothing works, I get glitching at least once during every track. It has nothing to do with CPU load or harddisk overload. I can run 72+ stereo tracks simultaneously when I'm writing in Cubase, but not one in Ableton. I found out the hard way Thursday night. I was playing 3.5 hours. It was so bad I had to stop and play records after less than 20 minutes, which I wasn't really prepared for as I only bought about 20 records just in case. The stupid thing is I've been DJing with it many times, but it has been a few months and I realize during this time I upgraded to version 5! I don't know what the problem is but this sucks bad, I paid a lot of money.

No glitches or overages here whatsoever with Ableton. Ver 5's working like a tank so far. We've had up to 40 stereo tracks audio 24/44 plus 10 mono = 50 total plus 6+ VSTi's and numerous plugs on multiple channels from different companies and I've never seen the meter over 60-65% power usage.

Running-

AMD Athlon 64 4000 + Claw Hammer 2Ghz FSB
4 GB OCZ Platinum 184-Pin DDR 400 Cas Latency 2-3-2-5
2 x Western Digital Raptor 150GB 10,000 RPM Serial ATA150 Hard Drives
Soundcard - RME HAMMERFALL

If you can't afford much, at least try to save up for a decent sound card like an RME. M-Audio sucks absolute shit in any capacity PERIOD - midi latency/sound quality etc etc etc and may make Ableton run shittier than usual as it makes every other DAW on Earth run like shit aswell. No argument needed. M-audio is a joke, if you cant afford something like an RME or the like now, save up. Don't waste your pay check in haste on an M-audio pile of crap when you could wait just a little longer and get something thats twice as much $ but 10 x times more powerful.



2 p

AdamJay wrote:

john gordon wrote:instead of worrying about being the first host to work with the new powerbooks ableton should have fixed this major bug.its been going on since they released ver.5.if they spent the same amount of time working on the audio glitch problem as they did with rewriting live to work with mac intel im sure it would be fixed.

and how do you know how much time they spent porting the universal binary?

to the first poster: obviously it hasnt been easy to figure out the solutions to these problems (audio, arrange) because they're so deep in the code its not really a question of how many people they devote to it.

i say this because theyve been going on for so long now, and they are so core to the usability and reputation of the program (ie sales) that if they could have fixed them over the past 8 months or so since release they definitely would have

its putting the right people (might only be a small team) on it all the time, to determine what they need to totally re-code for version 6 at this point.

5 is a lost cause. its too late and too much to redo for the sake of a version that is on its way out in 4 months from now

im sure nobody in here wants to hear or accept that likelyhood but the simple fact of the matter is its probably too late. imo upgrade everything you have now to get ready for 6

maybe the overkill in horsepower will make it a little better. or maybe it wont, but at least you'll have a better studio and will be ready for version 6 early

to adam: youve been around for a long time and - even if your happy with the way the program has been working for you - im sure yours is not the only rig youve ever seen or heard it used on

so im sure you have seen people working with it on a lot of different setups and if so there's no way you can believe that this is an "ok" state of affairs - specifically in reference to the audio performance and the arrange view lockups

what i dont understand is the small group of people that are constantly apologists for the guys in the company .. yes they're cool guys .. however

... what does that have to do with the bug reports forum - and what good does it do for a product that is in such a sorry state of affairs visa vis these issues, that its core funtions are almost unusuable for a way too many people?

looks like we're going to have to wait a full year to get something that is fully functional. but some of you are still defending whats going on here like they are members of your personal family. I dont get it

.

Jackal and Hyde wrote:No glitches or overages here whatsoever with Ableton. Ver 5's working like a tank so far. We've had up to 40 stereo tracks audio 24/44 plus 10 mono = 50 total plus 6+ VSTi's and numerous plugs on multiple channels from different companies and I've never seen the meter over 60-65% power usage.

Running-

AMD Athlon 64 4000 + Claw Hammer 2Ghz FSB
4 GB OCZ Platinum 184-Pin DDR 400 Cas Latency 2-3-2-5
2 x Western Digital Raptor 150GB 10,000 RPM Serial ATA150 Hard Drives
Soundcard - RME HAMMERFALL

i think its hard to overlook the mad fast AMD chip and the 4 gigs of ram you have going on there

ie .. as ive said in other threads lately .. the only people that are happy with the performance of 5 are people running it on the fastest gear possible with double or triple the amount of RAM you should be expected to have.

the RME might be helping but its only helping, it cant be the blanket solution. i say this because i was arranging a track on a dual G5 with 4 gigs of RAM and a Hammerfall just last nite

... similar number of audio tracks (30 - 40) and possible one realtime VST, numerous ableton and VST fx ...

and the audio started hitching during big buildups with lots of simultaneous audio tracks and humongous full frequency spectrum, its started to drop out and stutter.

he was totally mystified, thought something was going wrong with his shit, he runs the same amount of audio and in addition plenty of realtime CPU intensive VSTs on the same exact rig with the Hammerfall under Logic 7 and theres no problem at all.

i think if you were running an average to mid level system with the same card you might be in here with a totally different kind of post



love your stuff btw, rock on

.