TomViolenz wrote:I don't want to argue here, and I don't know how difficult it was to reverse engineer Mackie control in the beginning.
But this thread is over a year old.
A solution came from a user 4 days later. A solution for which he had to technically brake Abletons EULA (decompiling Lives .pyc scripts).
He was also not reverse engineering Mackie, he needed to reverse engineer Abletons work.
Now the first response from an Ableton employee comes 4! days ago, more than a year after the problem was solved by one of their users, and you think this was great work?!
I repeat: poor showing!
Firstly Tom, if you don't even own an MCU what are you even in here for stirring shit again? You haven't a clue of "how well an MCU works" with Live without actually owning one. Troll off somewhere else.
The "issues" were simple small glitches in some of the code and though a user did solve the problem Ableton have actually addressed the main issue of the channel strips not displaying data for any channel playing audio. the other small issues are not even important.
I have used a number of MCU emulated devices including a BCF1000 and an Alphatrack and both of these and my actual MCU have all worked perfectly over the last 4. With a few of us having the same issue and one user posting actual photo proof of the issue, the fixed scripts in this thread and some nice words to Ableton they addressed the issue for us which had nothing to do with the actual functionality of the MCU rather a simple glitch. Some users probably never even noticed.
I can certainly confirm if just for Abletons own knowledge that the main issue that I reported which was the ....... replacing a device parameter on a track playing audio is now fixed in the betas though this is something that is better discussed in the Beta forum but I felt as an ACTUAL user I should correct the misconceptions.