MPC X & MPC Live Forum: Support and discussion for the MPC X & MPC Live, Akai's current generation of standalone MPCs.
By dylanfree Mon Dec 24, 2018 2:56 pm
Surface Pro3 i7 8GB, 512GB Win 10 64bit
Reaper DAW 64-bit
MPC X 2.3

When running MPC X in controller mode using MPC 2.3 Application, the use of system resources seems ordinary.

However, running MPC X in controller mode using MPC64.dll (2.3) as VSTi in Reaper, the use of resources goes extraordinarily high to the point of CPU thermal throttling!

I haven't seen this happen with any of my other VSTis.

The high CPU, system resource usage starts occurring the second the MPC64.dll VSTi is loaded onto a DAW track, without ANY audio activity occurring. The high CPU, system resource usage CEASES the second I the VSTi is unloaded off the DAW track.

Highly repeatable: simple open empty DAW project, create track, load MPC64.dll as VSTi on track, monitor system resources with Intel Xtreme Tuning Utility.

The plots below start with MPC64.dll already loaded on a Reaper track. I capture simply unloading MPC64.dll VSTi from the Reaper DAW track and then reloading it back onto the track. No audio is being played at all. The high activity / thermal throttling follows when MPC64.dll VSTi service is running.

Image
By Felix56 Wed Dec 26, 2018 4:48 pm
Hy,
i imported yesterday some Playbacks from the Mac Normalized 44.100 HZ and 16bit to the MPC live and
i have the same Problem. On the Mac they sound clean and on the MPC live they clip...
i thought that they are not good but on the Mac they are perfect..
So i think its a new Bug with the import conversion !!!

Felix
User avatar
By jackmate Wed Dec 26, 2018 6:30 pm
..had the same problem, with the file being -6db, but it clipped heavily...
By Frisbi Thu Dec 27, 2018 1:53 pm
Another bug I think on standalone 2.3.
Sometimes when I change the velocity of a recorded Pad on grid view, everytime I try to change the velocity of one pad on drum program it changes the velocity of all pads.
I changed the preferences, same results.
I changed the edit zone, same results.
So I guess it is a bug.
By Frisbi Thu Dec 27, 2018 1:54 pm
jackmate wrote:..had the same problem, with the file being -6db, but it clipped heavily...

Yes, its a weird behaviour.
Try to work with imported samples using -6db as unity.
This way they work fine.
By MAXTHEDOG Sun Jan 06, 2019 12:26 pm
Standalone mode, never used controller mode other than to transfer files etc. Drastic (-3dB down to -24dB) loss of output on main outputs. Power cycled to rectify. Unable to repeat. Checked all the obvious but meters on Ableton and Focusrite confirmed that the level was down. Also level meters in the Live also down from similar levels to above. Running 2.3.
Cheers.
By Al Yeska Tue Jan 08, 2019 4:05 am
I'm blessed to have none of these bugs. Whoohoo! The bug i do have in my box is the presence of snaps and pops after filter or pitch edits, requiring that i save and power off my unit. Upon returning to the project after a restart, the pops are gone and a smooth happening to my sounds is preserved.
By Lee8989 Mon Jan 14, 2019 7:13 am
MPC Live standalone.

The pads are properly sending velocity information via MIDI (ie. a soft hit = lower velocity note), but when using note repeat to record the MIDI notes, you are no longer able to smoothly vary the velocity of the notes by applying more/less pressure in real time. The recorded notes all come out recorded as a single velocity. This never occurred on previous OS versions, and is something I use a LOT for recording hi-hat patterns for external drum machines. I can't imagine this would be by design, it would go against all previous MPCs!

Hope it gets a fix in 2.4!
User avatar
By bredal187 Wed Jan 16, 2019 10:47 pm
Al Yeska wrote:I'm blessed to have none of these bugs. Whoohoo! The bug i do have in my box is the presence of snaps and pops after filter or pitch edits, requiring that i save and power off my unit. Upon returning to the project after a restart, the pops are gone and a smooth happening to my sounds is preserved.


Have the exact same issue and "solution"

Sometimes it requires a second reboot