3phase wrote:
and i named the problem pretty acurate back in july...
not accurately enough as they say. they could not trigger the bug by your description => it was not accurate enough.
I really dont know if i can belife what mr dom says very much.. either he belives what he says or he has to execute an agenda to never commit such problems in public for sales resaons..
you do believe your statents, he does his... i can chose to believe the one that sounds more logical.
but when following is true..
certain mac computers had the bug..
no, THERE IS YOUR PROBLEM:
certain mac computers HAD BUGS TRIGGERED. does not mean they triggered the SAME bug.
inkl. my 2 years old mac book..
We can assume that many users could have experianced the bug.. the little poll, even when from no statistical significance, shows this tendency too... somehow a very rough short statistic catch is closer to a realistic tendency .. at least the poll has shown that more than 2 users have problems...
and that does (see above) NOT MEAN AT ALL THAT THEY HAVE THE SAME PROBLEM. i'm sick. you are, too. must be the SAME thing, then (right now, swine flu is hip).
and i doubt we would have seen a fix so deep in the core functionality when it really only would have been 2 users with the dualcore/midi bug problem.. some of the info we get here from ableton is not so consistent..except...
When following is true aswell..
only 2 users reported the bug.. only one correctly...
which is. and what's amazing about it: they still took the time to INVESTIGATE AND FIX THE BUG.
unlike apple, f.e., which till today doesn't aknowledge, that their file copy algorithm can fail over network, and result in a LOSS OF THE FILE ON BOTH SIDES. how do we know, then, that the bug exists (since years. since the first osx, and maybe even longer, not sure right now)?? because they have actively written bug-hiders in their time-capsule. namely they checksum ANY file transfer to the time-capsule to be sure it came over there, and is still valid data. instead of fixing their network bug. or openly agree that they have it (while it got proven time and time again).
It gets really clear that my not "correct" report cant be the main problem here..
yet it still is, with any of your reports, the main problem.
That it was only 2 users on a bug that should have effected many machines shows that many beiing quiete and happy with the recovery..
no, but those two that had the problem got it fixed, and the others with other problems GOT THOSE FIXED, too.
Thats the problem here..
the way you explain your stuff is, it's undetailed "thrown on the table" stuff, without clear explanation on what exactly it is you mean.
And this again only ableton can fix.. and if thats really the case and not some Dom politics..they actually should be thankfull for all the noise..
only you can fix how you work together with dom and those. and both sides stated, it's not the best way it CAN work. so better sit together and find a way. you life so close to each other.
And users that have crashes should report them to the poll and ableton of cause .. wether its one bug or many dont matters in a situation where the company thinks there are none and probabbly has stopped working on the fixes allready...
yes, but the company doesn't think that way. but there are tons of bugs to fix, the list surely goes into the thousands. and you can only spend so much time per bug to try to replicate it, see if it happens, and fix it.
If really only 2 out of hundrets or thousend s complain we are actally close to the happy new world but i dont helps to find mean bugs
they're only mean because they affect you. you wouldn't fight that way for a bug that you wouldn't have but i would, right?
and guess what, i wouldn't as well. i would invest time together with ableton to fix it. i would "do my part". they would "do theirs".
my reputation? i would worry more about abletons reptation.. and true.. they was nice in the past and had some ethics..
but does that look like the same company for you now?
it does for all, but you right now have the mark of "old freak that hates everything and wants to show he's better, and wants to get the cake and eat it". i know you aren't. but you act like this.
first insulted.. than dropped support case .. threathend with legal actions and told a lier in one word..and that all because i dont want to see the bugs as my bugs and take responsibilty for them?
no, but you want them to fix it without trying to help showing what's to fix.
thats indeed very ethic..
so isn't your wish of them doing everything for you without you helping them to know what it is you want.
or at least not really cooling me down.. however... as long maybe some other crashbug victims might open theier mouth? and of cause you can play it silent and write them directly..
i'm a beta tester and had crashes in beta. i reported them by sending the file in, short line what i did, and it got fixed. like all of the easy to find and fix bugs. some are nasty to find and thus can stay for long.
looks like it's you..
but i really dont belive that this is all exclusiv my problem... so let them know that the crashing is still there and that they have to fix it for all users... or name incompatible hardware as such...
you still call it 'the crashing', believing it to be one issue. that is exclusiv YOUR problem. till you get that, you're completely out of luck to undestand how ****ed up your position actually is.
And when they tell you fixes plese repost them in the forum... for all the others that are even to shy to write to them in privat..
yeah, build up the fancy revolution. we want to fix THE MIDI BUG!! be the rebell, fight the death star!
or simply, accept that there isn't a one-fits-all-solution, and thus, you have to help in each case to find a solution for that case.
Hope your problems are now resolved get back to making the music and don`t get bogged down with all this