MPC 3.4 Beta 3 - Bug Reports & Feedback Here

Event (MIDI) track mutes now implemented - select 'event' muting on track mute screen.

FYI: Pad mutes still 'audio' mutes only. Track muting in MAIN still an audio mute.

Lots of existing bugs fixed, lots of new ones introduced, lots of existing ones still there

Carry on submitting feedback, let them know what you think of how muting is now being implemented. Any new bugs, let them know. Keep on hassling them about the changes to programs (no way to assign a program to multiple tracks, changing program assigned to existing track etc)

MPC3 Bug Reports

MPC 3 Feedback & Suggestions

New features

Track Mute: Event vs. Audio Mute

Track Mute now offers greater flexibility with a new option to toggle between Audio Mute and Event Mute for supported track types. This enhancement applies to tracks containing both MIDI events and an audio path, including:

Drum Tracks
Plugin Tracks
Keygroup Tracks

For MIDI and CV tracks, Event Mute will always be applied, while Audio Tracks will always use Audio Mute, regardless of the selected option.

Event Mute silences new MIDI events but allows any currently playing events to ring out naturally.
You can seamlessly switch between Event Mute and Audio Mute via the Track Mute Toolbar, giving you more control over how your tracks behave during muting.

Export Drum Pads as Separate Stems

Exporting individual drum pad stems is now more streamlined, allowing greater flexibility in mixing and post-production. You can render an audio stem for each pad with events in a drum track. To export drum pads as stems:

Load a drum kit and record your pattern into the MPC sequencer.
With the drum track selected, press MENU and then choose SAVE.
In the SAVE selector, choose Drum Pads as Stems.
Specify your preferred audio format and destination for the stems.
Hit EXPORT to render your stems for easy mixing in your DAW.

Faster Sample Loading

Improved Performance: Sample loading now runs on a background thread, significantly reducing load times for programs, tracks, and projects.
Streamlined Program Handling: Replacing programs and samples is now more efficient, especially when loading a new program file into a track that already contains existing samples.

Bug Fixes

[NEW] Occasional hang that was seen on startup and update has been resolved
[NEW] Crash no longer occurs when exporting Looper to Audio Track after reordering tracks
[NEW] Loading an MPC2 project from the Recent field will load correctly and no longer show an empty project
[NEW] Mute automation is no longer locked in after using Explode Track
[NEW] Sample start and end points are now retained on loading
[NEW] Playback latency no longer occurs when loop brace is set beyond independent track length
[NEW] When the maximum number of tracks is reached the “Load to new track” button is now greyed out in the browser
[NEW] ‘Send To’ is no longer removed from I/O after reordering receiving track
[NEW] Resolved an issue where certain MP3 files caused the TUI to hang
[NEW] Resolved an issue where certain NFTS drives would not appear
[NEW] Q-Link Focus now updates correctly for MIDI tracks in track edit on Screen Mode
[NEW] List Edit transients are correctly muted at 001:01:000
[NEW] In Convert to New Drum Track pop-out the Create Events hit box placement has been corrected
[NEW] Improvements have been made to the loading times for larger programs and keygroups
[NEW] Project title is retained with _import appended to the file name when loading an MPC2 project
[NEW] Resolved cosmetic issue with grid lines during playback and when adjusting zoom levels

yep, the sample edit blank slice is fixed. but the muted tracks event are still in the grid when you convert a song into one big sequence and you wanna ignore muted tracks

No word on the midi note assign bugs in the changelog

FYI, browser loading is quicker, but only because loading is now more of a background process. If you load a sample heavy project it 'seems' to load really quickly, but if you immediately go to MENU > PROJECT you might see that some samples are showing a red '-' next to their name, which means they haven't actually loaded into RAM yet. But soon they'll all show as loaded.

This does mean that those queued samples won't be available to 'play' in your project until loading to ram has completed, so if you find that your pads are not yet emitting audio, this is likely the reason.

Three year old midi note-off bug???
nope.

MPC-Tutor wrote:Event (MIDI) track mutes now implemented - select 'event' muting on track mute screen.

FYI: Pad mutes still 'audio' mutes only. Track muting in MAIN still an audio mute.

Lots of existing bugs fixed, lots of new ones introduced, lots of existing ones still there

Carry on submitting feedback, let them know what you think of how muting is now being implemented. Any new bugs, let them know. Keep on hassling them about the changes to programs (no way to assign a program to multiple tracks, changing program assigned to existing track etc)

Why not post this in the MPC3 thread that's already on going?

Because that topic is getting long and often strays off topic. I make separate bug report topics for each firmware release, so I want to start treating the beta releases in a similar way. That way we can concentrate on talking about the new features, fixes and remaining bugs.

B-Wise wrote:Why not post this in the MPC3 thread that's already on going?

MPC-Tutor wrote:Because that topic is getting long and often strays off topic. I make separate bug report topics for each firmware release, so I want to start treating the beta releases in a similar way. That way we can concentrate on talking about the new features, fixes and remaining bugs.

B-Wise wrote:Why not post this in the MPC3 thread that's already on going?

Cool

ontherun wrote:No word on the midi note assign bugs in the changelog

i tried to map some notes, same thing, just chaos. The notes that are displayed are not sent and the notes in the stepsequencer are different from the ones on the main screen.
The notes that are diplayed in the output monitor are correct, when I set my HR16 to those Notes its fine..

got some performance issues were the whole GUI stops for half a second, happen more than twice

I'm having this issue with Beta 3 and my Scarlett 2i2 interface. I just tried the update, and the issue is still there.

When I play audio over my speakers through the Scarlett, I get a lot of static with my audio. I'm not getting it over the built in speaker, nor my headphones.

I've tried many things already;
- replugging and restarting devices
- resetting preferences
- re-reselecting the device in settings
- registered the beta of course...

Unfortunately, beta 3 is unusable because of that.
I just downgraded, waiting for the next release

Does anybody else have this issue?

step by step by step...
maybe AKAI isn't fast enough on filling all their users wishes, but at least they keep supporting us continously with free updates for quite a while now, which is cool in my books.

cocosushi wrote:step by step by step...
maybe AKAI isn't fast enough on filling all their users wishes, but at least they keep supporting us continously with free updates for quite a while now, which is cool in my books.

Them plugins ain't overpriced for nothing.

B-Wise wrote:

cocosushi wrote:step by step by step...
maybe AKAI isn't fast enough on filling all their users wishes, but at least they keep supporting us continously with free updates for quite a while now, which is cool in my books.

Them plugins ain't overpriced for nothing.

agreed - but then you don't have to buy them?

Still no time signatures besides 4/4. Major problem Akai is going to have to address eventually.