scutheotaku wrote:whatever (these word games on what it is are kind of silly), so there's not much else any of us can do. If it really does effect your (by "your" and "you" I don't mean Tone Deft, I mean the OP and "supporters") music, then I'd suggest using another DAW until this is fixed in Live (if it ever is). If you'd like a recommendation for free DAWs that are good, I'd be happy to oblige
They're not games. Words are very important. There is a big difference between a mistake and a decision. I can't believe I have to explain this to you.
Do you think I haven't considered this? Surely I don't have to explain the consequences of time spent developing workflow in another DAW? Which would especially be a waste if six months from now Ableton finish fixing the problem and Live becomes usable.
Tone Deft wrote:I take that as a conspiracy. conspiring to put out the bare minimum features and call it done.
Seriously. Look at the rest of the definition. The word is overblown. It's full of bias. You know as well as I do that it's often used ad hominem to discredit the point someone is trying to make. I think it's a word best avoided.
Tone Deft wrote:I wrote a software feature (funny enough, an audio delay buffer) that I thought I had tested, I asked someone else to test, we missed it, the QC group missed it and finally a customer found it 7 months after we shipped product. it was a big oversight.
This is a little different to a team working on a project for 10 years though.
Tone Deft wrote:have you ever been involved in software development?
No. But it doesn't take much intelligence to understand the process and how mistakes can be missed. I have considered it.
Tone Deft wrote:you want to say they're bad at DAW design
Actually, no I didn't. If I wanted to say that I would have. I say they made a conscious design decision. I've already stated how superior Live is to Logic in many ways. They're fantastic at DAW design.
Tone Deft wrote: LOL!! at this point we're not going anywhere with this.
Yep I don't know if we are getting anywhere per se. I think I'm close to getting where I wanted to go. I got the problem out in the open. It's up to Ableton to respond. I'm not counting on it. I just don't think there's anything you can explain about software development that will help me understand where Ableton is at with this.
Tone Deft wrote:and mad mofo-ing props to ninox_rufa for finding this and Khazul and others for analyzing what's going on.
Thanks. I just wish Ableton would shed some light on the situation so I can make an informed decision. If they have no plans to fix it or it's gonna take 12+ months I'll accept the losses and move to Logic. Just need to know.
In the end it doesn't really matter if was a decision or a mistake. I just wish they'd let me know where they stand.