MPC 3.4 Beta 1 & 2 Bug Reports (Archived)

The "clip" function disappear. It was a central part of my workflow. I won't be able to definitly swith to MPC 3 if this feature doesn't come back
Or even go away from the akai MPC stuff
Realy hope it will be back soon

doctortweek wrote:Key 61: The arpeggiator does not work - nor of course the latch button.

Going back to v2.0 tomorrow.

I can confirm that by pressing the "ARP" button on my Key 37 it won't engage the arpeggiator.
Although ... if I double tap the button, the arpeggiator starts in latch mode and the pop up window displays.
Here I can turn off and on the latch function as well as turn off and on the whole arpeggiator engine.
Curiously though ... I can also access the pop up by long pressing the ARP button, but the display disappears as soon as I let go off the button. Also, if I turn on the arpeggiator while doing this, the arpeggiator doesn't start. Only way to start it is by double clicking as far as I have been able to deduce.

Williammarsh0 wrote:MPC One - when using my zoom l12 as an audio interface after 3.4 update, audio coming from MPC clips/sounds distorted randomly. If I go in the menu and change it back to internal, then back to l12 again it fixes it. Sometimes happens multiple times in one session. Haven't yet checked to see if it does the same thing using just internals. Also, getting low memory warning since updating. Didn't have either problem on 2.15.

Wasn't quite sure at first, but can confirm this happens with the Tascam Model 24 as well. It's like random static. Using an MPC One Plus.

I just had a moment where I turned the main knob all the way down on the Model 24 thinking that may be the cause of this, and I lost all sound and couldn't get it back by turning the knob up. Had to do as you said, switch to Internal and then back to thw interface in preferences to get my sound back.

Tried changing the sample rate to 44.1khz 24bit on the interface thinking that might help. No dice.

I think there is something from with bank select and program changes.

I couldnt get PC to my yamaha modx6 any more. After rebooting the modx it works until I sent a bank change, after that it stops working.
I hooked up my 2500 to my modx and PC work from there fine with bank selects.

Can someone reproduce that, should I report that to akai?

Took my the half weekend because I thought my modx gone fritz.

When I load any different beat, the same sample loads from 1 track. To explain more, I load a beat lets call it beat 1. Beat 1 has sample xyz as the main sample on track 1. I load beat 2 and beat 2 should have sample abc as I created but instead it loads sample xyz from beat 1. This happens with every beat. Anyone experiencing this?

Monitoring from multiple inputs on a USB audio interface causes the audio to drop completely at times. Fixed by reselecting
the interface from preferences.

Cycles in motion slices does not work well. if I select slice 5 and I set random and cycles 4 I do not want that slice 1 sounds. Also, If I have to change all the motion for different pads, the numbers changes -1.

How is everyone doing with Pad Perform? I can load a new project, load a plugin instrument, pick a scale, and come up with something on the spot. After building the song around that, I save it.

My issue is that after reopening the project later on, pads 12 and 13 are assigned the same notes regardless of changing the scale. The only solution I've found is to recreate the track/plugin from scratch and deleting the prior one.

I understand Pad Perform may not be saved to the project itself, but the duplication of pad 12 and 13 throws me off.

Not sure if this is a bug or not. Thank you

Live 2 Retro

Korzo wrote:Cycles in motion slices does not work well. if I select slice 5 and I set random and cycles 4 I do not want that slice 1 sounds. Also, If I have to change all the motion for different pads, the numbers changes -1.

Regarding the first point, if you have 9 slices, set 'slice:5' and then cycles:4, it will use slices 5, 6, 7, 8, 1. Please expand on your issue if it's something else (step by step with details).

Similarly with your other issue, can you give a step-by-step on this and I will report directly to the developers. I'm very interested in ensuring slice motion is working 100% as I want to use it extensively. I've already picked up other bugs with it during closed testing that have now been resolved, so they are actively fixing these.

I had installed the beta software on my moc live. I was able to use it til there are two things that made me revert back: I could not save my session - it gives me a path error on both internal and external and I could not change the time signature. The software is good but I can't work on something with these two issues. When will these things get fixed?

doctortweek wrote:Key 61:

Making a new recording: after the count in the first note or notes doesn't get recorded... you have to play intentionally late and then move the notes on the grid so that they are on the 1st beat.

It is as if the 'capture window' is too small. I thought I was playing 'early' but this is not the case. If you play bang on the beat it does not register. Anyone else?

I have reported this to Akai.

I know exactly what you're talking about but, I've dealt with this without even upgrading to 3.0. I'm not 100% sure but, I think this only an issue for people not using quantization.

When you press and hold the note repeat you can change the frequency of the note repeats - 8th notes, 16th notes etc. When you do this it sets the global Timing correction (TC), which in my mind is something completely different. Can anyone confirm if it did this before version 3? I don't think it did but can't remember,

MPC-Tutor wrote:

Korzo wrote:Cycles in motion slices does not work well. if I select slice 5 and I set random and cycles 4 I do not want that slice 1 sounds. Also, If I have to change all the motion for different pads, the numbers changes -1.

Regarding the first point, if you have 9 slices, set 'slice:5' and then cycles:4, it will use slices 5, 6, 7, 8, 1. Please expand on your issue if it's something else (step by step with details).

Similarly with your other issue, can you give a step-by-step on this and I will report directly to the developers. I'm very interested in ensuring slice motion is working 100% as I want to use it extensively. I've already picked up other bugs with it during closed testing that have now been resolved, so they are actively fixing these.

You were right about cycles! I think the name is quite confusing. If I have 10 slices and I start with slice 6 and set 6 cycles, slice 1 will sound. If I set 4 slices, it will play 6, 7, 8 and 9.

There is still a bug, but not so big:
Set two sliced sounds in different pads (pad1 and pad2) and same layer (lets say layer 1), then click on the slice motion, set the cycles value to 2 (for example) for pad1, hit Pad2 set the any cycle value, hit Pad1 and the value of the cycles will be 1 instead of 2.

geecen wrote:When you press and hold the note repeat you can change the frequency of the note repeats - 8th notes, 16th notes etc. When you do this it sets the global Timing correction (TC), which in my mind is something completely different. Can anyone confirm if it did this before version 3? I don't think it did but can't remember,

In MPC2 as well, using note repeat turns TC ON.

Another Expert Sleepers ES-9 user here. Glitches and distortions render it unusable. I really wish this would be fixed once and for all in the final release.