No reaction to any of several bugs I posted in beta forum

[3phase]

tss. i am not whiny i am angry.. and stupid fabboys with their.. "its totally stable it only crashes sometimes" attitude even make me more angry...

and your stupid question here in the thread too..

have it ever come into your mind that you are maybe not the first that has reportet a bug or that its maybe allready solved or that your issue might be a user error? what is probably most likely with your type anyway...


Its from absolutely no relevance how ableton handles the bug hunting now..its too late..

far to late.. we have february allready ..10 month after release !!!!

ts..whiny...

i want to know if i can do my springtime gigs with this piece of shit software or not..

[Poster]

tss. i am not whiny i am angry.. and stupid fabboys with their.. "its totally stable it only crashes sometimes" attitude even make me more angry...

and your stupid question here in the thread too..

have it ever come into your mind that you are maybe not the first that has reportet a bug or that its maybe allready solved or that your issue might be a user error? what is probably most likely with your type anyway...


Its from absolutely no relevance how ableton handles the bug hunting now..its too late..

far to late.. we have february allready ..10 month after release !!!!

ts..whiny...

i want to know if i can do my springtime gigs with this piece of shit software or not..

you're abusing the current state of affairs for your own issue, which is just weak..
you jump on any given rant/complain thread just so you can piss even more on Ableton, even if the problem a user posts is not yours..
Ableton this, Ableton that.. bla bla bla.. look at you.. mr. rant.. all just for the sake of ranting.. hardly anything constructive comes out of your pen..

if I remember well from the days you were having that MIDI issue; you were the one that didn't want to provide the full info support had asked you..
you thought you knew better than the people who actually code Live.. you thought you could decide which info was relevant or not to get your problems solved..
I'm I right?
if so.. do you think it strange support drops the case? I mean if you're not willing to work with them, why should they work with you?
be open and constructive.. get's you much further in life and your bugs fixed sooner..

anyway..
we all know the current state of Live isn't all that, but why do you still feel the urge to put more and more oil on each fire that appears on these forums?

[bicarbone]

Seeing the video about ableton developers where allmost everybody says that he learnt coding themself just states between the lines that not the most expensiv guys in the biz got hired... even when learning a thing by themself dont autimatically says that the guys are bad.. but its remarkabel that ableton asks for any little shit job for a complete finsihed offical education and biz degrees..except for the coders..

why? are untrained coders better than the ones with a university diploma or just cheaper?

I'm an untrained producer. I learned mixing myself. I'm unexpensive in the biz. My tracks sound muddy. That's why I don't sell them.

Now, what I'd love to see is a list of known issues and bugs published by Ableton.

After having upgraded to Live 8 suite, I need to know which bugs they're working on, and for which ones I'm expected to find workarounds myself in the meantime, as untrained as I am.

Still, while feeling dodgy, Live 8 looks tasty and sounds promising. I just want to trust it when I'm using it. As simple as that.

[Dennis DeSantis]

Hi folks,

As someone mentioned in this thread, the forum is a valuable place for bug discussion, but it is by no means the most efficient way for us to manage and track bugs. While everything that's posted to the bugs forum is reviewed, we cannot promise to actually respond to every forum post. You can be sure, however, that bugs that are reported there are filed and dealt with.

I definitely understand the feeling that, by not receiving personal replies, your posts have gone into the void. Please understand that this is not the case. There are many, many more of you than there are of us, and we simply can't get back to everyone in the forums personally.

If you've experienced a crash, we strongly recommend contacting support directly.

Best,

[djsynchro]

Fair enough...

[djsynchro]

tss. i am not whiny i am angry..

No you're whiny. Always.

[Coupe70]

While everything that's posted to the bugs forum is reviewed, we cannot promise to actually respond to every forum post. You can be sure, however, that bugs that are reported there are filed and dealt with.

Dennis, I understand what you're saying.
But I guess the people that are complaining here do not expect
an extensive answer to their forum bug reports, but would like
to see some small status feedback like "Read, reproduced, filed as
bug" or something.

Otherwise they feel like having to ask about their bug report over
and over or send it in several times to be sure that they are heard.
And this can't be what you want as it makes it more complicated
for you because of all the unnecessary "have you heard me ?!" postings
in the bug report forum and all the double bug reports.

And I think if you do public beta testing the testers / bug reporters
deserve a short (!) public feedback.

[davepermen]

3phase crying in here?


.. have .. to .. resist ..

but anyways, i never cared about the forums for bugreports. that's why it's not the official way to report bugs, right? http://www.ableton.com/pages/support/co ... al_support they state the mail.

[scientist]

As someone mentioned in this thread, the forum is a valuable place for bug discussion, but it is by no means the most efficient way for us to manage and track bugs...
If you've experienced a crash, we strongly recommend contacting support directly.

i've been suffering from persistent crashes, resulting in a multitude of emails back and forth with support. ironically, the solution to my issue was posted as a sticky in the support forum (the known au bug) over a month ago. i was never made aware of this known bug or the forum post until today (fwiw i had given up on the support forum long ago).

why wasn't this mentioned immediately? an entire month of back and forth support emails (including attached log files and extensive descriptions of the issues) and no one bothers to mention that my problem is most likely due to a known and publicly announced bug?

since the expletive laced public forum rant freakouts have already been taken care of by others, i'll post a picture that sums up my current opinion on these matters:

[3phase]

[
if I remember well from the days you were having that MIDI issue; you were the one that didn't want to provide the full info support had asked you..
you thought you knew better than the people who actually code Live.. you thought you could decide which info was relevant or not to get your problems solved..
I'm I right?

No, you are not wright.. I have provided all infos necessary back than, but ableton wasnt willing to belife that the bug just happens when using midi without any other necessary tasks to trigger it.
They insisted that i give the info what i was doing to crash the program and interpretated the answer , nothing ..smoking a cigarette as unwillingness to give the real info... but it was just the truth..


blinded by arrogance.. i told them back than that questions about my hatdware are irrelevant and the nature of the half year later found bug have prooven me wright..

do you know the movie brazil?

[3phase]

3phase crying in here?


.. have .. to .. resist ..

but anyways, i never cared about the forums for bugreports. that's why it's not the official way to report bugs, right? http://www.ableton.com/pages/support/co ... al_support they state the mail.

anyway to reprort a bug is the wright way ... you cant force the user to fullfill your routines and spend the time to do so.. you should be happy that users report bugs allready.. because you seem to have the problem that the majority of the bugs wasnt even reported by your own betatesters..


Why are Ableton people so god damn arrogant about theiere work?
why do they call theier bugs the users bug?
isnt this software ment t run on all platforms and configs?

If not so please name apporved hardware/software combinations and name hardware you are not able to do propper code for..


CAn somebody please explain me how a user can cause a bug?

[davepermen]

yeah, as it's very easy to handle and filter out and control and manage SEVERAL bug sources, compared to one, in detail specified one..

guess which solution would mean more work effort on the bug managing? as opposed to the actual bug FIXING.

but of course, ableton has to do anything the way YOU want it, just because you are THE 3PHASE, the holy music production god, who can't read a simple page where it's documented how you have to contact them to get help, but instead is allowed to cry around all over the public forums to make them look bad. yeah, good way to get them to help you, dude.. really.


but, you know, you failed long ago, and we all know that


but one day, you will understand 'using common sense', and would notice that your way just doesn't make sense.

that ableton isn't perfect, we all know. they admitted. now you could be happy that your publicity stunts 'worked', as you got public acknowledged from their boss, that they failed.

but you won't be happy. you continue to bitch about a business that you have no fucking clue about: software development.

way to get old and grumpy, dude..

[davepermen]

CAn somebody please explain me how a user can cause a bug?

because everyone uses it differently, and triggers thus different bugs. YOUR bug was never a bug for me, so it was "the 3phase bug". this is not an attack against you, just a simple way to catalogue bugs. you use different hw and sw than i do, so you WILL HAVE DIFFERENT BUGS.

when will you understand that?

[3phase]

i was using midi !

that gives me the credit for my own bug?


teh other big one was that i mixed 16 and 32 bit files in one session...

very extrem and rare behaviour i gues.. :-/


what are the other people doing with live? playing 2 loops and watching the goldfish for the next 10 hours?

[davepermen]

no, but it's YOUR bug, because you used midi with your specific hw setup.

which is a different setup to EVERY OTHER ABLETON LIVE USER ON THIS WORLD.

and it COULD be that your combination of that hw and live triggers the bug, that is otherwise not happening.

but i know that doesn't make sense to you.



i use midi myself with different hw and sw, and i had one midi bug. i got it down to a specific situation, sent in, and the fix was deployed in the next update about a week later.

that was "my midi bug", which was in a beta (that's what they're for, finding and reporting bugs.. but the same should be done in non-beta ones).

i bet, that you could send your sets over that have those bugs, and they would work perfectly fine here. maybe by then, you would understand that the WHOLE ENVIRONMENT matters.

including the user, which might happen to use stuff in a slightly different order, thus not triggering a bug, or triggering one.