First steps with MPC studio - looks entirel broken/buggy

Hi,

i just got my new MPC Studio, while setting it up with my Windows 7 64bit computer it offered an MPC software update to 1.7 and a firmware update to 1.10 which i both installed.
MPC software seems to run as 32bit aplication

besides the normal MPC software install i do have "The Bank" and "809" installed - both got the updates to 1.3, which comes with the 1.7 update.

While doing my first steps with this new hard- & software i got the impression that something is horrible broken here - and i am wondering if its the studio controller itself - but let me explain it a bit more detailled.

Scenario:
I am able to load a sound from my harddrive to the MPC Software, pick a loop from that and let it play as track 1 in sequence 1.
Then i loaded a drumset from "The 809" pack.
I was then able to hit & record several drums into a second track. While hitting the pads they do lighted up for a while as expected.

But then the issues started:
I am not able anymore to record/programm additional drums via the controller itself (no sound, no light ...nothing) - while it does work using the mouse inside the software.
So - the existing/programmed sound is still playing - but it seems like no button-press on the controller gets interpreted at all
If i do restart the controller - while letting the MPC Software itselfrunning - it seems like the problem gets temporaly fixed (for some seconds or minutes) and then returns to the old problem.

Imagine i was restarting the controller each 1-3 minutes to be able to work via its pads.

Sometimes i had to restart the controller twice in a row - as the display just didnt display the expected informations on first restart.

Is that a known issue in general?
for me it feels like i dont have real issues with the MPC software itself - like many others seem to have - but instead with the Studio controller itself. Or am i interpreting it wrong here?

I am wondering if my setup is bad, or if the controller i bought is just a buggy one which i should return or whatever else i can/should do.

The studio itself seems like a great device / combination for me - if it would work without being in need to restart it all 1-3 minutes.

any tips/hints are heavily appreciated.
are there some kind of error/log files i should take a look on?

greetings
fidel

Is it plugged directly into a USB port on the computer, not through a USB hub?

Do you have a choice of USB2 or USB3 ports on your computer? If so, try a USB2 port.

hi,

first of all - thanks for the quick reply & sorry that i forgot to mention the usb-setup.

Yes - the Studio is connected directly to the computer - i am aware that usb-hubs might cause nasty effect. According to USBView i do have only usb3 connectors - so i cant really test using an onbaord v2-port.

Is usb-v3 a possible issue?

USB3 is an issue with the MPC Renaissance built-in audio interface.

Not sure if it is also an issue with the MPC Studio connection, just suggested it to see if it makes any difference.

Maybe try a different USB cable if you have one, and maybe try a different USB port.

You could also see if it is possible to disable USB3 in your computer bios, to force the ports to run as USB2, if you have that option, just to see if it makes any difference.

how do you even know which port is usb2/3?

@topic:
- i tried using an usb extension cable -> without success
- tried using a usb 2.0 hub -> no success
- disabling usb in bios is not an option in my dell xps 15 setup
- disabling power-savings option in device-driver seems to not help so far

right now i reached a point where it is working for the first time longer then 10 minutes.
this might be the result after replacing the entire usb-3.0 device driver with an older version.
I have to check if that state is now persistant or not.

i let you know how it develops



@pituchez:
there are several options to check that.
1) on some boards usb 3 ports are colored differently - usually blue or yellow. but this is an unsafe method.

2) personaly i would check in device manager and combine that with the usage of Microsofts USBView application - which is typically used to debug usb-issues.

ahh..yea one of mine is blue.

thx