HAD IT with Akai -- ditching the 5k before I hurt someone.

I won't be hangin around these boards anymore.

It's been "fun" for these last 2 months trying to get the MPC to work properly CONSISTENTLY. Namely, I'm having issues with the box zero'ing out note durations at random -- I've tried every fix, option and solution and have come to the conclusion that the OS programming is simply too amateurish and negligibly supported at best. I'm also not fond of how Akai handles support secretly rather than doing so on a public forum. They state that this creates diluted answers...not like the diluted answers you get from directly, mind you. Also...watch out for their super slow responses...they'll make you go beyond your return period if not careful.

Thanks for making my time here as pleasant as it can be for someone who fell for the 2k rip-off. I'm not going to be like most...I'm going to blatantly admit it: I got had by Akai.

Anyway, I'm going to wait awhile and then hopefully find some sucker on Ebay who doesn't have a clue about how bug-riddled the OS actually is.

hayoo

What exactly was your problem with the Os?

2 month's is not enough time to master a Mpc of any kind!

We all know that Nukai has horrible customer support, but i honestly think you did not give yourself enough time with the 5000

Rome wasn't built in a Day

picalo32 wrote:What exactly was your problem with the Os?

2 month's is not enough time to master a Mpc of any kind!

We all know that Nukai has horrible customer support, but i honestly think you did not give yourself enough time with the 5000

Rome wasn't built in a Day

Saving does not preserve ALL the note durations. No matter how it's saved...once this problem gets its hooks into a song, the piece is done for. Save it once and some random notes are set to zero duration; save it again, different random notes (on top of the others that were previously zero'd) are now zero'd. Zero duration = no sound for those particular notes. This isn't a saving issue... this is an OS bug. Akai is clueless, but I'm not the only one to experience this error. This has nothing to do with RTFM. How much time would you consider using a faulty piece of equipment "enough" before wising up...?

Look, I'm not looking to have the box mastered in 2 months...however, I DO expect that the box will not leave me wondering each time I save: "Are all the notes going to be intact when I reload?"

This is not an RTFM issue. This is an error that appears (seemingly) at random, but cannot be fixed once it affects a song...no amount of re-editing my notes, re-saving by all the means we have...nothing can "fix" the track once a "zero" has been saved as a duration...that note will NEVER play again in the sequence unless you load the song, edit the note, then play it. Saving the song (re-edited) does not fix the note...it remains at zero duration.

I meant no disrespect to you, did you post this problem before, maybe other folks will know about it and a way around it.

I didn't take your reply with disrespect.

I've posted a dedicated thread,... as well as saw another thread regarding "dropped notes" (which was the same problem). There are no solutions offered. Akai's sole solution is to reinstall reset the machine, reinstall OS2, reformat my drive. I did all that...and it actually did SEEM to work for awhile (a couple weeks) so I thought the problem was solved. I was then saving on a CF card, so I thought maybe that had something to do with it. Nope. No sooner than I suggested that "fix" to a person here on this board, my latest song shit the bed (after 36 hours of meticulous step editing...cumulative hours, not consecutive hours)...

More zero's than I've ever seen yet...and that's the last straw. Akai already ripped me on the box... I can't let them rape my valuable time and energy, too!

look i can see you frustration, u wont get what you paid for outta of it, all technology these days sucks at first, i'd give some time eventually they will get the os right, all mp's had bugs at some

* some point in the begining, its not the machine its nukai rushing it out before it was properlly tested for a quick profit

FrankieMonroe wrote:look i can see you frustration, u wont get what you paid for outta of it, all technology these days sucks at first, i'd give some time eventually they will get the os right, all mp's had bugs at some

You think? Akai is under the impression that the OS is stable. Everybody is complaining on fora Akai wants nothing to do with.

Send your complains directly to Akai.

FrankieMonroe wrote:look i can see you frustration, u wont get what you paid for outta of it, all technology these days sucks at first, i'd give some time eventually they will get the os right, all mp's had bugs at some

I wouldn't expect to get what I paid for it. I'm realistic. I can accept SOME bugs...and I have...the same bugs everyone else swallowed. How old is the 5k now? And OS2?

Akai is slow at fixing bugs when they DO know what the issue is; I can't expect they'll be even that "fast" at addressing a bug that only a couple of people can randomly reproduce.

Bottom line, if there's workarounds, I can deal with bugs. If I'm actually losing work, I cannot.

FrankieMonroe wrote:* some point in the begining, its not the machine its nukai rushing it out before it was properlly tested for a quick profit

I agree. And Akai will never get a dime out of me again.

CoinUp! wrote:

FrankieMonroe wrote:look i can see you frustration, u wont get what you paid for outta of it, all technology these days sucks at first, i'd give some time eventually they will get the os right, all mp's had bugs at some

You think? Akai is under the impression that the OS is stable. Everybody is complaining on fora Akai wants nothing to do with.

Send your complains directly to Akai.

I did send my complaints directly to Akai. Their foot-dragging is what caused my 45 day return period to expire. I dicked around back and forth with them while they gave me the same answer in different words each time: reset, reinstall....reset, reinstall...reset, reinstall. Because I cannot produce this error on-command, they feel that I am the error. ****'em...I've already given them enough "free work" and "free money".

Hi i have the same bug
in one bar if you have the same note twice and they are conected it will go to ziro on load.
but if instead of 2880 when you triger after same note 960 . if will change the note length to 2875 the poblem solved...
its suckes but that the way it is for now....

I doubt akai will ever release a new update for any mpc, espescially the 5000.

We have 4 5ks in my studio. I have only seen this at random of you don't name the program prior to saving. I then use save entire memory to hdd and cf card as well as a back up folder on computer.. just to be safe. I also write a build sheet with pad number sample that for a to pad level and settings on tune and level just incase. Give it some time man, the 5k is a lot to take in. Did you hit up the support forum? I hope you get through it man. Gear is always going to need some dozing now and then. I just spent $600.00 fixing my firewire.

yonibregman wrote:Hi i have the same bug
in one bar if you have the same note twice and they are conected it will go to ziro on load.
but if instead of 2880 when you triger after same note 960 . if will change the note length to 2875 the poblem solved...
its suckes but that the way it is for now....

I've read your reply quite a few times, but can't quite make sense out of it. If you have a viable workaround, I'm totally willing to use it.

So, when you say that "if you have the same note twice and they are connected" what do you mean by connected? Do you mean that they are connected audibly (first note overlaps subsequent note) or do you mean that they "touch" (sit next to one another) when looking at them in a STEP edit?

I don't understand your fix... would you mind trying again?

I appreciate your jumping on the thread, thanks.