Ableton Forum

3phase wrote: why you dont call yourself goebels2k?

Is this sufficient to trigger Godwin's Law?

Hi folks,

As I mentioned in another post, please don't blame other users for reporting their bugs. Ableton wants this information - until we can reproduce a bug, we have no way to fix it.

Regardless of whether Ableton is a big or small company, our users have the right to stable software, and have the right to be annoyed if it's not stable.

But please help us by providing concise, proper bug reports that include information about your hardware, steps necessary to reproduce the bug scenario, etc.

Thanks,

yeah!..lets start putting people in a funnel, then we will flush em down a toilet!
oh yeah!
stab stab stab stab!

Dennis DeSantis wrote:Hi folks,

As I mentioned in another post, please don't blame other users for reporting their bugs. Ableton wants this information - until we can reproduce a bug, we have no way to fix it.

Regardless of whether Ableton is a big or small company, our users have the right to stable software, and have the right to be annoyed if it's not stable.

But please help us by providing concise, proper bug reports that include information about your hardware, steps necessary to reproduce the bug scenario, etc.

Thanks,

thanks

you guys LOLZ me.

3phase - you should set up a PA in front of Ableton HQ and play a constantly crashing gig. that's a very interesting offer to take your rig into Ableton for some one on one.

is a whine free forum even possible?

Tone Deft wrote:you guys LOLZ me.

3phase - you should set up a PA in front of Ableton HQ and play a constantly crashing gig. that's a very interesting offer to take your rig into Ableton for some one on one.

is a whine free forum even possible?

CAN'T YOU READ!!! Suck comment iz very shelfish of you 2 make, hiz setup is cannot be known be ne1, and shudent b hiz prablem n-e-waiz, since company solds him softwairz which spose 2 b 1000 purcent relible in front 1000's of peeple!!!!11!!!1!1!1!!


Sorry, couldn't resist, his posts are unbearably whiny/unreadable. Me, I'm still on 7, haven't had a crash in I don't know how long, and I couldn't be happier.

Dennis DeSantis wrote:Hi folks,

As I mentioned in another post, please don't blame other users for reporting their bugs. Ableton wants this information - until we can reproduce a bug, we have no way to fix it.

Regardless of whether Ableton is a big or small company, our users have the right to stable software, and have the right to be annoyed if it's not stable.

But please help us by providing concise, proper bug reports that include information about your hardware, steps necessary to reproduce the bug scenario, etc.

Thanks,

I completely agree that we should be hammering Ableton HQ with all the well written bug reports we can- we all want this software to be rock solid (I've had a few problems in v.8, not tons personally).

But the victimized whining can stop.

Don't make me post the purple fuzzy monsters again.

To Ableton:
Who should be using beta versions and is there any drawback to using beta version. I'm a little confused about occasional statements certain versions may not allow to go backwards because of changes but may be unstable. The reason I ask is that in some bug reports Ableton asks if the user has the latest version of Live and does the latest version refer to non-beta. Also on some occasions Live has locked up and is that considered a crash. When Live locks up I usually reboot the computer and will I still have an accurate crash log to submit.

Thanks

so we are not flushing people down toilets now?

chaibuka wrote:To Ableton:
Who should be using beta versions and is there any drawback to using beta version. I'm a little confused about occasional statements certain versions may not allow to go backwards because of changes but may be unstable. The reason I ask is that in some bug reports Ableton asks if the user has the latest version of Live and does the latest version refer to non-beta. Also on some occasions Live has locked up and is that considered a crash. When Live locks up I usually reboot the computer and will I still have an accurate crash log to submit.

Good questions, and I'll try to answer them all.

You should consider using beta versions if you're having problems with the current release version. If you aren't having problems, it's probably best to keep working as you are.

There aren't really drawbacks to using beta versions. In general, we believe that our latest beta is the most stable version of our software.

Currently, it is not possible to open a Set in a version of the software older than the one used to create the Set.

It's difficult to say whether or not a "lock up" is always a crash. In some cases, Live may become temporarily unreponsive, but may work again after some time. But if it feels "crash-like," then it totally makes sense that a user would think Live has crashed.

I don't know if a crash log will always be created if you reboot without first quitting Live. It may be better to try to force-quit Live before rebooting.

Best,

Dennis DeSantis wrote:

chaibuka wrote:To Ableton:
Who should be using beta versions and is there any drawback to using beta version. I'm a little confused about occasional statements certain versions may not allow to go backwards because of changes but may be unstable. The reason I ask is that in some bug reports Ableton asks if the user has the latest version of Live and does the latest version refer to non-beta. Also on some occasions Live has locked up and is that considered a crash. When Live locks up I usually reboot the computer and will I still have an accurate crash log to submit.

Good questions, and I'll try to answer them all.

You should consider using beta versions if you're having problems with the current release version. If you aren't having problems, it's probably best to keep working as you are.

There aren't really drawbacks to using beta versions. In general, we believe that our latest beta is the most stable version of our software.

Currently, it is not possible to open a Set in a version of the software older than the one used to create the Set.

It's difficult to say whether or not a "lock up" is always a crash. In some cases, Live may become temporarily unreponsive, but may work again after some time. But if it feels "crash-like," then it totally makes sense that a user would think Live has crashed.

I don't know if a crash log will always be created if you reboot without first quitting Live. It may be better to try to force-quit Live before rebooting.

Best,

How long of a wait would seem reasonable to assume a lockup. I'm not sure what force-quit means. I've tried normal exit and ctr alt del but it seems like only alternative is hard reset of computer.

nathannn wrote:so we are not flushing people down toilets now?

Yeah, dammit! I had a perfect picture to follow the others. Now what do we do?!?

ze2be wrote:

nathannn wrote:so we are not flushing people down toilets now?

Yeah, dammit! I had a perfect picture to follow the others. Now what do we do?!?

the toilet would still work if 3phase would just quit flushing his tampons for a few days