Getsatisfaction.com...

tmpc wrote:There is too much for me to say concerning all of these comments, but as you all seem to have a very "it's all good" attitude towards these issues, I won't bother. However, none of you seems to understand the value of negative feedback . . . especially public negative feedback. I used to send Akai bug reports and private feedback; nothing ever came of any of it. But, I'm sure Akai reads this forum. Let the pile on begin!

Keep sending the bug reports.
Stop the psycho ex girlfriend talk here.

Thanks

bees80 wrote:Perhaps a seperate forum for bugs and complaints for the MPC 2.0 software and products.

And normal people who want to talk about pussy and shit (like me), can just do it on the main forum.

MPC HALP!!!

Don't worry. I'm done. The red pills are over there.

tmpc wrote:Preaching to the choir. I do that with all software, including operating systems. Due to my caution, I got through the Touch/DisplayLink/High Sierra cluster F without a scratch. But as an example of what I'm talking about, I recently decided to move to Mojave and MPC 2.8 to hopefully get past some very annoying bugs. In short, it was a disaster. Flaky and buggy as hell. So, I went back to what had worked for me before; El Capitan and MPC 2.2.1. The only problem was I still had the crazy bar numbering problem. Do you know about this one? If you make music with a lot of odd and changing time signatures, it wacks out the bar count. Thankfully, I found that MPC 2.4 fixed that. So far so good . . . but it's pretty damn pathetic.

I don't have that issues with the MPC 4000. I stay away from the MPC Touch and all it's glory. Especially on MAC.

tmpc wrote:Really? Let's see, the equipment is portable, and you can write code at home, in bed, in your PJs, with your bunny slippers on. Sorry man, the pandemic is no excuse for not fixing bugs.

If they're not getting paid, they're not coding anything. You guys enjoy, I suppose to be practicing. LOGGING OUT!