MPC 3.4 Beta 3 - Bug Reports & Feedback Here

gilesjuk wrote:Technically a beta is feature complete and just requires testing to ensure there's no major bugs. I'm hoping this isn't feature complete because the UX around copying, pasting etc in the arranger view is pretty terrible.

What you describe is IMHO usually called a "release candidate" (RC).

I also hope for features, but perhaps there is a reason we have a bug report form, but no official channel for requests to improve new features.

Just because gilesjuk mentioned room for improvement in the arranger (without specifics). But for the mixer I have a small feature request:

The new mixer is great, but I could do without busses I don't use. Unused stuff is only clutter,

I wished unused sends, submixes and outputs would be hidden. I'm fine with a setting that changes the behaviour, eg a checkbox "show all busses including unused bussed" or "hide unused busses".

Masi wrote:What you describe is IMHO usually called a "release candidate" (RC).

I would say that a release candidate is towards the end of the QA test cycle. So when first released as a beta it is considered to be feature complete but requires testing. It won't be a release candidate yet because it's not been tested. There may be bugs or serious performance issues. Once it's been through a number of test cycles and a lot of bugs fixed it becomes a release candidate based on decisions made by the test and development managers.

User testing (like we're doing) and feedback from UX may result in further release candidates being made.

Hi, the equalizers don't work in real time with the microphone directly connected to the MPC to sing. I have firmware 3.0 on the MPC ONE+. Is this happening to anyone else?
The rest of the effects like delay, doubler, harmonizer and tuner work correctly in real time.

A pair of Glasses wrote:

This isn't a bug. Go into the Preferences MIDI section & turn off the Control tab for the MPC or any external device, I forgot which. This should solve it.[/quote]

Euh,, this still shouldn’t stop the sequencer in my opinion, as I am micro adjusting an effect on the mpc and has no interest with sync or midi input.
I am going to test your suggestion, and report back [/quote]

So, I’ve got the time to test this a bit further, and when switching the midi-input “control” at only the Mpc setting, this (bug) is gone. So that’s good news,, on the other side you can’t use the shift function anywhere as it otherwise stops the sequencer (if this control tab is active) strange as with the other versions i didn’t encountered this, and use the shift button al the time for smaller adjustments.
This is for me the first time I have to make midi-input changes for it to work. Is it a real problem, no because I just need the sync signal from the daw, so I can perfectly switch the mpc-Control-input option to off,, on the other hand is it a bug? I would say yes.

Greets
Danny

The beta is relentlessly buggy with imported projects from 2.XX, too many times to mention now I’ve loaded up projects which I have imported, tweaked until they’re playing properly, and saved as 3.X projects, only to find that on reloading the import versions, samples which had been in the project are missing, tracks are empty or the whole sequence doesn’t play. It’s happened repeatedly with several projects. Sometimes reloading again sorts it out, sometimes not. And occasionally when I check the import project folder for the offending project… it’s blank. Then I have to start all over again importing and assigning samples. I know people will say ‘just go back to 2.XX’… I don’t want to be stuck on an obsolete OS with no further support/development expected, so I’ve really worked at getting on with 3.X but the compromises of the new system plus the constant glitches in it are really making it a stretch. Some flashy new toys on the top layer but a lot of damaged toys underneath, (the main page, the mixers, the weird and unintuitive track/program collision) and the whole toybox itself is looking fairly fragile at this point.

I have really been getting into the workflow of 3.4 vs 2.xx lately, and actually banged out over 8 tracks the last 3 days.

The thing is, STEMS is no longer working. It functioned correctly in the 3 of the 8 tracks that I recently created, BUT now when I press the STEMS icon either in the editor screen or the program mode screen, it goes thru the whole process yet creates no stems of the inputted audio file. Just spits out a copy of the original file.

I've tried multiple files, powercycled the unit, reset the preferences in settings, verified that the feature was active in the activations screen, deactivated/reactivated, and even did the power button long press semi-hard reset feature... But no luck.

It just started today. Anyone else experiencing similar issues? The only other glitches that I have noticed is that when selecting start/end points of a sample, I get a bit of jitter. Other than that, if I use the event mute feature too often I find that I have to stop then start the sequences to re-enable that feature.

Thanks in advance

How will we know when a new version of the beta is launched? Do they email current users/testers? Can you just do an online update?

physis wrote:How will we know when a new version of the beta is launched? Do they email current users/testers? Can you just do an online update?

Would think you could just do an update.

But this page has the release notes. I guess look for when it says Beta 4?

https://www.akaipro.com/mpc-release-notes

Bug when trying to use the mpc one plus as midi slave.

I use a ERM Multiclock which is controlled by a midi track in Ableton.

When you try and select a drum kit on the MPC one plus playback stops on the mpc.

If you try to load an instrument same behaviour.

If you try and record hits from the pads its the same behaviour

It starts and stops fine but almost any interaction on the mpc one plus causes it to stop playback.

This is the same behaviour as MPC 2 firmware and I had hoped it would be fixed in 3.

Tis can be replicated everytime without fail.

There was some threads about it a long while back but as I had manged to get Ableton link functioning reasonably I had given up hoping for a fix.

sparky wrote:The beta is relentlessly buggy with imported projects from 2.XX, too many times to mention now I’ve loaded up projects which I have imported, tweaked until they’re playing properly, and saved as 3.X projects, only to find that on reloading the import versions, samples which had been in the project are missing, tracks are empty or the whole sequence doesn’t play. It’s happened repeatedly with several projects. Sometimes reloading again sorts it out, sometimes not. And occasionally when I check the import project folder for the offending project… it’s blank. Then I have to start all over again importing and assigning samples. I know people will say ‘just go back to 2.XX’… I don’t want to be stuck on an obsolete OS with no further support/development expected, so I’ve really worked at getting on with 3.X but the compromises of the new system plus the constant glitches in it are really making it a stretch. Some flashy new toys on the top layer but a lot of damaged toys underneath, (the main page, the mixers, the weird and unintuitive track/program collision) and the whole toybox itself is looking fairly fragile at this point.

I ran into this recently and lost a couple hours work on an imported project. A google search led me to a reddit post that suggested purging unused samples before saving the project somehow does the trick. Not sure why, but it worked for me.

Regardless it's a fairly major issue I imagine will be fixed for the next version... hopefully.

Zlornick wrote:

sparky wrote:The beta is relentlessly buggy with imported projects from 2.XX, too many times to mention now I’ve loaded up projects which I have imported, tweaked until they’re playing properly, and saved as 3.X projects, only to find that on reloading the import versions, samples which had been in the project are missing, tracks are empty or the whole sequence doesn’t play. It’s happened repeatedly with several projects. Sometimes reloading again sorts it out, sometimes not. And occasionally when I check the import project folder for the offending project… it’s blank. Then I have to start all over again importing and assigning samples. I know people will say ‘just go back to 2.XX’… I don’t want to be stuck on an obsolete OS with no further support/development expected, so I’ve really worked at getting on with 3.X but the compromises of the new system plus the constant glitches in it are really making it a stretch. Some flashy new toys on the top layer but a lot of damaged toys underneath, (the main page, the mixers, the weird and unintuitive track/program collision) and the whole toybox itself is looking fairly fragile at this point.

I ran into this recently and lost a couple hours work on an imported project. A google search led me to a reddit post that suggested purging unused samples before saving the project somehow does the trick. Not sure why, but it worked for me.

Regardless it's a fairly major issue I imagine will be fixed for the next version... hopefully.

Interesting - somewhere along the line I also tried purging a project (for space reasons) in the beta and when I loaded it up again all the audio tracks were blank. So it’s like a roll of the dice whether legacy projects work out or not…

Multiple occasions where I am unable to save projects I’m working on most recent is at the time of this post due to my frustration. No matter what I try it won’t save so I have to power down the mpc, power it back up and then test if I can save and it works. I hope this gets resolved never had this issue until the beta. I do love the beta tho. Will down grade for now. (MPC X SE)

Hi, I am quite new to the MPC and I am trying to use it as a portable sound module / workstation.

What i am struggling with is how to quickly find and switch sounds while I am playing live.

The SOUNDS UI could be improved to allow quick browsing, searching and sorting of all sounds.
This would:
- display the favorite sounds.
- seach by source (drum, keygroups, plugin, audio, cv and midi)
- search by category (bass, keys, leads, ...)
- search by user tags
- ...
I would also like to be able to map midi commands to browse the filtered sound list as well as
assign specific sounds to a midi keyboard button for fast selection.

This mechanism could also work to search and select PATTERNS to swap without changing the sound.

Tnx
AF

funkybee wrote:Hi, I am quite new to the MPC and I am trying to use it as a portable sound module / workstation.

What i am struggling with is how to quickly find and switch sounds while I am playing live.

The SOUNDS UI could be improved to allow quick browsing, searching and sorting of all sounds.
This would:
- display the favorite sounds.
- seach by source (drum, keygroups, plugin, audio, cv and midi)
- search by category (bass, keys, leads, ...)
- search by user tags
- ...
I would also like to be able to map midi commands to browse the filtered sound list as well as
assign specific sounds to a midi keyboard button for fast selection.

This mechanism could also work to search and select PATTERNS to swap without changing the sound.

Tnx
AF

These boxes aren't really meant to used like this. They want you to make everything into Drum/Keygroup tracks. They should've gave each preset their own PC/MSB/LSB#, but NOPE!