MPC 3.4 Beta 3 - Bug Reports & Feedback Here

KEY37

I posted this in the last thread, but its still a problem with the new update and I can't believe no one else has mentioned it so maybe it just happens to the Key37, or not many people use key groups or something:

When using Keygroups, whilst looping a section, any held midi notes are muted and cut off as the playhead returns to the start of the loop instead of them ringing out for their recorded duration (this used to be the behaviour in MPC 3). I wonder if its related to the event mute/audio mute shenanigans?

Can someone else confirm it this is the behaviour on their MPC? Its really annoying to try to work on a loop when the audio is getting cut like this.

Anyone noticed the coloured strip on the far left edge of the arranger on the MPC live 2 glitches when you resize the tracks vertically?

Imported an OS2 project, saved it as an imported project, reopened today, no samples at all in the project; checked the project folder, no samples in the folder either. I guess importing is always prone to glitches but everything seemed fine when I saved it… maybe it’s referencing the samples from the OS2 project? But all program/track assignments are lost so it’s a massive job to rebuild it.

Hi everyone, first poster here. I'm looking for a way to map external midi controllers to my Mpc one.
In V2 used to be a tab on the Midi Control page, but has disappeared since the first release of the beta. Midi settings are checked, tried both usb and midi, I get cc messages incoming but I can't find a way to map them, notes also play fine.

One more thing I discovered since the last beta, there's a setting in track mix to turn solos into headphone monitors. I was hoping this to send the monitored tracks to the headphone output, but it doesn't work on my mpc one, it actually breaks the solo behavior. Has anybody tried it on other models?

Cheers!

Oscar South wrote:Anyone noticed the coloured strip on the far left edge of the arranger on the MPC live 2 glitches when you resize the tracks vertically?

I see nothing like that on the Key37.

Puddin wrote:KEY37

I posted this in the last thread, but its still a problem with the new update and I can't believe no one else has mentioned it so maybe it just happens to the Key37, or not many people use key groups or something:

When using Keygroups, whilst looping a section, any held midi notes are muted and cut off as the playhead returns to the start of the loop instead of them ringing out for their recorded duration (this used to be the behaviour in MPC 3). I wonder if its related to the event mute/audio mute shenanigans?

Can someone else confirm it this is the behaviour on their MPC? It's really annoying to try to work on a loop when the audio is getting cut like this.

I can confirm that if you have "Truncate to Clip Length" selected in Preferences>Sequencer>Note Length you will get this behavior, ie the held notes are cut at the end of the loop.
But if you on the other hand choose "As Recorded", the notes will ring out (if that is what is recorded).

So it's up to you how you want it to behave.

Logrinn wrote:

Puddin wrote:KEY37

I posted this in the last thread, but its still a problem with the new update and I can't believe no one else has mentioned it so maybe it just happens to the Key37, or not many people use key groups or something:

When using Keygroups, whilst looping a section, any held midi notes are muted and cut off as the playhead returns to the start of the loop instead of them ringing out for their recorded duration (this used to be the behaviour in MPC 3). I wonder if its related to the event mute/audio mute shenanigans?

Can someone else confirm it this is the behaviour on their MPC? It's really annoying to try to work on a loop when the audio is getting cut like this.

I can confirm that if you have "Truncate to Clip Length" selected in Preferences>Sequencer>Note Length you will get this behavior, ie the held notes are cut at the end of the loop.
But if you on the other hand choose "As Recorded", the notes will ring out (if that is what is recorded).

So it's up to you how you want it to behave.

Oh wow, thats embarrassing! Thanks. I didn't realise it was an option. Strange they've changed the default behaviour there.

Just noticed this - since updating to this 3rd beta all the demo projects have disappeared. When I go to Preferences>Project Load/Save>New Project Dialog the Demos option says (not installed). Not a huge problem to be sure, but makes me wonder if anything else is missing. I wonder if downgrading and then reupdating will bring them back. Keys 61 used here.

Edit: Arghh - revertign to 2.15 didn't fix anything. It seems my content is there on my ssd, but a lot of the content that's supposed to be available like expansions and instruments and drum kits have been moved to various folders in the lost&found directory - yuck. Gotta figure out how to properly initialize this thing.

Key 37
Can’t change start and end points of a sample by touchscreen, only with knobs. Still trying to figure out what causes this. Usually happens after I record something in a sequence

blake c wrote:Key 37
Can’t change start and end points of a sample by touchscreen, only with knobs. Still trying to figure out what causes this. Usually happens after I record something in a sequence

This happens often on the Live 2 as well, except the knobs dont work either nor can you even play the sample in the sample edit page. Basically have to restart the machine.

I just updated and noticed it no longer detects the key of samples in a drum group, this was super useful and needs to be fixed.

I'm having major issues with saving. Extracting samples is giving the temp file error a lot as well as saving projects giving that error. Seems to remedy itself if you create a new project then go back to the other one but am losing work. This is new for me with the 3.4 update.

The random setting of Slice Motion seems to be using a fixed seed per program (or maybe the reason is something else). This can be observed by doing the following:

1) Record a melodic line, say a major scale, into a sample and slice it up
2) Assign that sample to a single pad
3) Set slice motion to random
4) Try hitting the pad a bunch of times. You get random slices as one would expect.
5) Record a sequence, say a single bar containing a note on each downbeat
6) Play the sequence on a loop. Observe that you no longer get random slices for each beat - instead the same sequence loops over and over again.

I wonder if this is intended. I would like to be able to get an endless sequence of randomly selected slices. This would make for some interesting ambient tracks, for example.

I tried some workarounds but couldn't make it work (using random propabilities on notes does not help, neither does routing a midi channel into the program).

I hope we can get this as an option on the slice motion page.

Kookoz wrote:The random setting of Slice Motion seems to be using a fixed seed per program (or maybe the reason is something else). This can be observed by doing the following:

1) Record a melodic line, say a major scale, into a sample and slice it up
2) Assign that sample to a single pad
3) Set slice motion to random
4) Try hitting the pad a bunch of times. You get random slices as one would expect.
5) Record a sequence, say a single bar containing a note on each downbeat
6) Play the sequence on a loop. Observe that you no longer get random slices for each beat - instead the same sequence loops over and over again.

I wonder if this is intended. I would like to be able to get an endless sequence of randomly selected slices. This would make for some interesting ambient tracks, for example.

I tried some workarounds but couldn't make it work (using random propabilities on notes does not help, neither does routing a midi channel into the program).

I hope we can get this as an option on the slice motion page.

I figured a way to do this, in case somebody else needs it. Set the sequence to start from bar 2, and slice motion will keep giving fully random choices. It only loops if you go back to bar 1, beat 1.

"Save Current Sequence" is documented in the QuickStart guide on page 67.
It says you should be able to go to Menu -> Save and “Tap Sequence to save the current sequence.” This would be just like in MPC2, but . . . . the "Sequence" option is not displayed in the save window in the MPC . Also, it's not displayed in the screenshot in the guide either.

I don't like to assume, but it is likely they've actually done away with this functionality and just missed removing that line in the Quickstart guide.

The project folders under MPC3 no longer contain individual SXQ files like in the previous version, so maybe that architecture had to be abandoned when they added Arrangements and redesigned the track/program relationships.

Note: I've reported this to Akai as an issue, as it is at least an inconstancy with the documentation..