Ableton Forum

Timur wrote:

Tone Deft wrote:Ableton doesn't have to tell you a thing. you are not special. I'm sure they appreciate your bug reports but they are not your own personal development team.

Hm, wait a minute. Isn't that what "support" is meant to be about? You call them, tell them that you've got a problem and then they either tell you that it is a problem of your setup/system or a problem of their product.

show me an example. this is bullshit. you're into software, right? have you ever been part of a software development team in a job?

the problem is that Ableton is all lovey dovey with the user base which somehow makes you feel empowered. I love their feedback but you have no clue what's going on in their offices. it's in their best interest to tell you nothing but listen carefully.

I have learned (from b0unce and sliced bread) that persistant badgering about bugs and features can accelerate development. how about this? post more about the bugs and less about yourself.

Hm, you mean I post too little about bugs? Sorry, my fault then.

Timur wrote:Hm, you mean I post too little about bugs? Sorry, my fault then.

it's the draaaaaaammmmaaaaaa...

Here is a screenshot reminder for you:



I'm stopped doing the videos though, too little feedback for too much work.

I have no idea how to interpret that screen shot, I hate computers.

I have no doubt you're a great tester, I've read some detailed software geekshit from you. so, is there a debug method you can teach the rest of the class?

mad respect to you Eurogoons who are bilingual down to your OS!! that's crazy.

Hehe, that Task-Manager window is using german, but Sysinternals Process Explorer is english only.

I'm also getting into telling people what to and not to post, not cool.

http://www.youtube.com/watch?v=POl4vFp- ... re=related <-- I don't like mondays

Tone Deft wrote: I have no idea how to interpret that screen shot, I hate computers.

I am sure Ableton's developers do. Generally they seem to be quite talented and knowing about how things work.

I have no doubt you're a great tester, I've read some detailed software geekshit from you. so, is there a debug method you can teach the rest of the class?

Hm, lots of trying and most important, know what's going on with your system. Be curious and creative, just what you'd expect from an artist anyway.

dear tumor,

i have thought long and hard about how to say this, so a mastermind such as yourself can understand a simpleton like me...

i would rather come to the forum and see 50 threads complaining about the porn, or off topic complaints, then read one more word from you, complaining about live. i respect a lot of people here, for various reasons, but you are not one of them. have you ever said 1 good word about live? you are not even worth yelling at, or cursing.
you might be the one person i would troll block. no software is perfect, with all your knowledge of computers, why not write your own program, since live is so horrible?

peace,

d.

Timur wrote:

Tone Deft wrote: I have no idea how to interpret that screen shot, I hate computers.

I am sure Ableton's developers do. Generally they seem to be quite talented and knowing about how things work.

well played. yep, all about billable hours. damn, you never know what kind of talent people up in here have.

Timur's a character, can't deny that.

dcease wrote:have you ever said 1 good word about live?

Sure, even lots, and I've helped several people on the forum to get their Live going and make it a better experience. Like everyone here I love Session view for what it is, a unique expressive tool for being creative on a more intuitive level than with classic arrangement views of other DAWs. Add to that a bunch of really nice effects and superior routing options (I love that freedom).

Nevertheless love for a concept and artistic expression doesn't help much when a whole list of ugly bugs strike deep at both your personal workflow and the fundamentals of production crafts. When both Midi Clock timing and VST timing (which controls my beat machine) are fluctating so that both are even less reliable than an old half-broken tape-machine and after more than two months (in the latter case) I'm still waiting for an acknowledgement wether this is to be considered a bug of Live or not then I'd like to think another reminder is due.

no software is perfect, with all your knowledge of computers, why not write your own program, since live is so horrible?

1. Because I cannot code and don't have time to learn it. I want to make music.
2. Because I pay Ableton and others to code their software properly.

...then read one more word from you...

You should not ask questions then, mostly these lead to more words being written in form of an answer.

I think I know how to interpret that screen. I see icons for reaper and pure data. I get the impression that you don't even need to rely on live for what you intend to do, with your talents.

Hehe, that screen was meant to remind Tone Deft that not only do I provide lots of bug reports (that's what he asked for), but also among the most in-deep and technically most well documented ones you can find around, including such features as audio and video footage plus system informations downto what each single kernel-thread of Live and the rest of my system is doing (that screenshot was done at the very moment that Live crashed/hang after closing it and stayed in memory, so you can see I'm caring for other people's problems, too ). Should anyone acuse me of spending too little time and effort, providing too little useable informations and simply shouting shit when it comes to Live issues, I don't think so.

Because I cannot code

PEOPLE WHO CAN'T CODE ARE DONKEYS
explanation: I can. enough explanation

I've helped several people on the forum to get their Live going and make it a better experience

Timur helped me with setting my monitors and explaining a bit about the background of how the db settings where to be read

Well, ok, I lied! I can code Assembler on Motorola 68000 (Amiga, at least I could back then), the very basics of X86 Assembler (long time ago when I still had a 386er), some basics of Java and C/C++, C64 Basic (plus some basics of Assembler) and some other Basic variants (just basics, pun intented). So fortunately I'm no donkey.