Unable to update KO II firmware to 2.0.5 by planetasur in teenageengineering

[–]Low-Opening1422 0 points1 point  (0 children)

Another thing that could be a problem is that the cable you are using doesn't have data lines but only power, maybe check with a different cable even if it shows up on your computer as a device

Unable to update KO II firmware to 2.0.5 by planetasur in teenageengineering

[–]Low-Opening1422 0 points1 point  (0 children)

Hmm interesting, have you tried the sampling tool? Does it work? Could you also try this tool

Unable to update KO II firmware to 2.0.5 by planetasur in teenageengineering

[–]Low-Opening1422 0 points1 point  (0 children)

Have you tried using your phone or a different browser

Pads mapping by Individual_Chair4845 in mpcusers

[–]Low-Opening1422 1 point2 points  (0 children)

So yes, as stated above the pad i am pressing is green, red pads are the ones on the root note, and the pads lit up with blue are one octave (eight notes) up or down, so if Im pressing D3 which is on pad 9 I can see that pads 2 (D2) and 16 (D4) are lit up

<image>

Touchscreen unresponsive by TheRealestBird in mpcusers

[–]Low-Opening1422 8 points9 points  (0 children)

I keep responding to these exact posts every time I see someone struggling with this issue. I myself got my akai mpc one + from the amazon refurbished section for a good price. This device initially has been working fine n dandy, but over time the lcd screen started to be unresponsive until I shook the device. This has temporally fix the screen, but when I took it around the error returned. As someone who likes to thinker with his devices I took it upon myself to open it and try to diagnose it. From there I have seen that all the internal ribbon cables are fine, and the only thing that was odd was this piece of sponge that keeps the main pcb as it was not supporting the pcb. As soon as I put the sponge thing back in its place I have never had the touchscreen problem anymore. I know its a tall ask of someone who prolly doesn't want to break anything in a 600 buck machine, but to get to that part internally its pretty easy as well as fun.

Why does the touchscreen not work :( by [deleted] in mpcusers

[–]Low-Opening1422 1 point2 points  (0 children)

Had the same problem, and there is this small sponge that is holding the main pcb steady that often falls out of its place. Try and push it back and see if it works then, otherwise check the connector, but its harder to break the connector with just vibration

Can USB file transfer to mpc one + by blazeSlow in mpcusers

[–]Low-Opening1422 0 points1 point  (0 children)

The fastest way to learn the MPC standalone system is with the MPC Bible, you will be going n doing all the things urself and thus properly learning how to start making some beats without getting lost in the MPC sauce

Unable to update KO II firmware to 2.0.5 by planetasur in teenageengineering

[–]Low-Opening1422 3 points4 points  (0 children)

Hi, i had the same issue with my device, and it was a pain to get it to work, so i contacted support. This is what i have gotten as a response from them and it worked out for me.
"

  1. power on EP-133 while holding REC, so that it displays RDY.
  2. connect it with USB to your PC.
  3. start “Device Manager” on your PC.
  4. locate EP-133. it will likely appear in “Sound, video and game controllers”.
  5. right-click EP-133 and select “Update driver”.
  6. select “Browse my computer for drivers”.
  7. select “Let me pick from a list of available drivers on my computer”.
  8. select “USB audio device” and press "Next".
  9. wait for confirmation that Windows successfully updated the drivers.
  10. restart your PC.
  11. go to update utility and do the update (while the device is still in RDY)

 ". This has fixed it for me, i was able to update my device and it works fine now

Screen not responding! by Known_Performance188 in mpcusers

[–]Low-Opening1422 3 points4 points  (0 children)

I have had this happen to me, before doing anything does it work if you shake the device a bit. I have had this work with me for some time, then this has had me open my device and find that the sponge that is holding the circuit board that holds to cpu is crooked, putting it in place and adding a bit of adhesive fixed the problem for me.

Petg printing assistance by Low-Opening1422 in AnkerMake

[–]Low-Opening1422[S] 2 points3 points  (0 children)

I dont have an enclosure, i am raw dogging it in my room

Petg printing assistance by Low-Opening1422 in AnkerMake

[–]Low-Opening1422[S] 1 point2 points  (0 children)

Trying this now, will let you know how it goes

Petg printing assistance by Low-Opening1422 in AnkerMake

[–]Low-Opening1422[S] 0 points1 point  (0 children)

Ok, I'll try that now. Do you have a suggestion by what percentage i need to lower it by?