The Official 2.7 Bug Thread

Support and discussion for all of Akai’s modern standalone MPCs including the MPC X / X SE, MPC Live 1, 2 & 3, MPC One / One+, MPC Key 37/61.
 Reply Share on Facebook
User avatar

Re: The Official 2.7 Bug Thread

By zangetsu01 Mon Dec 23, 2019 7:38 am
Can anyone try to replicate the following in controller mode??




To replicate the problem:

Load an sample such as a hihat into a program and set the output for that sample to be submix 1. Go to the submixer and verify that the sample is indeed routed to submix 1 by hiting the pad.

Now load Mother Ducker input into submix 2. Verify that submix 1 is still okay simply by hitting the pad again. All should be okay at this moment.

Now load Mother Ducker (not the input) into submix 3. Boom submix 1 will stop working the hihat will be redirected to the main stereo output 1/2.

*Not that it really matters anymore because right now I’m tracking out 32 tracks to Studio One straight from the MPC software without the use of any cables.. Everything is done virtualy in the software with the use of Jack Audio Connection Software :smoker:

Re: The Official 2.7 Bug Thread

By c-real Mon Dec 23, 2019 8:04 am
Someone here should try to reproduce this bug and post it in the beta release forum in order to get it fixed in the next update.

So you can send 32 audio outs from your MPCX to your computer via wifi? This is interesting. How do you achieve this exactly?
User avatar

Re: The Official 2.7 Bug Thread

By zangetsu01 Mon Dec 23, 2019 10:46 am
c-real wrote:Someone here should try to reproduce this bug and post it in the beta release forum in order to get it fixed in the next update.

So you can send 32 audio outs from your MPCX to your computer via wifi? This is interesting. How do you achieve this exactly?


No you don’t have to to this over wifi if both daws are on the same PC.. its via a program called: jack audio connection kit.

It will act like an Asio driver in your Daw and you can rewire as many virtual outputs to any program you want. (Mind you this all done in controller mode)

Took me while to get the hang of it but it works.. :nod:

Re: The Official 2.7 Bug Thread

By c-real Mon Dec 23, 2019 11:23 am
zangetsu01 wrote:
c-real wrote:Someone here should try to reproduce this bug and post it in the beta release forum in order to get it fixed in the next update.

So you can send 32 audio outs from your MPCX to your computer via wifi? This is interesting. How do you achieve this exactly?


No you don’t have to to this over wifi if both daws are on the same PC.. its via a program called: jack audio connection kit.

It will act like an Asio driver in your Daw and you can rewire as many virtual outputs to any program you want. (Mind you this all done in controller mode)

Took me while to get the hang of it but it works.. :nod:


Okay I see. Thanks for clarifying (I misunderstood your "without the use of any cables"). So Jack Audio works as the ReaRoute ASIO driver provided by Cockos Reaper if I understand correctly.
User avatar

Re: The Official 2.7 Bug Thread

By zangetsu01 Mon Dec 23, 2019 11:33 am
c-real wrote:
Okay I see. Thanks for clarifying (I misunderstood your "without the use of any cables"). So Jack Audio works as the ReaRoute ASIO driver provided by Cockos Reaper if I understand correctly.


Yes instead of choosing your standard Asio driver you choose the Jack Audio router in your daw.

Re: The Official 2.7 Bug Thread

By Fess Mon Dec 23, 2019 11:40 pm
MPC-Tutor wrote:
Fess wrote:Threshold parameter doesn't work on stereo samples in Chop Mode using version 2.7. Mono samples seem to be okay when tested with 2.7 however. Sample in both cases was approx 2.5 min. Posted to Akai forum.


Could you elaborate on what you mean by the 'threshold' parameter not working? Do you mean 'threshold' mode just doesn't detect any peaks no matter what setting (i.e. zero slices at all settings), or do you mean threshold initially detects multiple peaks but adjusting the 'threshold' parameter doesn't discover more peaks?

BTW, did you actually mean 2.5 minutes? Threshold chopping isn't particularly suitable for samples that long, for a start it can only detect 128 slices max.



hey man, Akai support got back to me and said they tested it with a 3 min sample and it worked- then i tried and it now works. **** knows man, maybe a reboot fixed it.
But anyway, It was in chop mode and i chose the threshold parameter. Earlier it worked with a mono sample, but when first trying it with a stereo sample it didn't, and now it does. I wasn't drunk or high lol btw.
Well, it's working now. If it happens again, I'll let ya know.

On another note, auto-sampling doesn't seem to work well at all. I set the range from C1 to F5 in a Kontakt instrument (drumkit spread across the VST keyboard)and no matter what setting I chose it always grabbed only a snippit of each key (drum sound). Tried multiple settings and it didn't change the outcome at all.

Have you tried it?
User avatar

Re: The Official 2.7 Bug Thread

By zangetsu01 Fri Dec 27, 2019 10:16 pm
New bug:

Bet this going to piss of a lot of Joe's

In program edit it is impossible to have the start point of a sample to be independent of the loop point.
For example: Start sample = 250 and loop sample = 19855

When you start to turn your Qlink to adjust the start sample to 300 loop sample also goes to 300. :WTF:

In sample edit it still works.

If you've got a saved program (pre 2.7) where it still worked "Dont Mess With It..!!"

Once you've saved you can't get it back to normal.

*Edit: You can get it back to normal if you load the program into notepad and adjust the start and loop points over there.
User avatar

Re: The Official 2.7 Bug Thread

By Monotremata Sat Dec 28, 2019 8:07 am
zangetsu01 wrote:New bug:

Bet this going to piss of a lot of Joe's

In program edit it is impossible to have the start point of a sample to be independent of the loop point.
For example: Start sample = 250 and loop sample = 19855

When you start to turn your Qlink to adjust the start sample to 300 loop sample also goes to 300. :WTF:

In sample edit it still works.

If you've got a saved program (pre 2.7) where it still worked "Dont Mess With It..!!"

Once you've saved you can't get it back to normal.

*Edit: You can get it back to normal if you load the program into notepad and adjust the start and loop points over there.



Just did it on three separate tracks.. Loop and start are completely independent here in both Program Mode and Sample Edit. Did you make sure you turned off Loop Lock in Sample Edit before you tried changing the Program? If both Start and Loop are set to 0 and you move Start to 300, of course its going to move Loop with it. The Loop cant start before the sample does.
User avatar

Re: The Official 2.7 Bug Thread

By zangetsu01 Sat Dec 28, 2019 8:22 am
Monotremata wrote:

Just did it on three separate tracks.. Loop and start are completely independent here in both Program Mode and Sample Edit. Did you make sure you turned off Loop Lock in Sample Edit before you tried changing the Program? If both Start and Loop are set to 0 and you move Start to 300, of course its going to move Loop with it. The Loop cant start before the sample does.



Bro thanks for helping out.. This was a users error on my part. loop lock was enabled. :Sigh:
User avatar

Re: The Official 2.7 Bug Thread

By Monotremata Sat Dec 28, 2019 5:38 pm
zangetsu01 wrote:Bro thanks for helping out.. This was a users error on my part. loop lock was enabled. :Sigh:


Haha yeah I figured thats what you did. I had it turned off when I first did it, and went back in and re-enabled it to check. I still think its weird, you can set a completely separate loop for a sample in the Program Editor, but you cant disable Loop Lock or turn on 0 Snap there. WTF Akai? I never even knew you COULD set a new loop up specific to the program. When I first started with it, before I really got the time stretch stuff down, I **** up a bunch of my samples cutting them funny to make them fit the program. I could've just edited my loops in Program Edit and left the raw sample alone.

Ill have to check the submix thing later today (the misses is still sleeping in here so no monitors on yet haha). I don't really use em but I might one day!
User avatar

Re: The Official 2.7 Bug Thread

By zangetsu01 Sat Dec 28, 2019 9:44 pm
Monotremata wrote:I still think its weird, you can set a completely separate loop for a sample in the Program Editor, but you cant disable Loop Lock or turn on 0 Snap there. WTF Akai?


That is because it wasn’t possible in 2.0 and the other early versions of the software.

Ill have to check the submix thing later today (the misses is still sleeping in here so no monitors on yet haha). I don't really use em but I might one day!


Please do so..

Re: The Official 2.7 Bug Thread

By KOLAMBO Tue Dec 31, 2019 1:31 pm
Loosing Audio Tracks.... :evil:

Most of my Projects are loosing the recorded audio tracks from my Yamaha Synth... I have to browse them in my project library and bring them back in place after every reboot... wtf? Helpppp :hmmm:

Re: The Official 2.7 Bug Thread

By Certified Beatz Thu Jan 02, 2020 12:29 am
zangetsu01 wrote:
c-real wrote:Someone here should try to reproduce this bug and post it in the beta release forum in order to get it fixed in the next update.

So you can send 32 audio outs from your MPCX to your computer via wifi? This is interesting. How do you achieve this exactly?


On PC if so how the heck you get it to work I could never figure it out?

No you don’t have to to this over wifi if both daws are on the same PC.. its via a program called: jack audio connection kit.

It will act like an Asio driver in your Daw and you can rewire as many virtual outputs to any program you want. (Mind you this all done in controller mode)

Took me while to get the hang of it but it works.. :nod:
 Reply
Return to MPC X, MPC One, MPC Live & MPC Key