You can help us improve Live

[Piplodocus]

Sorry poor choice of words. There are routings that crash Live, to me the routings seem logical. When I send in my reports, am I reporting something valuable (experiencing a bug?), OR do they see this stuff at Ableton and say to themselves, "Well you just cant route things like that DUH."

Software should never crash. If a certain routing is guaranteed to make it crash and the developer knows it does the software should either be fixed, or be changed so it refuses to let you make that routing and/or tell you why you can't do it in a pop-up box. Software doesn't have to do everything, but it shouldn't let you do stuff that makes it fall to pieces. That's error handling.

[mbira]

@chapelier fou

Yes, unfortunately we will not have the chance to include data from computers which get never connected to the internet. But from our authorization system we know that this is the case for less then 2% of all computers which run Live so we hope this will not bias the data to much.

Regards, Bernd.

I just wanted to mention that at home on my studio, I use live and it is hooked up to the internet, but at gigs-where it is most important to never have a problem-I never have it hooked up. Also, I use Jackrouter and a different soundcard at home than at a gig. Just one of those things to keep in mind that there are probably many more unusual situations than just 98% online and 2% offline...

[Gregory Wells-King]

In other words was Live crashing and making a bug report for Ableton, OR was Live crashing because I was doing things you just cant do.

Urghh indeed.

I'm sure it's down to how I push it sometimes or 3rd party plugins, so have virually never sent one. I possibly should because I can't tell myself wether that's the case, Infact I think it's down to my audio interface most of the time.

[Broesky]

Where is the Ableton folder located on OSX Lion? Apple seems to have switched things around.

[The Philosopher King]

Is there any real point to this?

I reported numerous crashes when the Bug report thing first came out.

Nothing of any real value has been fixed between then and now.

How can this software be so buggy after three years? I don't get it.

Think I'll skip this 'upgrade'.

Carry on.

[tscharf]

usage information only tells you about the features that people actually use and are useful. You may be lead astray by it because of bad implementations. Step time entry, for example, is something I would dearly like fixed, but if you looked at my usage of it you would only see that I never use it. Not because it wouldn't be useful, but because the implementation ableton chose is completely and totally wrong.

[danger]

For what feature updates the userbase need, you only need to collect the FR emails and monitoring this forum.

[Broesky]

Anybody know where the folder is located on OSX Lion?

[darjee]

My music computer is never connected to internet.

same for me

[BdD7ntsr]

Hi !

I want a real big update for Windows 64 bit OS ! Your update only concern osx lion that's enougth !!
And i'm agree to think many crash happen because ableton do not support 64 bit so please make it.

[friend_kami]

usage information only tells you about the features that people actually use and are useful. You may be lead astray by it because of bad implementations. Step time entry, for example, is something I would dearly like fixed, but if you looked at my usage of it you would only see that I never use it. Not because it wouldn't be useful, but because the implementation ableton chose is completely and totally wrong.

the things i use the least are the things tha ti have the most problems with.
looper for exmaple. has a tendency to never work properly, thus i've simply stopped using it, only occasionally revisiting it in the hopes that it has been fixed. at the least on my computer it still fires random cleared buffers at times, including full-on crashes live. so if i want looper fixed, and they are only looking at user useage, does tha tmean that i should use looper more in order for the useage on looper statistics to rise then?

seems like a very stupid way to go about it, since it's quite obvious that the things with the most problems are more likely the things you avoid to use for that very reason that you have the most problems with them.

[Ableton Denver]

Software should never crash...Well...

Software mitigates a system in a constant state of flux controlled by monkeys written by monkeys (species reference, nothing person). Logic gates fail.

Internet/wireless on while live - no way.

Internet / wireless on in production - sure, but proll'y not.

I would rather a logging system be used, like the one already there.

Sure, your extra software is very light and stable, good. But I also have to turn on all these subsystems I intentionally turn off for performance and stability. If Live was built for live then consider the reality of the performance - not all Ableton use is art installation communicating over the internet.

Working with, and having history as, instrumentalist orientated performance, in turn the desire is control, stability, and using less to get more. Turning the internet on for a live live Live annon-o-cast is going to get a lot of data from people who run machines in such a manner.

Sarcasm, to me, dictates predicting this report :

"Strangely 100% of the recorded crashes were connected to the internet when the error occurred."

Coincidence? -> I think not.

Work on better local logging IMHO, it's already cooked in real nice.