I confess...

[hoffman2k]

[
You complained about a company not allowing big files in their email. If there were no file limit, your mail would have to wait till the last big file that comes in finishes downloading.
Where we differ in approaches is: You hold it against them. I would have just used one of the many free filesharing services online. But not after I tried if the same bug happened with a smaller file.
You can get that file there if you want to. Instead you posted 3 rants.

I tried helping in one of those threads and got snubbed so I'm not sure why I'm even bothering now. I'll just say it one last time: If you actually help Ableton find the cause of your problems, they'll be able to fix it. If it gets confirmed, it may not be fixed on the next version. But they'll fix it.
You don't have to take my word for it. I literally have seen 90% of the bugs I reported disappear.
Your mileage definitely varies, but then again.. You're driving backwards..

I dont know what you are talking about ? filesize limits? why this should bother me? its theiere problem when the crashfiles cant reach them and not mine.. and i dont know why i ve to fight with you. you dont work for ableton..or?


my problem is the crashing and monster loud pops.. that dammages my life sets and possibly the speakers of the venue and the ears of the audience...


and i tryed to help but my case was closed imideatly by mr dom because he didint liked my way of writig..
When i answer to the question what i ve done to cause the crash "i smoked a cigarette" the info is there... when the dont belive that the crashes happen on a random base i cant confess things i havent done

again..this are not my bugs.. and closing my case because i gave to little info about my hardware setup? ts..what has my hardware setup to do with your bugs? this was so clear a buying of time and i just refused to play this kind of callcenter games.

Any serious question about my software config i have and would have answered.. but retarded ..what do you do with your atari computer questions???

Sometimes you see in the design of abletons midifunctions that you proably really dont know what people do with an atari computer in 2009

having fun with midi !!

Hey, if you can't see that your problems could be solved by answering the questions people ask, then by all means keep shouting.
Why would they want to know what system you're using? Hmm.. Ehrm.. Hard one..
I mean, what could they possible do with that information other than try to recreate the bug in an almost identical scenario. Those idiots!

And the nerve of that Dom fella to have tried to help you. Who does he think he is? Head of support at Ableton?

[liam18]

Because i wanted to try exporting in various formats to compare the mix on my ipod against other bits of software i've been using.

Yes...I'm a shmuck already. And I'm sorry etc etc. But I'm still hoping that becoming a legit customer somehow fixes this. And that I've served as a cautionary tale to anybody else cluelessly downloading a hack from bittorrent

[Slightlydelic]

[

Being the hippie that I am, I always presumed that helping others and yourself get rid of a potential showstopper would keep the bitterness on a low. But what do I know..

so so.. a hippy...

and i am again a ranter..i was called a ranter on my first topic here where i wanted to find out if my crashings are related to live or the os...
than the problem was put to my karma..
than i had to do another thread to finaly get the bug confirmed..instead that ableton anounces such major bugs themself a soon they get it... what is clearly a sales before customer support attitude.

And than you do an bug fix beta that had more new problems than fixes..tons of crashes?
And than from that to a propper release within days?

wow..can we belive that?

i ve to go into production again tomorow..we will see if the crashing is gone..
atleast 32bit file bug is still there... so lots of extra work before on can risk to be on stage with Live ...
beside the potential killing of expensiv tweeters...




I really can say that i ve developed a certain misstrust in Ableton lately..

if somebody would tell me that ableton uses slave labor of blind chineese kids to pack theiere products i would belife it wright now..

oddly enought if ableton were to be using child labour, they would loose the rights their copyrights and patents afford them, and as such you would be perfectly OK to use the cracked version.

[citizenchris099]

Because i wanted to try exporting in various formats to compare the mix on my ipod against other bits of software i've been using.

Yes...I'm a shmuck already. And I'm sorry etc etc. But I'm still hoping that becoming a legit customer somehow fixes this. And that I've served as a cautionary tale to anybody else cluelessly downloading a hack from bittorrent

Look the hacked Live has nothing to do w/your problems. Get that idea out of your mind ok. If you like Ableton then you need to buy it otherwise move on.

[stringtapper]

no,it's bloody genuine alright.

An yes, I'm a berk, a low life etc etc. That said, I've been stung too many times in the past buying software that promised more than it delivered. So being the dumbass I am, I thought I'd have a go at a hacked version of Live 8, and this happens.

and look, I'm not having a go at ableton....if I have an axe to grind it would be the third party developers who've created this draconian piece of anti-theft software.

So, now everyone's had a chance to point fingers and laugh, great, glad you've had a good a thread. But I'm still hoping someone can let me know if this has happened to them and this really is an act of anti-theft thuggery...or might it be unique to me eg a component failure. I've searched far and wide on the net, and seen in one thread, a single mention of a 'fade-out' glitch on Live 4...and that was a posting from 2005 i think.

I really need a fix for this....if it's a case of paying a fine for some heal code, then I've been a naughty boy, I'll pay. But ideally, I'd like to do what the anti-theft code was designed to do and become a legit, happy, customer

Where did you even get the idea that this was "anti-theft thuggery," hmm? Did you look this up before you posted here? Or did you dream it up first and then post here, automatically assuming something that may not even exist?

And then this begs the question: why did you stop there? You could have gotten really wild with all of this speculation. Maybe it was SkyNet. Maybe it was the Illuminati.

Maybe there are tiny Tron characters having disc battles inside your sound card at this very moment!

The possibilities are endless!

[liam18]

yeah that's great..glad you're still getting some fun out of this thread.

May i refer you to someone who posted earlier on this thread that they paid a fine to ableton to 'heal' their pc. Might be true, might not. But the 'fade out' warble I'm getting from mic-in recordings has the hall-marks of a deliberately implemented and maddening glitch, rather suspiciously occurring 1 week after the hack is activated. So I'm sure I'm not being too daft here.

[hoffman2k]

yeah that's great..glad you're still getting some fun out of this thread.

May i refer you to someone who posted earlier on this thread that they paid a fine to ableton to 'heal' their pc. Might be true, might not. But the 'fade out' warble I'm getting from mic-in recordings has the hall-marks of a deliberately implemented and maddening glitch, rather suspiciously occurring 1 week after the hack is activated. So I'm sure I'm not being too daft here.

Its not technically possible for Ableton to do what you claim. For one, they'd need a list off all audio interfaces in the Live code. Not to mention powers beyond asio or coreaudio. An educated guess would suggest one of the other programs on your system messed up your buffer settings or a sample rate conflict.
All the copy violation detection does in Live is tell you you've been busted and the application will stop working.

[Slightlydelic]

[
You complained about a company not allowing big files in their email. If there were no file limit, your mail would have to wait till the last big file that comes in finishes downloading.
Where we differ in approaches is: You hold it against them. I would have just used one of the many free filesharing services online. But not after I tried if the same bug happened with a smaller file.
You can get that file there if you want to. Instead you posted 3 rants.

I tried helping in one of those threads and got snubbed so I'm not sure why I'm even bothering now. I'll just say it one last time: If you actually help Ableton find the cause of your problems, they'll be able to fix it. If it gets confirmed, it may not be fixed on the next version. But they'll fix it.
You don't have to take my word for it. I literally have seen 90% of the bugs I reported disappear.
Your mileage definitely varies, but then again.. You're driving backwards..

I dont know what you are talking about ? filesize limits? why this should bother me? its theiere problem when the crashfiles cant reach them and not mine.. and i dont know why i ve to fight with you. you dont work for ableton..or?


my problem is the crashing and monster loud pops.. that dammages my life sets and possibly the speakers of the venue and the ears of the audience...


and i tryed to help but my case was closed imideatly by mr dom because he didint liked my way of writig..
When i answer to the question what i ve done to cause the crash "i smoked a cigarette" the info is there... when the dont belive that the crashes happen on a random base i cant confess things i havent done

again..this are not my bugs.. and closing my case because i gave to little info about my hardware setup? ts..what has my hardware setup to do with your bugs? this was so clear a buying of time and i just refused to play this kind of callcenter games.

Any serious question about my software config i have and would have answered.. but retarded ..what do you do with your atari computer questions???

Sometimes you see in the design of abletons midifunctions that you proably really dont know what people do with an atari computer in 2009

having fun with midi !!

ive just remebered the thread hoffman is talking about, as your displaying the same kind of attitude again.

"its not my problem if they cant receve the file"

yes it is your problem, because your bug wont be fixed if they havent got the file.

and closing my case because i gave to little info about my hardware setup? ts..what has my hardware setup to do with your bugs? this was so clear a buying of time and i just refused to play this kind of callcenter games.

why jump to conclusions and not just give themm the info they want, they want to help you, they're not saying it is your hardware setup, but atleast they may be able to rule things out.

and on the other hand, i have 2 computers running live, it doesnt crash, spike, or otherwise behave badly, so what is different about my situation? it can only be the hardware.

im not trying to have a go here, but you seem to be doing very little to help ableton help you overcome your problems. i would realy like you to realise that, i dont understand why you cant see that for your self. My fully working live setup is an absolute pleasure to wile away the hours on, and i would wish everyones experience of live to be atlast as good as my own.

[Hidden Driveways]

yeah that's great..glad you're still getting some fun out of this thread.

May i refer you to someone who posted earlier on this thread that they paid a fine to ableton to 'heal' their pc. Might be true, might not. But the 'fade out' warble I'm getting from mic-in recordings has the hall-marks of a deliberately implemented and maddening glitch, rather suspiciously occurring 1 week after the hack is activated. So I'm sure I'm not being too daft here.

I've been reading this forum daily for years. Your symptoms are unusual for someone using a hacked version of the software. In the past I recall people claiming that they got the aforementioned "copywrite detected" warning, then their version of Live wouldn't work anymore. There have been reports of hacked versions of Live that would do this, and also corrupt any old files that were created with the hacked version, so they could never be opened again.

They were all things that I've read on this forum, not that I've experienced. Since you have a crack of Live 8, your problem could be a brand new thing. The trouble is that you have downloaded this thing illegally. You don't know where it came from, or who did what to it. The only criminal is you.

There was this great guy named Mike Rock who was a manager at a Guitar Center in New York. One time a young employee was telling him the troubles he had been having with a girlfriend, how he moved in with her and she went psycho, etc etc etc. Mike just looked at the kid and said: "Look, if you're eating a shit sandwich, remember, YOU ORDERED IT!"

Sorry Liam, but you ordered a shit sandwich. The good news is that this will likely not be your last meal, and you have a chance to dine well in the future.

[3phase]

[

Hey, if you can't see that your problems could be solved by answering the questions people ask, then by all means keep shouting.
Why would they want to know what system you're using? Hmm.. Ehrm.. Hard one..
I mean, what could they possible do with that information other than try to recreate the bug in an almost identical scenario. Those idiots!

And the nerve of that Dom fella to have tried to help you. Who does he think he is? Head of support at Ableton?[/quote]


Ok mr acid... I helped enough.. if ableton says i havent they lie.. its just that the dont liked my tone but i followed and answered theire requests..

Sorry man..Mr Dom himself started the "war" with his quite rude calling me a ranter just because i brouht the problem to public attention

However.. i post my emails with ableton... i maybe wasnt very friendly but i tried to help ...
But the arrogant ableton support needs a bit more respect and devotion otherwise they cant work on it...
Sorry.. i had the shit in front of the people., i was called a ranter for naming heavy bugs in public.. i dont need to play nice...



So once and for all the mails.. See yourself if i was helping or not

sorry that it sitches to german at one point


Ableton Support to me after beeing called a ranter in the forum by the dom:


could you please install Live 8.0.4 and send a crash log of 8.0.4 if it crashes again?

What are you doing exactly to reproduce this?


I wrote to support on 28. Juli 2009 13:16:14 MESZ

it just happens .. even smoking a zigarette and looking out of the
window causes the ocassional crash...

its related to midi..and its worse on 8.04...

and because i hate the grey in grey startlogo from live 8.04 i wont install it again...

i might go for the beta.. it cant get worse as it is now.


They answered


Hi,

sorry but i am afraid that this does not help us at all..

Would you mind to describe what you do before it happens?
We need a description of how to reproduce this otherwise we have no starting point to investigate.

They gray splash screen is the suite splash. If you want to have the colorful splash in 8.0.4, then install the non suite download.


I anwered

I worked on my liveset i had last sunday.. I was doing just everything you do... recording clips.. editing midifiles.. assigning controlers... or just smoking a cigarette..

ther is no special pattern in the crashes, i just had them every 2 hours..what scared me somuch for the gig that i went bac to 7..

to realize that you cant reload loops renderd in live 8 ...

why do i have buzzing +20 db noises when i start a live 8 loop in live 7?

what are you doing with the audio files?


Only hint i can give is that the trouble started after doing more with external midi devices

within my very complex midi setup ocassionaly a midiloop occured..it seems that live 8 dont likes that and some crashes might be related to that...

but however.. a midi loop is something we used to play tunes with in atari days.. a midi loop is not allowed to crash the daw.. it just clogs the midi bus...

A DAW is not allowed to be crashed by midi traffic !

But as I said.. it´s just an idea that the crashing might be related to midi traffic.

But maybe try some midi loops

And one more thing about midiloops..

because Ableton Live dont has latency free midithru i dont use it anyway.. So i didnt had midi loops thru Live...

The trusty tool midipipe is responsible for handling midi issues on my mac...

and when ther was a midiloop than it was a midiloop within midipipe...

What dont bothred Live 7 and before..as it dont bothers Logic or cubase...

So the crashes just might not be related to that..




The answer to this mail was that on the 28.7

Dom> 3p

Hallo Sven,

sorry, dass ich mich hier einmische, aber ich habe mir Deine Reports gerade durchgelesen und so kommen wir leider nicht weiter.

Wir brauchen eine detailierte Beschreibung Deines Setups und was genau Du damit tust, sonst kommen wir zu keiner Lösung.

Ich habe Dir doch im Forum die Anleitung zu Supportrequests gelinkt.
Trotzdem haben wir noch keine ensprechenden Infos und alle nötigen Logfiles vorliegen. Warum? Bist Du etwa doch nicht an einer Lösung interessiert?

Ich liebe Humor, aber mit Sätzen wie "passiert beim Rauchen" oder "ich mag 8.0.4 wegen dem Splashscreen nicht installieren" ist doch in einer Fehlerbeschreibung niemanden geholfen. Einige Mails später kommt dann überhaupt erst die erste Erwähnung von Midipipe.

Wie gesagt, wenn Du möchtest, dass wir weiterhin mit Dir an Deinen Problemen arbeiten, funktioniert das nur mit Dir zusammen und Teamwork.
Wenn das aus irgendwelchen Gründen nicht Deiner Motivation entspricht, teile uns das ruhig mit.



Dom is complaining that i dont help enough..

I answered to that :

3p>Ableton

Die blöde anmache als ranter beschimpft zu werden motiviert nicht gerade... öffentliche kritik is nicht gleich ranting

Und ich glaube auch nicht das system stabilitaet explezit mein problem ist sondern euers..Als anbieter DER Live software..
Die Konkurenzlos dasteht..

Aber das kann sich schnell ändern in der heutigen Welt, deshalb rate ich zu etwas weniger Arroganz.

Live ist auch nicht mehr als ne loop schleuder mit mediocrem timestretching. Einzig in der exterenen steuerbarkeit brilliert es..
Dafür kann es keinen miditimecode ausgeben und hat sich damit als echte DAW eigentlich disqualifiziert..
Ein Live tool.. Als solches solte es wenigstens so stabil laufen wie irgendein open source program..

Also soviele crashes wie in den letzten 2 wochen hatte ich das letzet mal in system 7.5 zeiten...also eigentlich hatte man schon vergessen das ein program einfach so crashen kann.


Wenn ich klar sagen könnte was den crash auslöst hätte ich es gemacht..das mit dem zigarette rauchen war kein humor sondern ein fakt.

irgendwas im hintergrund macht ab und an eine abfrage und dann ..peng...

Und Live 4´s splashscreen ist nur einer der punkte..es gab da noch so andren trouble das einmal falsch klicken den loop schrottet und das war nicht undo able...

Ich hab daraufhin die Finger davon gelassen und mit Live 8.03 mit weniger ärger gearbeitet..

Der versuch der sache mit euren betas auf die spur zu kommen ist daran gescheitert das die nur beim ersten start ein crashfile erzeugen und danach einfach nur noch wortlos crashen...

hier ein file das eure neue beta gerade für den letzten crash der vor beta erzeugt hat, etwas das diese nicht mehr getan hat





Ansonsten ist mein setup

MAcbook 2,1 ghz, 3 Gb ram, os x 10.5.7 , fireface 400, Ableton Live, Midipipe 1.43, Midi interfaces MT 4 emagic.. TM-1 electron..

Interfaces werden gegeneinander verschoben wegen timing.. mit midipipe wird bei bedarf ein atari eingeschleift um anständig midi editieren zu können und diverse sound expander thru mässig auf die keyboards oder externen midi sequencezer wie nord modular G2 oder doepfer maq zu legen..
Ist ja leider unmöglich das mit live alleine zu machen...

eventuelle midiloops also nur möglich wenn der atari gepatched ist und dann auch nur auf midipipe ebene und nicht im live direct..
Trotzdem hatte ich den eindruck das arbeiten mit midi die absturzrate drastisch erhöht..

Trotzdem bleibt es das Live 8 mimer irgendwann gelegentlich gecrashed ist.. beim zigarette rauchen...
Allerdings nicht im 2 stunden rhytmus.


Mir ist klar das das problem nicht durch Ableton ausgelöst sein muss.. es ist jedoch aufällig das im gleichen setup live 7 kein einziges mal gecrashed ist.. und das bei effektivem 36 stunden dauer betrieb...

Was dann doch recht deutlich auf eine inkompaiblität mit irgendwas von live 8 hinweist...

Gruss
Sven


As the answer to that they closed my case...

Hallo Sven!

Danke für das Beta-Package, ich werde es an [email protected] weiterleiten.

In Deinen Mails scheinst Du eher die Diskussion als ernsthafte technische Hilfe zu suchen. Mit ersterem können wir Dir leider nicht dienen und Deine Art zu kommunizieren befremdet uns ein wenig.

Eine detailierte Beschreibung Deines Setups und Deiner Vorgehensweise kann ich auch nach erneuter Nachfrage nicht finden und werde den Case nun, bezüglich der Aussage am Ende meiner letzten Mail, schliessen.

Gruss,
Dom Wilms
Ableton Technical Support


Dom says that he cant find a detailed enough description of my setup in the previos mail and closes the case



But they still had their bug..which turned out to be midirelated as described in my very first mail..

And the bug and fix was only anounced in public after i started a poll that showed that 50% of the mac users had similar problems.

thanks ableton for great support and keeping the us users from knowing the sad truth.

[4.33]

yeah that's great..glad you're still getting some fun out of this thread.

May i refer you to someone who posted earlier on this thread that they paid a fine to ableton to 'heal' their pc. Might be true, might not. But the 'fade out' warble I'm getting from mic-in recordings has the hall-marks of a deliberately implemented and maddening glitch, rather suspiciously occurring 1 week after the hack is activated. So I'm sure I'm not being too daft here.

Its not technically possible for Ableton to do what you claim. For one, they'd need a list off all audio interfaces in the Live code. Not to mention powers beyond asio or coreaudio. An educated guess would suggest one of the other programs on your system messed up your buffer settings or a sample rate conflict.
All the copy violation detection does in Live is tell you you've been busted and the application will stop working.

hey Bjorn, look at the extensive list of the control surfaces, it's likely that they have most of the soundcards covered as well!

i'm just glad i didn't own APC40 at that time, it would probably also be smoked

[djsandman]

"Give away the stone
Let the waters kiss and transmutate
These leaden grudges into gold " - Tool

I understand the resentment towards liam, but at this point it would probably be better for everyone if he gets his problem fixed and PAYs for Live; thus supporting the developer of the program we all love. More money for Abes = more R&D into Live = more fun toys for us in the future.

So liam, I'm guessing if the cracked version of Live did screw with your soundcard, it was probably due to some poor-written cracked code or some malicious code added to the cracked program outside of Abes. The good news is, I doubt that it did any physical damage to your card. It probably just screwed up the drivers.
So I recommend reinstalling your soundcard drivers and running a few tests (outside of your cracked version of Live). If the problem still isn't fixed, then you may need to do a clean install of windows.

[hoffman2k]

hey Bjorn, look at the extensive list of the control surfaces, it's likely that they have most of the soundcards covered as well!

But why would they? I could type a whole thing about class compliance, Asio and CoreAudio but the shorter point would be that Live in windows can't even tell a midi controller from an audio interface in that there is no device name.

[4.33]

hey Bjorn, look at the extensive list of the control surfaces, it's likely that they have most of the soundcards covered as well!

But why would they? I could type a whole thing about class compliance, Asio and CoreAudio but the shorter point would be that Live in windows can't even tell a midi controller from an audio interface in that there is no device name.

that's exactly what i'm talking about! ableton timebomb fries everything USB. thank god my nord lead is only MIDI. it is not possible to fry something via midi. it is data-only protocol.

[Tone Deft]

that's exactly what i'm talking about! ableton fries everything USB. thank god my nord lead is only MIDI. it is not possible to fry something via midi. it is data-only protocol.

that's retarded.

Ableton fries USB devices?

data only protocol?

WHAT?!?!?!? hilarious!!