OS 1.01 Bug Report

How often are you guys unable to work because of these issues?

never

No bug is stoping me to work ....

Just depends on if its on its period that day... Sometimes it can keep up the workflow, sometimes it cant.

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.

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.

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.




****UPDATE****
Not a bug. Solution found in the manual p 73.

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.

Try to re-think what you did: sending out a "mute event" to a midi channel. It doesn't matter on which track you do that as long as every track is sending out it's events to the same midi channel. (Morpheus asks: If you try to ride the same three cars at the same time and die while crashing with one...could you live on in the remaining two?) Maybe the tracks sync themselves to all midi events they share.

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.)

#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.

#3: I bought a sample AKAI library containing .S1S-files but I can't load them

Onkobu wrote:

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.

Try to re-think what you did: sending out a "mute event" to a midi channel. It doesn't matter on which track you do that as long as every track is sending out it's events to the same midi channel. (Morpheus asks: If you try to ride the same three cars at the same time and die while crashing with one...could you live on in the remaining two?) Maybe the tracks sync themselves to all midi events they share.

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.

Askia Shaheed wrote:

Onkobu wrote:

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.

Try to re-think what you did: sending out a "mute event" to a midi channel. It doesn't matter on which track you do that as long as every track is sending out it's events to the same midi channel. (Morpheus asks: If you try to ride the same three cars at the same time and die while crashing with one...could you live on in the remaining two?) Maybe the tracks sync themselves to all midi events they share.

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.

The other MPC's dont work this way... I discovered that as well a while ago playing with a Piano in Reason, while doing different piano parts, usually it just silents those particular notes. But the 5000 silences the whole Channel.

I run into so many problems when im working, I dont remember em until Someone else may talk about an issue. At the moment, when im in the middle of a song, i dont have time to write the issue down when im trying to meet a last minute deadline. But that is one of the things that I did find before.

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.)

#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.

#3: I bought a sample AKAI library containing .S1S-files but I can't load them

You might wanna try to upgrade to the new OS first and then make sure that its still a bug.

im pretty sure, if you are trying to import the .S1S files, that still might be an issue, because you can import some of the other Akai MPC files

#3: I bought a sample AKAI library containing .S1S-files but I can't load them

If i remember well those files are not in the compatibility list ...

tomazzzi wrote:

#3: I bought a sample AKAI library containing .S1S-files but I can't load them

If i remember well those files are not in the compatibility list ...

well, theres your answer

JOG WHEEL ISSUE:

When turning the jog wheel (e.g. assigning samples to program, changing mixer settings like pan etc), I'd say approximately 1 in 4 jog wheel 'ticks' go unnoticed at best - this is truly annoying and adds to the sluggish feel of the 5000. Not sure if this is an OS issue or (hopefully not) a hardware issue. In fact in the mixer screen, if I select 16 pads at once and try to increase the effect send level for all pads, I'd say only 20% of the jog wheel turns are actually registered.

EDIT - jog wheel works fine when running through the 'effect select' list or when using the jog wheel to change an effect parameter setting, so can only assume the missing ticks in certain screens is another OS issue.

MPC-Tutor wrote:JOG WHEEL ISSUE:

When turning the jog wheel (e.g. assigning samples to program, changing mixer settings like pan etc), I'd say approximately 1 in 4 jog wheel 'ticks' go unnoticed at best - this is truly annoying and adds to the sluggish feel of the 5000. Not sure if this is an OS issue or (hopefully not) a hardware issue. In fact in the mixer screen, if I select 16 pads at once and try to increase the effect send level for all pads, I'd say only 20% of the jog wheel turns are actually registered.

EDIT - jog wheel works fine when running through the 'effect select' list, so can only assume the missing ticks in certain screens is another OS issue.

Folks, I'll check all the newly posted stuff here soon and will enter it in the bugbase/feature request list if confirmed/logic.

scd wrote:Folks, I'll check all the newly posted stuff here soon and will enter it in the bugbase/feature request list if confirmed/logic.

Whats up SCD? Glad to see ya back....

Any idea on the new OS update yet, timeframe wise?