Live 8.0.9 still crashing....

[3phase]

so you cant solve the issues..
bad company.. bad bad company...

so ricardo started to tell bad things about life..and now this 3phase guy..and who is next?
But as long the student rollers are happy with theire brandnew 4track replacement everything is fine.
may the electric guitar prevail.. actually i should touch my again..this software is a huge inspiration in this direction.. a 606 over a mesa boogie bass amp.. my guitar on a marshel stack with out power soak.. and an lxp 5 for the one octave lower reverb to projekt the sound.. hmm ..pure audiophil fun.

and the only thing crashing are the neigbors eardrums... great

[davepermen]

you can't solve your attitude. bad 3phase, bad 3phase.

i'm on the while reading your other bug reports in the beta section. maybe you should start to post in german, as you might be more clearly stating what you're doing. sometimes they are really hard to read.

well, no one except ableton to deliver a perfect product as mostly no product on this world is perfect. but they normally try hard to fix issues. but calling the doctor stating "it hurts me" and then calling the doctor a bad one because he didn't made your hurt go away is fun

[Dandy Dust]

downloaded live 8.0.9 - it is crashing for me! pitty! any news?

[3phase]

your humor is very strange, as your performances (just from what i see on myspace)

what do you see on myspace? tresor 1992..its called techno and it was life at least as life as techno gets.. even was writing 303 lines on stage... not just playing some back

But maybe thats the problem... the modern ableton user dont wants much from the software.. and he dont cares about crashes much because the recovery works and no harm done...

and probably is the crash risk on stage not as high when you dont try to record clips while beeing on stage or insert fx in the track while everything is running...

ableton states this:


you had a bug.

others have bugs.

not true.. they only state that i have a bug... but how can i have a bug..i am no coder for ableton live

And as the polls show i am not teh only one with a bug... i really dont care if this are one bug or multiple bugs because either case they are not my bugs.. And its pure ignorance and very arrogant from a software company to see bugs as individual user problems rather than a structural management problem. If ableton wouldnt e so popular they shurely couldnt afford that attitude.

your bugreport was not detailed enough, and no other reported bug from all the other bugs was even remotely similar to your bug until a second one about a similar issue popped in. they solved it, and done.

Again..seeing the nature of the bug and taking ableton statements about it as truth this is a big bad joke in itself and should ring the alarmbells of some ceo´s...

And.. it is not solved... it has shifted.. its like cancer therapy.. the cancer is minimizing but spreading to other parts of the body now...

A fix is no crashes.. because of the again exclusiv nature of "my" bug its likely that the fix of the previous bug is the cause of the actual crashing..

lets call it the crash bug... maybe it has different permutations.. but the anoying bug is the crash bug..

all others are daylie biz and normal..
but the crashbug? you dont really want to be the company with the crash bug..

if i look at those two sides, it's obvious that your position is wrong. because ableton has a statistic about bugs, which you don't have.

yeah.. a statistics about shtty plug xyz bugs.but the mean big bad crash bug? they stand naked before it and had only 2 user reports... needed 4 month and it escaped thru the sink up the ass and eats the brain now from inside...
a horrible beast.. statistics dont seems to help there..

brushing it under the carpet dont helps either..


and regarding the doctor..again and again and again..

ITS NOT MY BUG

ITS AN ABLETON BUG

Live 7 Works.. Live 8 not... conclusion?


I never called a doctor.. i informed somebody that there is something glowing and smoking funny in the cellar.

it smokes more and more but they say.. hey first you tell us its smoking and now you tell us its even more smoking,.thats funny...

[dom]

so you cant solve the issues..

True, we can't solve your personal issues and general grumpiness towards your life or Live - it's just not our job.

We can, however, fix technical issues with our product Ableton Live, if they are reported correctly and at least somehow reproducible.

so ricardo started to tell bad things about life..and now this 3phase guy..and who is next?

Don't know, who actually cares?
Ricardo Villalobos and 3Phase are by no means the only persons on earth caught claiming plain wrong technical statements in public without even blushing.
Suprise: Earth is still turning, music still exists, so what?

may the electric guitar prevail.. actually i should touch my again..this software is a huge inspiration in this direction.. a 606 over a mesa boogie bass amp.. my guitar on a marshel stack with out power soak.. and an lxp 5 for the one octave lower reverb to projekt the sound.. hmm ..pure audiophil fun.

and the only thing crashing are the neigbors eardrums... great

If this is how you roll, our product is not the best match for you - by definition! Sorry.


Cheers,
Dom

[Dandy Dust]

I restarted the old version. Then started another .als to start off with and now it

SEEMS TO WORK nicely, the Live 8 Library is being aktulaized...

Dandy

[davepermen]

sorry, i forgot to write it out.


you have FOUND a bug

others have FOUND a bug

then you asked everyone "do you have found bugs" and quite some replied "yes"

so you, then, concluded, that the bug YOU found was a major issue that occured often.

and that, sir, makes no sense.




about your myspace, well, this is funny (but veeery strange, i'd never do such stuff)

By 1984 this had developed to some kind of sound terrorism with acoustic attempts and timebombs. Things like percussion performances in stairhouses of high populated buildings and time"bomb" hapenings with tapeloop based objekts "to be destroyed" in order to stop them. The high score was 12 police cars within ten minutes and a closed down floor on a huge shopping center.

it was the year of my birth btw


other than that, no, i want my software to be 100% reliable. still, i obviously have fallback solutions as needed, as nothing is 100%, ever.

so for live never disappointed, so didn't xp, vista, any beta (yes, i gig with betas!!), any version of traktor, and all in funky combinations sometimes. still i'm perfectly aware that one day, i will have a problem while live on stage. just as with vinyl, just as with cdjs (david guetta lately was great, blaming the cdj while it was the cd itself).


you just don't think very rational about conclusions. you take that stuff very personal, always thinking if it's your problem, the whole world has to now look at you and fix it by .. reading it in your eyes. as sometimes, you can't explain it at all.


but i had so much fun, i'm considering meeting you when i'm near berlin one day (if you would like to, too). i would especially love to have a day off at your studio, seeing all the mess live gives you from what i can read, you have tons of problems with it. which is strange, having on my own zero. so it's something that makes me curious. all points towards "it's you, that's the problem", but then again, obviously not (serious!).

but you can get better with your bug reports. i understand that you are pissed off by the product, i would be as well in your case.


just a very quick question: you have reinstalled everything, and started with new empty sets from fresh and still have those bugs you all report in the forum? or just with all your stuff that evolved trough years of legacy by now? because that always causes issues in any software.. we in the windows world are used to that

[3phase]

may the electric guitar prevail.. actually i should touch my again..this software is a huge inspiration in this direction.. a 606 over a mesa boogie bass amp.. my guitar on a marshel stack with out power soak.. and an lxp 5 for the one octave lower reverb to projekt the sound.. hmm ..pure audiophil fun.

and the only thing crashing are the neigbors eardrums... great

If this is how you roll, our product is not the best match for you - by definition! Sorry.


Cheers,
Dom[/quote]


I know.. snce you are trying to get into the footsteps of the magix music maker some things have changed..

But originally ableton life was a good match for people that roll...

And i still dont understand what you mean by reporting bugs correctly..shouldnt you be happy about users reporting bugs at all?

in a situation where the big bad midi bug only was reported by 2 users.. and only one did it correct..

just for my understanding... what is correct? secretly in the background of cause.. because ther are only user bugs.. no ableton bugs..

but beside that..

when you only accept a bug report with a reproduceable description... and dont get to it without...

Wasnt you prooned to fail on the big bad crashbug that only strikes randomly and only and certain computer models?

So which person could have supplied you with a reproducable setup?
isnt the truth rather that ableton finaly started to exept the possebilty of am own bug because more and more users reprorted crashes but found themself unable to do your " correct" bug reports?

a bug known is a bug fixed works only when you report it to people that listen and dont try to be more german tna the germans... frst you have to file a correct bug report and supply as wit a detailed descrpten how to find the bug.best with the involved lines of code of cause... and fill formular xbA3..otherwise we cant support YOUR bug..

sorry man..

if ableton really rolls like that its defently not the wright software home for me...
however after so many years you cant switch the bitch so easily...
I also still have logic.. they went dont that road you are going now aswell...years ago...

they still have the same bugs so... but its not the crash bug..
you really want to keep it?

[davepermen]

if they can't reproduce the bug, they have about 0 chance to find it in the code. debugging is very hard. downright impossible without knowing when it occurs under what circumstances, to then reproduce exactly that step function call by function call, checking where some value messed up and thus results in a bug that might lead to a crash.


and to explain you how a bug report should be (best case):

after a crash, there is a bug-file on the desktop (when you start live again). that should get send to [email protected].

that is the start of it, the propper one. it looks like you failed so far these basic steps (you send to personal mails, you post logs into the forum, etc)

[3phase]

just a very quick question: you have reinstalled everything, and started with new empty sets from fresh and still have those bugs you all report in the forum? or just with all your stuff that evolved trough years of legacy by now? because that always causes issues in any software.. we in the windows world are used to that

in the mac world we usually dont have to. at least not every year.. every month..
reinstalled 10.58 a few month ago.. it runs fine with any other app.. inkl live 7..

Shall i really wipe the harddisk and see it as my bug?

with all the legal software its a rather big hazzle to do a clean install and do all the reauthorisations...

However... i would do it if there would be the sligthest indication that ableton is telling some truth.. but the polemiks of mr dom shows a different picture..
He knows damn well that i am not the only person with the crash bug..

[3phase]

if they can't reproduce the bug, they have about 0 chance to find it in the code. debugging is very hard. downright impossible without knowing when it occurs under what circumstances, to then reproduce exactly that step function call by function call, checking where some value messed up and thus results in a bug that might lead to a crash.


and to explain you how a bug report should be (best case):

after a crash, there is a bug-file on the desktop (when you start live again). that should get send to [email protected].

that is the start of it, the propper one. it looks like you failed so far these basic steps (you send to personal mails, you post logs into the forum, etc)

i sended in that reports..wasnt detailed enough and i havent used theire web formular or some shit reason like that...
what leaded in a drop of the support case..

sorry.. a bug report is not a support case.. support only can start after a bug is analyzed.. to get there you have to acknowledge it first..

and i told them how to reproduce it.. run some midisequences.. smoke a cigartee ..wait..

more wasnt necessary to reproduce that bug.. just the patience to finish the cigarete or smoke 2 of them..
but that was a quite good chance to experiance the bug than...

i named my mac model... when they only do theire betatesting on pro books i cant help it

[jamief]

Regular crashing hear on live 8.08
xp2
2.16 ghz duo core 2 gig ram

I have been so busy have wokerd through the crashes and ignored them. Always for the most part been able to recover from the recover set feature on restarting live.
What where do i send to abeton support when running xp2 ? So that they can trace bugs ?

[davepermen]

you still refer to it as "the crash bug". there are tons of things creating DIFFERENT crash bugs. just because they all create a crash, does not mean they are all related in any form.

and no, i don't suggest you to reinstall everything and do this monthly, or so. i never reinstalled any of my vista machines at all, that's unneeded. but it's always a good thing to verify that's not the problem. what you should do?

backup, install osx and live (not even activated), test if it's stable for some days. after seeing if it's same or different, report that in your post, and restore your system. now there are two options:

a) it did not have the bugs after a fresh install: the bug is installation-dependent and should still get fixed. but one needs more details about the installation. as you're close to the ableton HQ, go over, give it to them.

b) if it DID have the bugs on fresh install: bugs only have to be searched from live to your sounddrivers and mididrivers. nothings' special about it.

and if a) would be true, i personally would consider staying on the reinstalled environment.


and yes i have quite some friends who HAD TO reinstall their osx as it got messy. apples aren't bug free just as well.

to your new post:

sorry.. a bug report is not a support case.. support only can start after a bug is analyzed.. to get there you have to acknowledge it first..

uhm, no, dude. a bug report IS THE OPENING part of a support case. and then, it starts with "where, how, why, what exactly, more detail needed there, and that, and please explain clearly". language is hard, sometimes people just don't understand each other well. and it can take time.

and i told them how to reproduce it.. run some midisequences.. smoke a cigartee ..wait..

you send them a perfect set that fails on your system, and the only thing they had to do was pressing space bar and wait? not "told" them. "gave" them. because telling is vague.

[Tone Deft]

if they can't reproduce the bug, they have about 0 chance to find it in the code. debugging is very hard. downright impossible without knowing when it occurs under what circumstances, to then reproduce exactly that step function call by function call, checking where some value messed up and thus results in a bug that might lead to a crash.


and to explain you how a bug report should be (best case):

after a crash, there is a bug-file on the desktop (when you start live again). that should get send to [email protected].

that is the start of it, the propper one. it looks like you failed so far these basic steps (you send to personal mails, you post logs into the forum, etc)

i sended in that reports..wasnt detailed enough and i havent used theire web formular or some shit reason like that...
what leaded in a drop of the support case..

sorry.. a bug report is not a support case.. support only can start after a bug is analyzed.. to get there you have to acknowledge it first..

and i told them how to reproduce it.. run some midisequences.. smoke a cigartee ..wait..

more wasnt necessary to reproduce that bug.. just the patience to finish the cigarete or smoke 2 of them..
but that was a quite good chance to experiance the bug than...

i named my mac model... when they only do theire betatesting on pro books i cant help it

totally disagree 3phase.

let's put it this way, Ableton asks for a bug reporting snap shot, they don't ask for anecdotal evidence. they get their software to tell them the details which is far more than you could tell them.

doesn't matter, if you don't want to cooperate that's your loss.

I've done what you're describing, record midi for 10-15 minutes on end while I wank off on keyboards. Live has never crashed on me doing that.

[3phase]

totally disagree 3phase.

let's put it this way, Ableton asks for a bug reporting snap shot, they don't ask for anecdotal evidence. they get their software to tell them the details which is far more than you could tell them.

doesn't matter, if you don't want to cooperate that's your loss.

I've done what you're describing, record midi for 10-15 minutes on end while I wank off on keyboards. Live has never crashed on me doing that.

i ve send many many of that crash files... and i named my audio hardware.. really dont know what the doms keeps on saying i havent send them what was needed.. probaly i passed out on a special bug reporting web formular..i dont know what he wants..

shall i send you all the files i ve sende to ableton? your mal account can take some megabytes?

good... because abletons mailserver cant.. most of my crashfiles was bounced because they was to big...