MPC 3.6 & 3.7 Standalone Bug Reports

- Still no program changes per track per sequence.

- Still program changes are seen as automation in List Edit, meaning there will always be the unremovable program change added at 0.

- I still cannot hold notes over sequence changes… If I hold a chord it will cut out when the sequence changes.

Also when booting up the first time after the upgrade I had to reactivate all plugins... And after rebooting again after activating I was met with "Need to download plugin content again" something message. After accepting this the plugins which needed to be reactivated needed to be manually replaced... So I needed to remember what plugins and presets I had used. Super annoying. I've so far tested with a small program made in 3.5, I hope the same will not happen in one of my larger programs...

Interesting. After the update from 3.5 to 3.6 the plugins on my MPC did not need any reactivation or download.

Can please someone with a midi drum machine trigger an instrument on Pad A1 on the main screen, than go into the step sequencer and trigger Pad A1, does the same instrument get triggered, ergo is the same note sent?
Here is a video that shows whats wrong: https://youtube.com/shorts/R0N4LXtVmOE?feature=share

Since there is this Pro Update, is that bug still there when Its activated?

EDIT:
im playing arround and go knows why, but no i have the pad mapping i only had in the step sequencer on the main screen.
But when I trigger a pad inside the step sequencer(pad select) no midi note is sent.

ontherun wrote:Can please someone with a midi drum machine trigger an instrument on Pad A1 on the main screen, than go into the step sequencer and trigger Pad A1, does the same instrument get triggered, ergo is the same note sent?
Here is a video that shows whats wrong: https://youtube.com/shorts/R0N4LXtVmOE?feature=share

Since there is this Pro Update, is that bug still there when Its activated?

EDIT:
im playing arround and go knows why, but no i have the pad mapping i only had in the step sequencer on the main screen.
But when I trigger a pad inside the step sequencer(pad select) no midi note is sent.

If I set the MIDI progressions menu to Chromatic C1 starting at bank A, recorded triggers to my E-MU e5000 Ultra maps out correctly on the pads and in the grid. The step sequencer though is different. On Bank A Pad A1 starts at C-2 (or C-1) then works its way up chromatically up the pads and banks. However, if you exit out the step sequencer and press a pad mapped to your drum machine/synth/external device, going back into the step sequencer mode and programming the sequence will be for the last pad you hit before going into sequencer mode. IMO everything is fine so far on the MIDI side of sequencing.

On another though, not only do I have to reauthorize my paid plugins every boot up, I also lose my renaming of MIDI ports in the MIDI/SYNC preferences on every boot up as well. This is awful for workflow if you don’t have a backup notepad to list your external MIDI connections if your sequencing MIDI gear. Anyone else having this same issue?

going back into the step sequencer mode and programming the sequence will be for the last pad you hit before going into sequencer mode.

But if you press "pad select" and press a pad its not the same note.
In a normal drum program pads/samples are the same pad, no matter where you are.
This is confusing.

ontherun wrote:

going back into the step sequencer mode and programming the sequence will be for the last pad you hit before going into sequencer mode.

But if you press "pad select" and press a pad its not the same note.
In a normal drum program pads/samples are the same pad, no matter where you are.
This is confusing.

Right…what’s going on is when you press pad select and press a pad, it’s not the same as in Main mode. For some reason Step Sequencer Pad Select starts the pads from C-2 (or C-1 I forgot) on Bank A Pad A1 and triggers chromatically up from there the further up the Banks you go. Look in the corner of the step sequencer and it will show you what note the pad is triggering. It is triggering and sequencing correctly. It’s just that step sequencer mode starts at the lowest note of the chromatic scale starting at Bank A pad A1. Hope that helps.

Hi,

First, sorry for my english...

Since the 3.6 update , my MPC X have a bug.
The music of my sequence stopped after something around every 5 minutes, but the play button is still green...i need to stop and to relaunch the music... It's boring
Please help me
Peace
Sam

SAMKCH wrote:Hi,

First, sorry for my english...

Since the 3.6 update , my MPC X have a bug.
The music of my sequence stopped after something around every 5 minutes, but the play button is still green...i need to stop and to relaunch the music... It's boring
Please help me
Peace
Sam

Check if the Arranger has loop turned off.

Not strictly a bug because I can't recreate it every time, but for a heads up:

Issue: re *Some* Projects originally created in V2.15, imported into V3 and last saved in V3.5.

When first opened into V3.6 and working in the arranger I'm getting an error message within, say 5 mins, with the choice of reloading the project or new project (should have taken a photo for exact wording, but I didnt) - no save option.

I don't have a common denominator between the projects that crashed to work out what causes the error. When I've saved a project straight away upon loading I don't have an issue.
I've run out of V2.15 to keep looking into this, but heads up, might want to save your old projects in 3.6 before editing them. And a 2nd heads up, apparently if you roll back to 3.5 you then can't open 3.6 projects (I've not rolled back to confirm, but it's what "they" are saying)

I also have some very noticable clicks/stutters when changing sequences... On the verge of it being unusable currently when relying on sequence changes

Anyone else have issues with this?

Yep… at least since 3.5.

horisonten wrote:I also have some very noticable clicks/stutters when changing sequences... On the verge of it being unusable currently when relying on sequence changes

Anyone else have issues with this?

Noticed lots of crackling on audio tracks when using audio interface. Using a Behringer umc 1820.
its not just a monitoring problem as you can hear the crackling during in the recording.
pushing the play/start button will also cause a crackle as the teh player moves to the new start position.

DellAtreides wrote:And a 2nd heads up, apparently if you roll back to 3.5 you then can't open 3.6 projects (I've not rolled back to confirm, but it's what "they" are saying)

I believe this is case, I think the same happened when trying to load 3.5 projects in 3.4.x.

After updating my MPC key 61 from version 3.5 to version 3.6, I lost the opening screen, where a certain plugin sound library is selected. Instead, I get a window where I can just select a project (which I don't have). It's as if all the factory plugins have been lost, which are of course licensed, because they come with the instrument. I tried to get the library sounds window, by pressing the sounds button, on the instrument itself, but without success.
Can someone explain to me what is going on?
In the end, after multiple reboots, I got annoyed and downgraded to v.3.5. To my great happiness, the favorites list returned, which was filled to the brim, and its re-formation would have cost me several hours. That must have already happened with the transition from v.2 to v.3.
Thanks in advance.