OS 1.01 Bug Report

scd wrote:

Askia Shaheed wrote:

scd wrote:Can you reproduce that bug Askia?

Which one? MIDI sync?

No, I mean the crashing/freezing mpc

Anyone can reproduce that bug.... All you gotta do is try to make a beat fast.... Once you start clicking different screens, a couple of "Undo" button hits, and try to rerecord very fast, a couple of tries, and you ve got it.... FROZEN LIKE THE ARTIC

scd wrote:

Askia Shaheed wrote:

scd wrote:Can you reproduce that bug Askia?

Which one? MIDI sync?

No, I mean the crashing/freezing mpc

Yes. I wrote about that in this same thread I believe.

Askia Shaheed wrote:Yes. I wrote about that in this same thread I believe.

OK, a bug entry has been made.

Was working on some multisamples today and set up some sustaining loops in Soundforge. Loaded them into the 5000 and out of 13 samples loaded, only 2 retained the loop points.

I fired up the MPC1000 (currently running JJ 3.08) and all 13 loaded up fine. Re-saved in the 1000 and loaded the 1000 versions back into the 5000, and this fixed it for the 5000.

Not sure why the 5000 is struggling with the direct loading Soundforge stuff (meta data is being saved in SF).

Another bug:

Record a sample in your MPC5000
Go to TRIM and set a start point of 0
Go to LOOP
Unlock the start point padlock
Set a new Lp start point of whatever, say 100.
Now hit WINDOW for the Loop Fine screen
The start point shown is 0, not 100. Editing this '0' changes the TRIM start point, not the loop start point.

Conclusion: In LOOP, pressing WINDOW does not show the 'loop' fine screen, you instead see the 'trim' fine screen.

How did they miss that one or do I need to RTFM or read my own ebook,lol?

I've trimmed this thread down to keep it focused on actual confirmed bug reports.

Hey yall.
I am facing a terrible bug right now that is absolutely stopping my workflow. In trim mode I will cut a sample down, go back to the main screen and press the sample and often it will either not play, because the trim has been changed by some other force, or the start and end points will have changed. Often it will say that the start point is -31,000 for example...I have no idea what that even means, but I know it's not normal. Also, I will fix all the start and end points ion trim and save, and when I load the project again, many of the same samples that were changed will be messed up again. I don';t know why this is happening, but it is reeeeeeeeeallllly enfuriating. I have stopped making beats until someone can clarify what this might mean. Spoke with akai forever and they were baffled. Does anyone have any idea how I can remedy this terrible situation?
Regards,
Boom Baptist

tha wrote:Hey yall.
I am facing a terrible bug right now that is absolutely stopping my workflow. In trim mode I will cut a sample down, go back to the main screen and press the sample and often it will either not play, because the trim has been changed by some other force, or the start and end points will have changed. Often it will say that the start point is -31,000 for example...I have no idea what that even means, but I know it's not normal. Also, I will fix all the start and end points ion trim and save, and when I load the project again, many of the same samples that were changed will be messed up again. I don';t know why this is happening, but it is reeeeeeeeeallllly enfuriating. I have stopped making beats until someone can clarify what this might mean. Spoke with akai forever and they were baffled. Does anyone have any idea how I can remedy this terrible situation?
Regards,
Boom Baptist

Hi there,

Can you give me some more info on this one?

– Important: does this happen on converted samples or are you using self made samples etc.? I mean, where are the original samples coming from?

– I know it sounds like "I don't believe you" (I do), but can you give a step by step process how to recreate this bug?

Boele

MPC-Tutor wrote:Another bug:

Record a sample in your MPC5000
Go to TRIM and set a start point of 0
Go to LOOP
Unlock the start point padlock
Set a new Lp start point of whatever, say 100.
Now hit WINDOW for the Loop Fine screen
The start point shown is 0, not 100. Editing this '0' changes the TRIM start point, not the loop start point.

Conclusion: In LOOP, pressing WINDOW does not show the 'loop' fine screen, you instead see the 'trim' fine screen.

Confirmed.

For some obscurs reasons some tracks stop working randomely on my MPC.

If i reboot it everything works fine ...

Hey yall.
I am facing a terrible bug right now that is absolutely stopping my workflow. In trim mode I will cut a sample down, go back to the main screen and press the sample and often it will either not play, because the trim has been changed by some other force, or the start and end points will have changed. Often it will say that the start point is -31,000 for example...I have no idea what that even means, but I know it's not normal. Also, I will fix all the start and end points ion trim and save, and when I load the project again, many of the same samples that were changed will be messed up again. I don';t know why this is happening, but it is reeeeeeeeeallllly enfuriating. I have stopped making beats until someone can clarify what this might mean. Spoke with akai forever and they were baffled. Does anyone have any idea how I can remedy this terrible situation?
Regards,
Boom Baptist

Yesterday i was working on a track & had the same bug.

I though it was a mistake so i didn t pay much attention.

I was working with some 16 bits wave loops when it happenned.

tomazzzi wrote:For some obscurs reasons some tracks stop working randomely on my MPC.

If i reboot it everything works fine ...

Can you give a more precise description? "tracks stop working" is a bit vague
Are they playing but not sounding? If so, did you do anything specific before that? (using mute or solo buttons for instance)?

Can you give a more precise description? "tracks stop working" is a bit vague

Yeah i know but i can t really give an exact procedure on how to reproduce it. :S

All i know is several times i had a non working track ( not sounding even with a program assigned, not responding to pads )

It always happenned to me on a new track ( unused ).

After a reboot & reloading of the project the track worked fine ...

I ll try to make a video next time.

tha wrote:Hey yall.
I am facing a terrible bug right now that is absolutely stopping my workflow. In trim mode I will cut a sample down, go back to the main screen and press the sample and often it will either not play, because the trim has been changed by some other force, or the start and end points will have changed. Often it will say that the start point is -31,000 for example...I have no idea what that even means, but I know it's not normal. Also, I will fix all the start and end points ion trim and save, and when I load the project again, many of the same samples that were changed will be messed up again. I don';t know why this is happening, but it is reeeeeeeeeallllly enfuriating. I have stopped making beats until someone can clarify what this might mean. Spoke with akai forever and they were baffled. Does anyone have any idea how I can remedy this terrible situation?
Regards,
Boom Baptist

Dang... I thought I was trippin last week and this weekend when I was saving samples and programs, and they would still be messed up....

tomazzzi wrote:For some obscurs reasons some tracks stop working randomely on my MPC.

If i reboot it everything works fine ...




Yesterday i was working on a track & had the same bug.

I though it was a mistake so i didn t pay much attention.

I was working with some 16 bits wave loops when it happenned.

Had this issue as well.... or sometimes, if you just keep messing with it, it might end up working





Also, another bug, sometimes, every sample in every program would be keyed up a step automatically... and would play slightly faster since they are keyed up half a step

Man i'm glad I chose to sit this round with Numarks first attemt on building on the history of the MPC line. seems like Numark may have bit off more then they could chew..How often are you guys unable to work because of these issues? Seems to be quite a bit.. Scd, when numark took over, did they keep the old tech squad or did everybody get ousted?