2.14 & 2.15 Bug reports

does not seem to work here either

I uncovered what appears to be pretty serious issue over the weekend. I was processing some breaks, chopping, etc. I started noticing that every time I used either the bounce as sample, or flatten pad, or export, Akai (both MPC Live and Force) add about 1 millisecond of silence to the beginning of the sample. So basically, if I'm processing something multiple times and resampling it, it could be off by up to 10-20 millisecond WTF
Clearly this could be a pretty big problem figuring pretty much all of the music I've made on either machine is going to be slightly 'off' in one way or another.
I've been in some FB groups etc where others have confirmed the same.
Wondering if this is a known thing as I've not been able to find much online about it.
Really bumming me out. Not only does it render my Akai stuff basically useless for what I need it for, it makes me figure that all of the music I've made on them, most importantly drum and break bounces, are all shifted to the right a bit. Really hope this is able to reach devs at Akai because I'd imagine it make a lot of ppl feel the same about using their stuff for anything that requires the type of accuracy that they are sold to deliver on lol

2.15
MacBook Air (M1, 2020)
Monterey 12.6
*MPC Stem Separation
*Jura
*Ring The Alarm
*Flex Beat

All Akai/AIR plugins fail/require activation. Activation - shown as successful in both inMusic Software Center and MPC-Preferences-Activations - fails to activate. Promoted for activation again within each plugin, these activations fail as "error retrieving user details".

Tech Support solution: roll back to 2.14 for now, will escalate.
Escalated Tech Support: glad 2.14 activations is working, ticket closed!

The activation issue in Standalone - MPC X - is intermittent, as it always was for me in the last several releases. Tech Support recommendation there was to also roll back to 2.14 so it will match MPC Software.

when you copy events (from MAIN, SEQUENCE pencil) the name of the track is not copied over to the new sequence (if you use replace, i can understand they don't 'overwrite' the name when you choose merge)

wavejockey wrote:when you copy events (from MAIN, SEQUENCE pencil) the name of the track is not copied over to the new sequence

That's because it's copy events, not copy track. I think it's always been like that, even on legacy MPCs hasn't it?

i guess you are correct