8.1.3???

[3dot...]

I really don't know what's caused that .. playing for the last 30 minutes seems stable...
(I've upped my buffer from 128 to 512.. plugin buffer at 256...cpu pretty steady now 30-40% ...it's a heavy set..)
I will now proceed to try and introduce 'clip-mapper1.0' into my live8.1.3b1 template..
wish me luck..

[ilia]

Hi Ilia, the plugin buffer problem that I mentioned earlier affects plugins from a specific manufacturer that I'm not going to name here. If you encounter frequent crashes, especially when running a loop in the Arrangement View, scrubbing through the Arrangement's playback position, hitting start/stop or changing presets in the plugin itself, contact us by email and I'll send you more information.

Apart from that, too small plugin buffers will usually only cause a higher CPU load, but may also lead to dropouts if the buffer is too small. I'd keep the plugin buffer at 64 samples minimum. Another important fact when setting the plugin buffer is that it must be divisible by the audio buffer (or vice versa), e.g. the plugin buffer should be EXACTLY a halve, a third, a quarter, etc. of the audio buffer, so that the buffers can render "in sync". Otherwise you can get dropouts (plugin buffer is smaller than the audio buffer) or you would waste CPU cycles (plugin buffer is higher than the audio buffer). The audio buffer itself should ideally be a power-of-two value, i.e. 64, 128, 256, 512, etc. samples.

Best,
Nico

Thanks for this info. The RME buffer on XP can be set to 48 and then powers of 2 from 64 through 1024. I usually always have the plugin buffer at 32, so only 48 for audio should be problematic... 48 is still usually usable under reasonable loads on my desktop ([email protected]) but less stable than the others (I attributed it simply to CPU being more heavily taxed) Unfortunately, Live won't allow a plugin buffer setting of 16 or 24, maybe that would improve performance for those of us wanting to squash latency on fast machines?

Crashes when going through a loop (as well as volume dropouts and sudden CPU spikes to 600%) are a very common annoyance here, yes (and in Live 7 as well). Would be great if this could be alleviated.

[SubFunk]

you should remove all plug ins and try to open it again .theese crash on launch szenarios are most of the time plug in related... for me all of the time......

i refuse that. simply because those plugs i use since years (since the bias master perfection suite exists) and are in every single of my damn projects! fuck this disco, superfreq 4 i just found out is the reason for not letting me use key or midi mapping in an older project, i use superfreq 4 since it's existence and since i use live v 5.2... the plugin's latest version is now AU 1.2.1.19801 and it is several years old (well a lot of changes occurred to the plug, right?) and it is used from me in several instances in every damn project in any host i use... now suddenly it is a problem for live to deal with... fuck that! i am not willing to be turned into an idiot, is use DAWs since years professionally and surely know what am i doing... well, i don't have a single clue about programming, i am not an IT person, i am a sound guy that wants to make music. i seriously reach the point of dropping ableton live and all my activities and promotion around it. i feel totally cheated.

i just wrote that to nico from support as well, he dealt very nicely with that problem and tried to help me, poor support team, that has to deal with baby shit like that. it is not their fault, i don't think so they try to help with problems that some others in the same company manage to 'construct' ???

well, whatever... instead of makin' music with ableton i will go for a walk to calm down, this chapter is now closed for a while... if they don't fix that immediately, i will withdraw in the ableton live user group berlin thread officially my activities! i have other things to do then spending my free time with headaches and anger.

cheers
axel

[drako]

Seems to run very smooth here, except for that nasty UI bug.

??? whats that?

With some vst's, mostly eq's, in my case Voxengo and Uad Cambridge, adjusted frequencies reset, when releasing mouse button.

[3phase]

you should remove all plug ins and try to open it again .theese crash on launch szenarios are most of the time plug in related... for me all of the time......

i refuse that. l

you shouldnt... the show must go on..ableton or not... i had it a few times that the gulty plug was one i just had for demo and forgotten about it...and never ever have used it anyway... but its best to remove them first all...

than see if t loads.. than just put in the ones used in the track.. most of the times one plug is causing the crash thats not even used in the file...


you know.. a good trouble shooting routine is to isolate the problem.. so you might end with a stable version with all your precious plugs.. or when you know which one it is you might see if there is an update of that plug.. or an older version...

[SubFunk]

well, to be honest, i have Logic for the studio, works a tread and maschine for live playing, the beta 1.5 already works a tread... so fuck it, i am out, at least for now, jeez, i love this program... i truly love it, there is a reason i did a lot of activities around it... and i complained, i wanted to see it being better but i feel like they really start to take the piss now. and i run out of energy, it's like running after a girl you love that is not responding to you at all, you know?

[3phase]

well, to be honest, i have Logic for the studio, works a tread and maschine for live playing, the beta 1.5 already works a tread... so fuck it, i am out, at least for now, jeez, i love this program... i truly love it, there is a reason i did a lot of activities around it... and i complained, i wanted to see it being better but i feel like they really start to take the piss now. and i run out of energy, it's like running after a girl you love that is not responding to you at all, you know?

ok..do the otello.kill her

[SubFunk]

well, to be honest, i have Logic for the studio, works a tread and maschine for live playing, the beta 1.5 already works a tread... so fuck it, i am out, at least for now, jeez, i love this program... i truly love it, there is a reason i did a lot of activities around it... and i complained, i wanted to see it being better but i feel like they really start to take the piss now. and i run out of energy, it's like running after a girl you love that is not responding to you at all, you know?

ok..do the otello.kill her

well you know that this saying actually comes from another member of the forum, that is usually quiet and calm...

so i am not the only one feeling this way, i even 'talked' to denis yesterday... they have no idea how bad the word on the street is, i am just the tip of the iceberg.

[3dot...]

... they have no idea how bad the word on the street is, i am just the tip of the iceberg.

YES !I've seen this ... even the crack addicts(my students) are hating on it !!!!

[3dot...]

automated responses from ableton support :

'[email protected]' :
"Thank you for your email.

I will be out of office until April 6th and not have access to emails during
this time.

Best,
xxxxxxx
Sound Team Project Manager"

'[email protected]' :
"Dear Ableton Customer,

Thanks for contacting our support team.

Due to the amount of interest in Max for Live and Live Intro, we're currently dealing with a lot of emails. This means it might take us a little longer than usual to get back to you.

But don't worry, your email hasn't been lost and we'll do everything we can to get back to you as soon as possible.

Meanwhile, you might find some answers in our FAQ section:
http://www.ableton.com/faq

We'll be in touch again soon. Please accept our apologies for this delay.

All the best,

The Ableton Technical Support team"



...WEAK(but polite)

[Bionecteur]

Due to the amount of interest in Max for Live and Live Intro, we're currently dealing with a lot of emails.

[SubFunk]

...WEAK (but polite)

yeah, like denis, i can't take him serious anymore... it's all friendly blurb, nothing more. we want results, hard facts.

it is simply going on for to, much to long... how long is live 8 out now? for gawds sake this is becoming a joke.

well, i am still in love ain't i? but i am seriously outa here now.

[Hermanus]

I'm gonna give 8.1.3RC a try

[Dennis DeSantis]

yeah, like denis, i can't take him serious anymore... it's all friendly blurb, nothing more. we want results, hard facts

The best we can offer is a version with improvements. We can't make crashes or bugs in previous versions disappear. The results and hard facts can only come by users telling us "yes, this is better" or "no, this is still a problem because of [x]." I'm not asking you to take me seriously. I'm only asking for your help in making Live work better.

but i am seriously outa here now.

Then I apologize, again, for the bad experiences you've had with Live and wish you the best with whatever you choose to do. But somehow, I suspect you'll reply again.

[auditory canvas]

I'm struggling to understand some of the complaints here.

We can't realistically expect new versions of Live, which are intended to sort out certain bugs, and problems, to work with every older 3rd party plugin anymore. In order to fix some bugs, changes need to be made, that may mean older 3rd party plugins no longer work. Why should it be the duty of Ableton to make sure every 3rd party plugin still works with the new versions? Why not a duty of the 3rd party plugin developers to make sure their plugins continue to work with new versions?

I mean that's a bit like expecting home entertainment system manufacturers to continue to include tape decks on their new products, just so I can still play my old tapes that I paid good money for 10 years ago.

Nobody is really forced to upgrade every time a new version, or point release comes out, if the old version works for you then why upgrade? And if you do upgrade and older plugins cease to work with the new system, why complain and call it a fault of Ableton?

Perhaps an good analogy might be Microsoft or Apple - they don't make sure every 3rd party application and driver works on their new releases, they expect the application developers to ensure that their software remains compaitible with new versions and point releases, and service packs, so why would it be any different for Ableton and 3rd party plugins? I think it's more the responsibility of the 3rd party plugin develops to ensure they support their customers and endeavor to ensure their products are up to date and able to work with the major DAWs and new versions of each.

I think it's a small miracle that Live actually runs as well as it does for the majority of users considering the near infinite combinations of computer specs, software, and plugin combinations. think that's quite impressive on Ableton's part to be honest.