dom wrote:The first statement is right, just as Alex wrote in the announcement.
No, he did not. He just wrote that "display" was fixed, which in contrast to the
real fix is a minor cosmetic one. I added the more important unannounced fixes that are related to the mentioned fix.
The second, however, was made up by yourself.
No, it is not, you are just too ignorant and stubborn to check the evidence and your own reality. It doesn't matter anymore, because the latest Beta shows a whole different playback behavior now.
As i already mentioned in another thread: Live does not and was never playing using a rounded tempo.
Whatever it does, the output of audio clips playing at non-integer slave tempi sounds very obviously different to integer tempi upto 7.0.12b
1. With 12b
2 the playback behavior changed! This is
not a simple change of Live's tempo display. I still can prove my reports by audio examples.
You are either lying and discrediting me or lacking knowledge of what your own application is doing while ignoring the possibility and evidence of potential errors that are presented to you!
It only was displaying a rounded tempo and was communicating this rounded tempo to plugins - the latter was obviously a bug and was fixed now.
For such an "obvious" bug and your repeated bragging about how detailed your inhouse testing of the Midi engine was I wonder why you never noticed it yourself and had me do your work again?
As i already asked you several times: Please, with sugar on top, stop confusing people with cooked up statements.
No need for sugar, you keep thinking your software is running by the "specs" and ignore any evidence for potential errors as long as it is not at least blantantly easy and obvious to understand.
This time you reached a new level by even making up bugfix statements that Alex never wrote.
That's just cheeky, bad for other people and even damaging your own credibility.
Excuse me? I quoted Alex' announcement under his name and added my own findings under my own name. Alex moved the post into its own thread and even wrote me a PM about it. He did not mention anything about me making up statements in his name.
Like before you are beginning to spam my content and topic related thread with accusations. Please stay on topic. If you think I am wrong then argue on the basis of the material I provide (screenshots, rendered audio samples, Live sets, videos) or provide your own material.
Can't confirm or deny this yet, but we will investigate.
Nice, last time you were too busy with calling me things and ignored that part of my report completely. I guess alot of Ableton Live users will be very grateful if you finally fix Live's Midi Sync Slave behavior.
It makes no sense to try judging midi clock sync using phase tests and we will not investigate this further.
Could please someone with more sense take over here? Not only did I provide animated screenshots that prove Live 12b2's
jumpy tempo response visually while also offering audio examples, but claiming that phase tests are senseless when trying to judge tempo(-stability) related issues is such a #!§$& statement that I can only repeat publically what I wrote in an email before: Shame on you, Ableton!
Besides that the aim of the tests was not phasing, but timely playback. The phasing happens on its own whenever Live behaves erratic. It is just
one way to make the problems audible in order to understand them. But now you are gonna tell me that audio producers, musicians and engineers don't care for unexpected audible phasing sound!? Sorry, no bonus!
