MPC 3.4.1 (Release) Bug Reports Here

Hi everyone.

I'm encountering some very serious bugs.

1) After inserting a few empty bars at the beginning of the project, no track produces any sound within those empty bars. The volume level can be seen moving in the corresponding panel, but the output remains silent. The situation returns to normal after the newly inserted bars.

2) After copying some bars, if I try to record new notes, the recording overlaps with the sound of the previously copied bars. In other words, the new recording loops the previous bars.

This is absurd.

Thanks for the help!

I am unable to recreate the first one, is it a particular track type? Audio track? Drum track? Can you upload a video of this issue?

Second one I am not sure I understand what you are describing, Is it possible to explain in a different way, or with a video?

pachismo wrote:Hi everyone.

I'm encountering some very serious bugs.

1) After inserting a few empty bars at the beginning of the project, no track produces any sound within those empty bars. The volume level can be seen moving in the corresponding panel, but the output remains silent. The situation returns to normal after the newly inserted bars.

2) After copying some bars, if I try to record new notes, the recording overlaps with the sound of the previously copied bars. In other words, the new recording loops the previous bars.

This is absurd.

Thanks for the help!

MPC-Tutor wrote:I am unable to recreate the first one, is it a particular track type? Audio track? Drum track? Can you upload a video of this issue?

Second one I am not sure I understand what you are describing, Is it possible to explain in a different way, or with a video?

pachismo wrote:Hi everyone.

I'm encountering some very serious bugs.

1) After inserting a few empty bars at the beginning of the project, no track produces any sound within those empty bars. The volume level can be seen moving in the corresponding panel, but the output remains silent. The situation returns to normal after the newly inserted bars.

2) After copying some bars, if I try to record new notes, the recording overlaps with the sound of the previously copied bars. In other words, the new recording loops the previous bars.

This is absurd.

Thanks for the help!

As for the first issue, after creating a series of MIDI tracks (connected to their respective plugins) and drum tracks (on which I had successfully recorded), I inserted 16 new bars at the beginning of the sequence. The result is that these new bars are completely silent. If I try to record, the volume level of the recorded track moves, but the output panel remains still. Once past the 16 new bars, everything starts working normally again. After multiple attempts, I managed to record normally on a couple of MIDI tracks within the new 16 bars, but the others remain inexplicably silent.
As for the second issue, after recording several MIDI and drum tracks, I copied a few bars. After this operation, if I try to record on new bars following the copied ones, the previously copied bars are recorded simultaneously along with the new notes. In practice, during the recording of the new bars (which should initially be completely empty), the bars from the previous copy operation are also played and recorded. I want to clarify that the "loop" function is disabled.
I don't know if I explained myself correctly.
Thanks!

List Edit > Insert: PAD parameter not picking up correct pad

1. Drum track > Go to LIST EDIT
2. Press INSERT to open INSERT EVENT screen
3. Hit pad A01

Expected: The PAD field changes to pad A01
Actual: Pad field changes to F13 (0). None of the pads are giving the correct values no matter which bank I select.

MPC-Tutor wrote:Setting custom sequence loop disables audio track playback upon loop

1. Project with at least 1 audio track
2. Set a custom seq START point (via MAIN or ARRANGE)
3. Press [PLAY START] and let sequence play and then loop back to START point

Expectation: Audio track continues playing
Actual: audio track is silenced upon looping
Workaround: Press STOP then PLAY to reactivate audio track.

ohhhh my ..... This is so bad, I wouldn’t have dared publishing 3.4x.
This is like buying a watch without clock hands..... I have wasted hours, trying to find the error I could have done....
I tried slices and other ways no chance.
Now I read this. Thanks Tutor for the explanation - I was almost going to kill myself

As for the first issue, after creating a series of MIDI tracks (connected to their respective plugins) and drum tracks (on which I had successfully recorded), I inserted 16 new bars at the beginning of the sequence. The result is that these new bars are completely silent. If I try to record, the volume level of the recorded track moves, but the output panel remains still. Once past the 16 new bars, everything starts working normally again. After multiple attempts, I managed to record normally on a couple of MIDI tracks within the new 16 bars, but the others remain inexplicably silent.

Just to give you peace of mind, I've had this too with one of mine. The project was originally started in 2.15.1 before being opened in 3.4.1 and in one linear sequence. I decided to insert 2 bars at the start and record a midi track but, same outcome as what you described. The song had 5 midi tracks running outboard gear and 3 drum tracks off samples. But it's only affected the one project and several others had been fine. I've since given up and downgraded back so I can't help further isolate the cause, sorry.

DellAtreides wrote:

As for the first issue, after creating a series of MIDI tracks (connected to their respective plugins) and drum tracks (on which I had successfully recorded), I inserted 16 new bars at the beginning of the sequence. The result is that these new bars are completely silent. If I try to record, the volume level of the recorded track moves, but the output panel remains still. Once past the 16 new bars, everything starts working normally again. After multiple attempts, I managed to record normally on a couple of MIDI tracks within the new 16 bars, but the others remain inexplicably silent.

Just to give you peace of mind, I've had this too with one of mine. The project was originally started in 2.15.1 before being opened in 3.4.1 and in one linear sequence. I decided to insert 2 bars at the start and record a midi track but, same outcome as what you described. The song had 5 midi tracks running outboard gear and 3 drum tracks off samples. But it's only affected the one project and several others had been fine. I've since given up and downgraded back so I can't help further isolate the cause, sorry.

Thank you for the comfort!

OPx-4 > FX: FX states not properly saved (or restored?) - was there in 3.4.0 beta3

1. Create plugin track with OPx-4
2. Go to PROGRAM EDIT
3. Go to FX sceen
4. Pick 3 effects and set arbitrary parameter values
5. Save as new plugin preset
6. Change to any other preset
7. Change back to the newly created

Expected: The FX settings are set as at the time of the preset creation
Actual: Most of the FX settings are back to their initial values

The same happens when I save a project and load it. The FX settings are broken.
It's impossible now to use the internal FX of OPx-4.

lordradish wrote:Putting program changes in list view or grid automation doesn't seem to work, nor do they let you actually pick a number - it just goes in percentages.

It shows percentages, but it seems to keep its values.

Insert a PC and set the value to 50% with the encoder. When you double tap the value field you see its actual value: 63. Set the value to 10 and you get 8%. Double tapping you see the 10 again.

"Simply" ignore set the program number on the number pad and ignore the percentage.

I’m facing a serious bug in MPC 3.4.1 where the Rec button (overwrite recording) is not functioning correctly. When using the Rec button to overwrite an already recorded sequence, some previously recorded notes remain and overlap with the newly recorded notes.

This issue does not occur when overwrite recording with a single pad, but it happens when performing finger drumming using multiple pads.

With such a fundamental feature not working properly, MPC 3 becomes completely unusable.

Video: https://imgur.com/a/baZz5TW

Not able to recreate this, must be something unique that you're doing? Is this all projects or one specific project?

Can you post a step by step recreation?

Elijah wrote:I’m facing a serious bug in MPC 3.4.1 where the Rec button (overwrite recording) is not functioning correctly. When using the Rec button to overwrite an already recorded sequence, some previously recorded notes remain and overlap with the newly recorded notes.

This issue does not occur when overwrite recording with a single pad, but it happens when performing finger drumming using multiple pads.

With such a fundamental feature not working properly, MPC 3 becomes completely unusable.

Video: https://imgur.com/a/baZz5TW

MPC-Tutor wrote:Not able to recreate this, must be something unique that you're doing? Is this all projects or one specific project?

Can you post a step by step recreation?

Elijah wrote:I’m facing a serious bug in MPC 3.4.1 where the Rec button (overwrite recording) is not functioning correctly. When using the Rec button to overwrite an already recorded sequence, some previously recorded notes remain and overlap with the newly recorded notes.

This issue does not occur when overwrite recording with a single pad, but it happens when performing finger drumming using multiple pads.

With such a fundamental feature not working properly, MPC 3 becomes completely unusable.

Video: https://imgur.com/a/baZz5TW

I believe this issue occurs regardless of the specific project or program.

To recreate the problem, follow these steps:

1. Turn off TC.
2. Record finger drumming using Rec+Play Start.
3. Record finger drumming again using Rec+Play Start. (If you repeat step 3 two or three times, you can clearly hear the overlapping notes.)

This issue does not occur when using external USB-MIDI pads or in controller mode (MPC2).

Okay, got it. TC must be off. That's really not good at all.

A way to highlight it; record basic kick snare pattern at half level. Extend all the events then record at full level so you can see the short red events on top of the existing long yellow events.

Also SHIFT > SELECT ALL > DELETE doesn't seem to visually delete those ghost events. You have to leave grid and go back before they go.

I just officially reported this to the closed beta group.

MPC-Tutor wrote:
A way to highlight it; record basic kick snare pattern at half level. Extend all the events then record at full level so you can see the short red events on top of the existing long yellow events.

I see, that makes it much clearer.

when i save in ableton format from a 37 or an X, both in 3.4.1, as well as early betas, and then try to open , on my laptop, in ablrton... doesn't work... it starts the ableton opening and before it gets there, it stops. sometimes says ableton didn't open and try again ...and does it again..
please help...thx