MPC-Tutor wrote:Better add this as per my separate post:
In TRIM > CHOP, there is no option to 'fine' edit regions like there is on the 2500 (e.g. select region 2, select the end point, hit WINDOW for the 'fine' screen). So no way to zoom in on start or end points and hence no way to make an exact edit.
Perhaps not a bug as the manual doesn't mention this feature even being there, but still a major oversight and something that should be added back into the core OS.
Askia Shaheed wrote:I am not sure if this qualifies as a bug but it did have been scratching my head for a minute. If the MPC 5000 is low on sampler memory, the time stretch function will not work. You can attempt to execute a time stretch but nothing will happen. I think an appropriate response should be a message to indicate that there is not enough memory to perform this function.
mmcerda wrote:Hey I don't know if it's a bug but if I have a program loaded with loops and I press one of the pads the loop will sound as long as I keep the pad pressed.
If I release it, the loop will stop. But if I press the pad with the loop, and then I press the Track Mute Button, I can let go of the pad and it will keep on playing until I press the same Pad again.
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
Askia Shaheed wrote:Another MIDI bug?
1. I assigned track 1, 2, and 3 to MIDI channel 1 which will playback Reason's Redrum, which I have a drum kit loaded
2. I recorded KIKs on track 1, snares on track 2, and hi hats on track 3
3. Next, I went into Track Mute
4. When you mute Track 1, it will also mute track 2 and 3.
So if you have a MIDI channel assigned to a track and turn on Track Mute, it will mute every other track that uses the same MIDI channel.
Onkobu wrote:I have some new bugs, not mentioned in the bug reports:
#1: I loaded a sample (4 bars, 120bpm), invoked time stretch and replaced it with itself...sample turns into total silence and assigning samples to pads in program mode is broken (while turning data wheel down it stops at 'no sample', in the other direction it runs over the last sample and starts displaying the first sample. The broken sample can't be chosen.)
Onkobu wrote:I have some new bugs, not mentioned in the bug reports:
#2: Decimator and Reverb (Small) on bus 1+2, playing with Decimator's settings (heavy downsampling) - whole main bus becomes silent, sequencer still playing, no sound until reboot.
Askia Shaheed wrote:
I was thinking the same thing which is the reason why I put a question mark.....
I can't remember if other MPCs work the same way. If this is the case, I was wondering if it is possible for TRACK MUTE to submit a MIDI VOLUME CHANGE of 0 to ALL events on the track instead of muting the entire MIDI channel. That way it will not impact other tracks assigned the same MIDI channel.
MPC-Tutor wrote:Better add this as per my separate post:
In TRIM > CHOP, there is no option to 'fine' edit regions like there is on the 2500 (e.g. select region 2, select the end point, hit WINDOW for the 'fine' screen). So no way to zoom in on start or end points and hence no way to make an exact edit.
Perhaps not a bug as the manual doesn't mention this feature even being there, but still a major oversight and something that should be added back into the core OS.
MPC-Tutor wrote:Saving bug:
Create a new sample by any method (e.g. via RECORD, or by editing or copying an existing sample)
Go to DISK > SAVE > Save a sample
The sample you created previously is not available in the list of samples that can be saved
The workaround is to first change 'Type: SAVE A SAMPLE' temporarily to something else, e.g. 'SAVE A PROGRAM' and then go back to SAVE A SAMPLE.
Conclusion: the MPC5000 doesn't automatically refresh the active sample list when you return to the SAVE screen, so you have to force it to.
scd wrote:This works fine here.
I startup without outload and record three samples in REC SAMPLE mode by using the record button
So three times the sequence RECORD - START - STOP - KEEP
Then I go to DISK - SAVE and all three new samples are there.
MPC-Tutor wrote:scd wrote:This works fine here.
I startup without outload and record three samples in REC SAMPLE mode by using the record button
So three times the sequence RECORD - START - STOP - KEEP
Then I go to DISK - SAVE and all three new samples are there.
Hmmm, I re-booted the MPC5000 and cannot recreate this bug anymore. It was definitely doing this during my previous session, so there must be something setting this off - it didn't matter if the sample was recorded or just created via editing an existing sample (e.g. STEREO > MONO). I will investigate further to see what triggers it.
