Stefan Jantschek wrote:Stromkraft wrote:
It's not enough to "start another clip on the same track". It has to (!) be a clip without the same automation. In this case pitchbend.
Wrong.
It sometimes happens even when you start the same clip again.
Obviously with the same automation (reset).
The reason could be that the pitch bend reset command sometimes does not get
recognized within a certain amount of midi stream data.
Same problem when you record a new clip.
Any missing or unrecognized pitch bend resets couln´t really called "design".
Dropped MIDI data could be a bug, yes. I've never argued anything else.
Since
I can repeat what you describe with this setup: A clip with no pitchbend after one with; and since I can
NOT repeat with your suggestion above: a clip with pitchbend after having finished a clip with pitchbend up or down, or the same clip, then
clearly!!,
your steps are indeed insufficient!!
I've been using Live 9 every day on 5 machines since 3 years, with external synths and software synths — not so many Live native ones though — and
I have never ever encountered this issue. I've encountered many other issues and have been as helpful as I can in identifying these with reproducible sets or steps, that I haver given to support and the beta team.
That does not at all mean others can't encounter this! It's preposterous for you to suggest that's what I'm saying! Maybe it's too much for you to comprehend that there can be multiple aspects to a problem that appears to be clear cut and always repeatable for you.
I have not at all suggested you or anyone else cannot have a problem with pitchbend or other automation behaving unpredictably. I suggest that what you describe are two problems (or even more), that may, or may not be, related. The fact others can't repeat this should be used as information that your instructions for reproducibility are insufficient. Would it be terrible hard work for you to make steps even I can reproduce with the same clips, or clips with pitchbend after the bend? If so, what's so hard about that?
I'd suggest one thing to do in these situations are to share sets displaying the issue in question, as well as the absence of it, with other interested users.
This way one can pinpoint all the necessary steps and share these with Ableton support. It's certainly possible this is already known, as you suggest, but
it's not on me to find this out. I don't have the problem! (other than what I acknowledged previously)
This is on you to locate, present and make known so there can be a bug case, or so that pertinent information for an existing bug case can be added, in order for there to be a chance of resolving it.
Ableton can do some things to find bugs on their own surely, and sometimes they may appear do nothing about it. In this case we can nag on them about this to fix it.
What we cannot do IMHO is to put together different issues and call them one thing, present insufficient information for others to reproduce and just whine a lot on why Ableton don't address our pet peeves.
What you need to ask yourself is whether you actually want to solve this automation problem of yours or if you want to whine about it. The choice is yours.
I'm not at all against fixing issues, but I'm not asking that Ableton fix serious issues that seemingly only I, or very few other users, have. Sometimes you need to face that if it only happens for you then it is you that need to change something, possibly in your set up or how you do things. On the odd chance sometimes it's the opposite of course. Then it's even more important to be able to make the problem happen at will or otherwise diagnose the issue. Sometimes, or typically, with the assistance of Ableton support.
All I ask is that you make an effort to make this problem
reproducible for anyone! Because if even if someone else can't reproduce, that's information you can use to refine the effort to solve the problem. In the end it's on Ableton, yes, but they can't fix what they don't know. Why not help them a little?
I suppose first step is to find the bug report at centercode, present it, so people can verify they can make the problem happen or not and also so people can vote.
I know, you rather would like to make music. I'm the same. Sometime it feels good to do what you can to contribute to a solution, however. This is a choice that we all will face sooner or later. Ableton could have a gigantic beta bug team and we would never have to get involved in these kind of issues, but likely then
Live would be quite a bit more expensive. Pick your poison.
