Ableton Forum

When does the RC2 expire ?

pr0jekt2501 wrote:When does the RC2 expire ?

15th of May.

I'm running 8.1.3b1 and I've been experiencing random clicks on random channels when hit Spacebar (Start/Stop). If there's a reverb on the channel, it feedsback like crazy upto 26dB and in a fit I search for the volume knob. Downloading 8.1.3b2. I've changed the buffer size, no luck. Seriously, no idea as to what is causing it. Anyone else with the same problem? I can't even open this current track on a previous version to check.

Running 10.6.3 Mac OS X on a 2009 Mac Pro.

The clicks come in only when I stop a track and feedsback if there is a reverb plugin or a reverb returns send. Oh and the 8.1.3b1 still crashes like crazy. I hit 'Save' almost every minute or after every change I make.

Also, I just checked. I can't reproduce the problem on a new session. So it's just this track, which has a lot of 3rd party plugins, so no idea as to what could be causing it. Any solutions? Any way of re-opening the track with settings to default or something?

meant to post this 2 Live versions ago:
no biggie, but if you close the prefs during manual vst rescan Live vanishes (on XP)

do i need to understand this?

i openend live again today, to give it another shot... now, one of my older projects which i am about to 'rebuilt' into a live song, worked perfectly well, no crashes, no glitches, no audio problems, only thing is that still the temp and fans go crazy when live is open.

i mean i am happy about that, but it is like live behaves like a girl having her period or not, i really don't understand that.

the same project a day before would still cause audio crackles and little drops while moving things (anything, plugs, tracks, etc.) while the sequencer is running?

again, i have not changed anything on the system since, the OS update from 10.6.3 to 10.6.3.v1.1 i did prior to that.

so, i basically have the same odd issues of randomness, which are so hard to pinpoint what the cause is or could be.

SubFunk wrote:so, i basically have the same odd issues of randomness, which are so hard to pinpoint what the cause is or could be.

my $0.002 thought is that *usually*

randomness == intermittent == like a loose wire == hardware/physical

reproducible == conditionally based behavior == logic error == software,
UNLESS there are potential software on software interactions (ie resource contention) which need to be checked for by eliminating other simultaneously running applications, at which point it becomes reproducible because "when I run software x and software y together, this happens".

Why do I have to increase my sample output by 1500 sample difference from 8.1.1 to the new beta. I had not played with komplete 6 in a week or so and thought I'd run her thru to see what the beta thought and I have to increase by such a large amount that in makes a big difference for me for latency issues in live performance.

Went back to 8.1.1 to try the same three plugin (absynth 5, FM8 and Massive )in the same way and it seems that the new beta uses alot more CPU and you have to increase the sample output.

No good in terms of live performance vst's

mikemc wrote:

SubFunk wrote:so, i basically have the same odd issues of randomness, which are so hard to pinpoint what the cause is or could be.

my $0.002 thought is that *usually*

randomness == intermittent == like a loose wire == hardware/physical

reproducible == conditionally based behavior == logic error == software,
UNLESS there are potential software on software interactions (ie resource contention) which need to be checked for by eliminating other simultaneously running applications, at which point it becomes reproducible because "when I run software x and software y together, this happens".

well that exactly puzzles me.

it should be 'dependent' if at all on interaction, but it is, as in my case always the exact same situation, one day good, one day bad... no different interaction, or plugs or whatever going on... exactly the point i don't understand.

well, i have to say that some of my biggest issues seem to be finally gone, like moving parts in the arrange without causing an immediate crash.

mikemc wrote:my $0.002 thought is that *usually*

randomness == intermittent == like a loose wire == hardware/physical

reproducible == conditionally based behavior == logic error == software,
UNLESS there are potential software on software interactions (ie resource contention) which need to be checked for by eliminating other simultaneously running applications, at which point it becomes reproducible because "when I run software x and software y together, this happens".

Hmmm... Plenty of ways for a single application to have pure software bugs causing seemingly random problems: pointers writing to uncontrolled address space, memory leaks, which depending on a whole pile of other seemingly unrelated OS stuff may or may not have catastophic consequences on stability.

SubFunk wrote:do i need to understand this?

i openend live again today, to give it another shot... now, one of my older projects which i am about to 'rebuilt' into a live song, worked perfectly well,

Thats my impression regarding L8.13 aswell.. sometimes the performance is going extremly out of line..another day its ok again...

that probably dont makes it easier to find the source of this.. But there is something strange that should be nailed down...
just how???

SubFunk wrote:

mikemc wrote:

SubFunk wrote:so, i basically have the same odd issues of randomness, which are so hard to pinpoint what the cause is or could be.

my $0.002 thought is that *usually*

randomness == intermittent == like a loose wire == hardware/physical

reproducible == conditionally based behavior == logic error == software,
UNLESS there are potential software on software interactions (ie resource contention) which need to be checked for by eliminating other simultaneously running applications, at which point it becomes reproducible because "when I run software x and software y together, this happens".

well that exactly puzzles me.

it should be 'dependent' if at all on interaction, but it is, as in my case always the exact same situation, one day good, one day bad... no different interaction, or plugs or whatever going on... exactly the point i don't understand.

well, i have to say that some of my biggest issues seem to be finally gone, like moving parts in the arrange without causing an immediate crash.

reproducible ...not quite obvious in complex systems...especially ones which rely heavily on timing and resources..
all the more important to have a solid base on which to build..
and something in Live's architecture is apparantly f'd up a bit..
(v7 would be my guess.. that's when I started having issues)

3phase wrote:

SubFunk wrote:do i need to understand this?

i openend live again today, to give it another shot... now, one of my older projects which i am about to 'rebuilt' into a live song, worked perfectly well,

Thats my impression regarding L8.13 aswell.. sometimes the performance is going extremly out of line..another day its ok again...

that probably dont makes it easier to find the source of this.. But there is something strange that should be nailed down...
just how???

"Report a bug" from the help menu creates a pack immediately. If something strange happens but it isn't a crash, you can make a snapshot. Ableton can check the logs to see if they can find whatever caused your problem.

Those random bugs are the nastiest. The hardest to nail, but what a joy when they're gone.
Looking forward to the next RC. This one clicks a little. At least they aren't 42dB pops anymore

hoffman2k wrote:

3phase wrote:

SubFunk wrote:do i need to understand this?

i openend live again today, to give it another shot... now, one of my older projects which i am about to 'rebuilt' into a live song, worked perfectly well,

Thats my impression regarding L8.13 aswell.. sometimes the performance is going extremly out of line..another day its ok again...

that probably dont makes it easier to find the source of this.. But there is something strange that should be nailed down...
just how???

"Report a bug" from the help menu creates a pack immediately. If something strange happens but it isn't a crash, you can make a snapshot. Ableton can check the logs to see if they can find whatever caused your problem.

Those random bugs are the nastiest. The hardest to nail, but what a joy when they're gone.
Looking forward to the next RC. This one clicks a little. At least they aren't 42dB pops anymore

how do you exactly create a 'snapshot' cause i am not sure if i send the right stuff in... and did anyone got any kind of response?

if i send something to support i am used to a response, at least to know they have acknowledged it, but if i send stuff to bugs@... nothing ever happens, at least it feels like that.

i am so sick and tired of being a beta tester since a year without being 'appointed' as such, that this is seriously my last call, if they don't get this release halfway sorted i am off. for sure.

p.s. @ HD for sure!

it's in a dropdown menu around the top middle of the GUI, 'Take Bug Reporting Snapshot.' if you open the pane on the right side of Live where File Manglement lives there are instructions on what to send into Ableton. these are only in place for beta and RC releases.

Tone Deft wrote:it's in a dropdown menu around the top middle of the GUI, 'Take Bug Reporting Snapshot.' if you open the pane on the right side of Live where File Manglement lives there are instructions on what to send into Ableton. these are only in place for beta and RC releases.

he? what? where?

i am either totally blind or i don't have it, i searched in all my drop down menu possibilities...?

where the heck is that? can someone post a screenshot for a blind man, please.

another major annoyance, why can't they make it as easy as other software manufacturers? (and those even reward you for doing it!!!!!!)

maybe they should slowly but surely realise that they deal with musicians and sound engineers / producers not IT nerds!!!

all i want to do with this program is making music. not science.