MPC 3.4 Beta 1 & 2 Bug Reports (Archived)

I'm working on a sequence in Beta 2 and have my Octatrack MKII synced over MIDI.
In the arranger, if I start the sequence at bar 1 everything plays nice together. If I start the sequence at bar 5 or any bar that's not 1 (my Octatrack tracks are 4 bars) the sync is off and my Octatrack plays back the tracks out of sync. This makes using loop points and locators in the arranger unusable with external gear.

Let me know if I'm doing something wrong.

I can't confirm if this is by design but the Explode Tracks function does not work on MIDI like it did back in the 2.xx firmware. The function isn't even an option if you create/use a MIDI track.

(Workaround)
I had to change the track to an internal DRUM track for the option to appear. Once exploded, 3.xx beta created the multiple DRUM tracks (as designed) and converting them back to MIDI achieved the desired effect.

DBurkeM wrote:I'm working on a sequence in Beta 2 and have my Octatrack MKII synced over MIDI.
In the arranger, if I start the sequence at bar 1 everything plays nice together. If I start the sequence at bar 5 or any bar that's not 1 (my Octatrack tracks are 4 bars) the sync is off and my Octatrack plays back the tracks out of sync. This makes using loop points and locators in the arranger unusable with external gear.

Let me know if I'm doing something wrong.

Is the Octatrack's 'TRANSPORT RECEIVE' set to ON? The MPC3 is sending the song position pointer correctly, so it seems like the issue is on the receiver.

Elijah wrote:

DBurkeM wrote:I'm working on a sequence in Beta 2 and have my Octatrack MKII synced over MIDI.
In the arranger, if I start the sequence at bar 1 everything plays nice together. If I start the sequence at bar 5 or any bar that's not 1 (my Octatrack tracks are 4 bars) the sync is off and my Octatrack plays back the tracks out of sync. This makes using loop points and locators in the arranger unusable with external gear.

Let me know if I'm doing something wrong.

Is the Octatrack's 'TRANSPORT RECEIVE' set to ON? The MPC3 is sending the song position pointer correctly, so it seems like the issue is on the receiver.

Transport receive and clock receive are on in the Octatrack. I figured it out, it's due to the 2 tracks on the Octatrack being set to play back at half time.

Hi where I'm at, I always had difficulties updating via the internet, so I haven't been able to get the beta public 2 version. I was wondering if the issue with Looper mode saving to audio track is resolved?

dilingdong wrote:Hi where I'm at, I always had difficulties updating via the internet, so I haven't been able to get the beta public 2 version. I was wondering if the issue with Looper mode saving to audio track is resolved?

No, it hasn’t been resolved yet. According to the Known Issues in the release notes, there’s a crash when exporting from the Looper to an Audio Track after reordering tracks. It seems like it might not crash if you don’t reorder them.

Finally got around to installing 3.0 beta after installing 2.15.1 and doing thorough stability tests. Installed, then immediately reset preferences and updated via online to latest version (3.4.0.92). After setting the preferences to my personal liking, I noticed that there are at least 2 preferences that seem to keep resetting to their defaults after loading a new project:
1) Preferences>Hardware>VU Meter Source: I usually set it to “Main”, it keeps resetting to “Current Track”
2) Preferences >Hardware>Bank Button Press: I usually set it to “Select/toggle bank”, it keeps resetting to “Select A-D”.

One cool feature addition/change (for those of us with MPC X/X SE units): the OLED display above the current track now displays the actual track name instead of just “Track 1”, etc. Also, the physical “Menu” button has returned to its toggle operation like it used to in older versions of 2.x. Press it once, you get the menu screen. Press it a second time, it returns to the main screen.

Found a little glitch with my MPC Live 1, after copying a track and trying to rename it, it reverts back to it's copied name instead of what I want it to be called.

For example, I wanted to copy all settings from Track 1 to Track 2. Track 1 is titled "Kicks 1" and I want Track 2 to be titled the same. When copying, the MPC automatically suggests the name "Kicks 1-1" to be used. If I accept this and try to change it later, it keeps reverting back to the incorrect "Kicks 1-1" instead of the new "Kicks 1" I manually write into the track edit box. This problem doesn't happen if I just totally rename the track, it only seems to happen if it seems like I'm missing some of the ending characters of the title.

Edit: it seems that in general I'm having a problem with renaming copied tracks. They seem to want to name themselves. Copied track lengths revert back to their copied values after changing them.


Also running into concerning memory issues. Trying to get a similar workflow to my 2.9 workflow that I gig around with constantly. Not even close to adding the tracks I need to perform live improv (I have 100 tracks per sequence, and I go through multiple sequences). I haven't even added 32 tracks of simple drum programs, and I'm already at 82% memory. My CPU is hovering around 35-40%.

Man, I'm starting to get the hang of 3.0 but if I can't perform live like I can on 2.9, I'll definitely be bummed. It seems 3.0 is really ratcheting up the memory.

MPC 2.9 is the only usable version for me at this point....STILL! and I'd love to buy the soft synths and effects....oh well :/

As part of my thorough testing of 2.15.1 and 3.4.0.92, I load up all the demo patterns/styles/songs that are included with the base unit and the expansion packs that can be downloaded. Most loaded and played back ok on both versions. A few (2 to 3 or 4) would not load or took forever (5-15 minutes or more) to load and gave "memory almost full, please save your work" errors when loading. I think this is because some of the demo styles in the EDM & Future House Essential Sound Libraries pack have multiple sequences with different instruments loaded onto the same tracks, which the new Beta OS is trying to duplicate to multiple tracks/instances per sequence. I have a feeling you are pushing the maximum limit with your sets, thanks to this new setup.

Hi folks wondering if anyone has encountered this. 'New project' button (from the startup screen) loads what looks like a default project (which im guessing is normal or at least other people see this). Launching 'New Project' from the menu causes the MPC X to reboot every time. Cannot start a new project.

I changed the preferences so that New Project is now an empty project by default, which fixed the reboot issue from the startup screen (and it launches an empty project), but 'New Project' from within the Menu still rebooots the machine.

ignore muted tracks in song mode doesn't ignore them, just mute them with automation.the midi datas still here. so whatever you choose "include muted tracks" or "ignore muted tracks" it act the same.

MJ76 wrote:Hi folks wondering if anyone has encountered this.

I changed the preferences ... 'New Project' from within the Menu still rebooots the machine.

I have similar here with MPC One. I set the preferences for new project to a template I created (empty project with one audio track as input). Then selecting new project causes the MPC to freeze, power switch is unresponsive... only solution is to hard cycle the MPC (remove power, re-insert, and boot up again).

Has been reported.

MJ76 wrote:I changed the preferences so that New Project is now an empty project by default, which fixed the reboot issue from the startup screen (and it launches an empty project), but 'New Project' from within the Menu still rebooots the machine.

My guess is that this serves as a RAM clean-up.

Key 61 user however only recently purchased. It came with ver. 2 15 but because Beta 3 was out I didn't want to invest too much time in learning MPC 2 .15 so I went with 3 4 beta.

I can't seem to save MIDI Port settings in a project. I have my Fantom G synth plugged into Key 61 via USB and use it both as a controller for the Key 61 and for its own sounds. Key 61 is the sequencer I use, not the G's. The ports show the Fantom G both in and out ports, all good. I create my song with say a couple of MIDI tracks set to pkay the Fantom G, ports set, midi channels set. All good, playing great. Hit save, shutdown, come back next day and all midi port settings, mapping of channels are gone, I have to re-map ports and midi channels manually = pain in the backside. Why can't midi port settings / channels be saved with the project? Imagine 2, 3 external synths, sound modules and having to manual re-map each boot up, each project etc. Not practical.

Is this a bug or user error?

Hi, I have some problems with midi tracks. I have an mpc Live that I use to control 8 tracks of a Roland workstation via midi and a midi controller connected via usb. It is no longer possible to create a midi mapping for the Mute and Solo buttons, and when the tempo starts the mpc brings the volume of many midi tracks to maximum. Already when I turn on the mpc I find in the mpc mixer some tracks, always different, with the volume at maximum, but the volume is actually changed only when the mpc is in play. I specify that even disconnecting external midi controllers the volume of the tracks is always altered.