Is this a bug? Known issue? I'm not super proficient with MI

yeah - it def looks like automation, but it is not! First thing I did was wonder how in the heck I recorded a bunch of wacky automation, but looking at my tracks, there was none!

proofofghosts wrote:And just to illustrate that this isn't a processing power issue - assigning filter Cutoff to inserts on subgroups or on the master channel works smoothly as you would expect when assigning that parameter to a project level q link (except that these assignments don't save at power off)

So yeah, weird behavior. It looks and acts like you would expect a daw to behave when it is maxing out its cpu or ram, but of course this isn't the case (or maybe somehow assigning knobs with Midi learn does in fact require more processing power than I would have thought??)

Have you checked the CPU meter on the MPC when this is happening to see if it's tapping out?

definitely a bug i my opinion.

i am trying to set up my launchcontrol xl for a liveset to control various midi parameters in my 1 week old mpc one and i have huge problems with it.

when i set a fader to control midi track 1 volume , its starting to jump around and then the mpc crashes.
it also somehow triggers the pad a1 when im moving the fader up, i think its not suppose to do that because its a midi cc value.

Discovered the same issue! -- when mapping akai midimix controller to program inserts...values jump all around. BUT as jabberwalky mentioned, seems to only be an issue with previous projects, created with an older firmware. New projects are working correctly (currently running MPC 2.11..

Hey guys im having almost the same issue as mentioned in several of the comments and the main thread. Im trying to midi map filter cuttoffs to my NOVATION LAUNCHCONTROL XL and the values start jumping around and everything gets buggy. Im on version 2.12.2 (latest as of now).

Anyone discovered any fix or workaround?
Thanks

I had exactly the same problem yesterday when making a template.
I was mapping the track MIDI volume.
At first I thought I had accidentally recorded automation.

I was using controller mode on win 10 and the software stopped responding a few times.

I cleared everything, restarted everything and when I mapped exactly the same thing again it was fine!!!!........ Dunno.

Cheers all

Something is terribly buggy in the MPC MIDI mapping area! I've regularly have it change my mappings which I've been using mid session. If it changes it from being a ABS controller to a relative controller then you'll get the weird jumping values, which I had along with setting to Off, changing output parameter it's controlling, even changing what type of channel (eg from subgroup to return) it's controlling a parameter on. And this is before I get into how often that page just crashes or freezes for what seems no reason....