Ableton Forum

Hi,

I would appreciate it very much if Ableton would reintroduce the Announcements section.

I don't visit these forums very often and now it's quite difficult to search for Live
changelogs. Now it's much more difficult to find out, whether or not any given bug has
been fixed and if, when. Perhaps you could link to it from General section or start
separate threads, other for commenting and other for informational purposes?

Cheers,
Koston

+1

-1

I like it in the General section

Koston wrote:Now it's much more difficult to find out, whether or not any given bug has been fixed and if, when.

it's a coin flip if a feature is fixed for you. the only way to know is to try it yourself.

how does Ableton learn about bugs?
from customer e-mails and their own internal testing.

how goes Ableton know if a bug is fixed?
from customer e-mails. their internal testing doesn't mean jack shit to tell if something is fixed or not.

never let a software company tell you something is fixed, try it yourself and let them know exactly how it's broken on your system.



yeah, just sticky it to the General section.

Tone Deft wrote:

Koston wrote:Now it's much more difficult to find out, whether or not any given bug has been fixed and if, when.

it's a coin flip if a feature is fixed for you. the only way to know is to try it yourself.

never let a software company tell you something is fixed, try it yourself and let them know exactly how it's broken on your system.

I've been in software development business for a decade and in my book, beta-testing is something you hire people and pay salary for. If Ableton wants me to be their tester, they can hand over binaries with debug symbols and access to bug tracking system.

Meanwhile, I can appreciate having easy access to version changelog history.

Koston wrote:

Tone Deft wrote:

Koston wrote:Now it's much more difficult to find out, whether or not any given bug has been fixed and if, when.

it's a coin flip if a feature is fixed for you. the only way to know is to try it yourself.

never let a software company tell you something is fixed, try it yourself and let them know exactly how it's broken on your system.

I've been in software development business for a decade and in my book, beta-testing is something you hire people and pay salary for. If Ableton wants me to be their tester, they can hand over binaries with debug symbols and access to bug tracking system.

Meanwhile, I can appreciate having easy access to version changelog history.

I hear ya, I've 37 and have been a hardware engineer for 13 years along with some software. I've had these discussions with my software cohorts at work and for the last year been discussing this very same topic on this forum regarding Ableton Live.

people don't like this but Ableton have literally asked that users be beta testers for 8.1, things are that out of hand. the users are a bug rich resource, far better than paid testers. they've never done this before but these are 'interesting' times.

I have had very few problems. that's probably because I've been a beta tester for the last 4 versions.

To be honest, using users as a testing medium is practically an accepted practice these days.
Without the ability to hire 1 tester per 2 coders (a luxury afforded by really large companies only), you're not going to catch all the bugs in a piece of very complex software.

Live is a VERY complex piece of software, that does a LOT of stuff and does (most of) it very *very* fast. Props to the Ableton lads for their efforts, and if having such a complex prog with a few bugs lets me play with new features sooner, and keeps Ableton solvent (let's face it, if they did a Netscape a completely re-wrote Live from the ground up, they'd end up like. . . well, Netscape), then I'm happy

However, I would agree about the bug tracking system: maybe it'd be nice to have a proper "Report A Bug" form on the site somewhere, kinda like a helpdesk. A lot of companies keep a list of known bugs publically accessible so that all of us numpties get to see how many people are having problem x, and what sort of attention problem x is getting.