Rant: MPC Live Crash crash crash

CharlesRandolph wrote:
I suggest doing the following.

1. Back up all data.
2. Remove all attached devices.
3. Factory reset the device.
4. Format the hard drive as instructed
5. Reattached hard drives as instructed
6. Test to see if the bug is there. If no, continue to 7
If yes, report the bug to Akai and return the device.

7. Update the device, one update at a time. Then restart after each update.
8. Test to see if that update causes the bug. If no, do Step 7 again and continue.
If yes, report the bug to Akai and return the device.

bredal187 wrote:

CharlesRandolph wrote:
I suggest doing the following.

1. Back up all data.
2. Remove all attached devices.
3. Factory reset the device.
4. Format the hard drive as instructed
5. Reattached hard drives as instructed
6. Test to see if the bug is there. If no, continue to 7
If yes, report the bug to Akai and return the device.

7. Update the device, one update at a time. Then restart after each update.
8. Test to see if that update causes the bug. If no, do Step 7 again and continue.
If yes, report the bug to Akai and return the device.

Yeah...I'm not gonna do that. I'm not buying an overpriced unit only to spend several hours or even days to find out why it's flawed.

I get where you're headed, but the mpc live is not worth it, Imo. Sure, it runs on battery, but that's about it. No portamento, crashing often, bad effects, unable to rearrange effects, unable to rearrange tracks... I might find more to **** about in the next week or so, before I return it as a faulty machine.

Bezo wrote:Somewhat related, maybe, I had a project saved that I couldn't open. I have about 8 VSTs in it, so it takes a second. I tried 2-3 times to open it and it would get hung up loading the same VST. What worked was opening an empty project then loading the session from Recent Projects in the File menu. I then overwrote the file saved in my normal location and it opened fine the next time. Odd as they should've been the same file, but it worked.

Shorty story...

I updated my studio about 10 months ago, still fine tuning some things. I was all hardware prior, less Pro Tools & BFD plugin. I had exactly 1 issue in those 10-12 years; my new Minitaur had a known tracking issue. Including shipping, I had it back in a week.

Modernized a bit with a new controller, new drum machine & went all soft with instruments (considering bring the synths back out). Both controllers were demo units, but my Komplete Kontrol & Touch had issues and needed to be replaced. And I've had to reinstall a couple of VSTs to fix problems. I spent more time trouble shooting, fixing & replacing in the last 10 months than I did the prior 10+ years.

CharlesRandolph wrote:

Bezo wrote:Somewhat related, maybe, I had a project saved that I couldn't open. I have about 8 VSTs in it, so it takes a second. I tried 2-3 times to open it and it would get hung up loading the same VST. What worked was opening an empty project then loading the session from Recent Projects in the File menu. I then overwrote the file saved in my normal location and it opened fine the next time. Odd as they should've been the same file, but it worked.

Shorty story...

I updated my studio about 10 months ago, still fine tuning some things. I was all hardware prior, less Pro Tools & BFD plugin. I had exactly 1 issue in those 10-12 years; my new Minitaur had a known tracking issue. Including shipping, I had it back in a week.

Modernized a bit with a new controller, new drum machine & went all soft with instruments (considering bring the synths back out). Both controllers were demo units, but my Komplete Kontrol & Touch had issues and needed to be replaced. And I've had to reinstall a couple of VSTs to fix problems. I spent more time trouble shooting, fixing & replacing in the last 10 months than I did the prior 10+ years.

Updating any studio, especially when your setup is stable, can be trouble shooting nightmare. That's one reason I buy longer term pieces and it takes me time to incorporate and patch new gear into my chain. The issue with software, is if the MICROSOFT or APPLE decides to change something. It can and will break the entire setup.

This is one reason, why MAGIX, Sequoia 14 only works on windows. They could not keep up with MAC OS because apple would update and not give the DEVS, enough time to test and patch the software. Now MAGIX have customers who can't work, because the software does not work with the OS update.

Same thing goes for old hardware, that needs new Windows/MAC OS drivers. If the company stops support on the device. They should release the drivers, so those who have the machine and wants to keep using it, can. I find it strange that the MPC 4000, can be seen by window 10 machines, but the drivers are outdated.

Why can't Akai Pro just make the driver code public. Then we can fix it or they can charge a couple of dollars for an updated drivers. Nevertheless, I built Window XP SP3 just for old software. It not used for anything else and it never connected online.

Bezo wrote:I did update myself out of being able to use Ak Sys with my Akai Z4 a long while back. PITA as doing some of that stuff on the Z4's screen was a deep menu dive.

CharlesRandolph wrote:

Bezo wrote:I did update myself out of being able to use Ak Sys with my Akai Z4 a long while back. PITA as doing some of that stuff on the Z4's screen was a deep menu dive.

The ironic thing is Ak Sys works fine on Windows 10, it's the hardware drivers.

CharlesRandolph wrote:Nevertheless, I built Window XP SP3 just for old software. It not used for anything else and it never connected online.

Bezo wrote:Actually, I think I remember someone recommending a cheap PC just to run Ak Sys.

The Man Machine wrote:So the end user is the guinea pig with Akai. Even after so many FW updates.

Great thread, but no MPC for me I guess.

CharlesRandolph wrote:I don't understand how so many people are having different issues. I understand if most people are having the same problem, then it's the machine or code. But with all these different issues, on the same machine using the same software. It has to be user based.

Danoc wrote:I said this long ago. Ya think? That's why l just shut and keep working.

CharlesRandolph wrote:I don't understand how so many people are having different issues. I understand if most people are having the same problem, then it's the machine or code. But with all these different issues, on the same machine using the same software. It has to be user based.

Heavie wrote:I think it's sad, a person has to be lucky on a lottery draw when buying gear or they have to tip toe around a gear when operating it to keep it stable. Are you really suggesting, a person have to find the sweet spot to use a mpc x or the live without crashes. Unless the original poster is physical putting wear and tear on his live. Like slamming the live down or beating it with a hammer. His live should not be crashing, when performing simple functions like twisting knob, triggering pads, pressing buttons.

My God, you purchase products to use and enjoy it. NOT to trouble shoot it!! This problem is wide spread among all the brands releasing gear under inMusic. Not just Akai with the latest MPCs. The other brands under inMusic Brand are having failure problems and the same lucky people who's luck up are stating it's user error, until they get bit by the failure bug. Then the table turns and they start crying, why my unit is not working.

I agree 100%. Music production/remixing is currently a hobby for me. If my main source of income was music production then I would NOT use inMusic Brand products. The reliability & stability is just not there.

Clients don't want to hear that you couldn't finish their project due to faulty hardware or half backed, poorly implemented software. The client would tell you to use something else or they would take their project(work) elsewhere to be completed.

If Akai's desire is to cater to professionals in the music industry then their hardware/software needs to be at a professional level.

chino wrote:I agree 100%. Music production/remixing is currently a hobby for me. If my main source of income was music production then I would NOT use inMusic Brand products. The reliability & stability is just not there.

Clients don't want to hear that you couldn't finish their project due to faulty hardware or half backed, poorly implemented software. The client would tell you to use something else or they would take their project(work) elsewhere to be completed.

If Akai's desire is to cater to professionals in the music industry then their hardware/software needs to be at a professional level.

Lampdog wrote:I do this exact same thing when I wanna use 4k software.

Danoc wrote:I said this long ago. Ya think? That's why l just shut and keep working.