JJ OS Bug Reports (ARCHIVE)

Bug in mpc2500_xl213.osx

1. Go to Song mode.
2. Press Full Level while playing a song.
3. Current sequence moves to Step 1, just like pressing Play Start.

At 234 bpm with a 8/32 time signature the autobar can't go backward.

Otherwise I was wondering if what I'll describe below is a normal behavior or not.

I edited some parameters on a pad in step edit and I wanted to copy them in another sequence but in the same track (not replacing the whole track).

The options in the SEQ EDIT mode are :

-REPLACE : only the copied pad information remains

-MERGE : the pad information is copied but it does not overwrite the already existing information on that pad located at the same time position.

So finally I got the copied events located at the same time on the time display.

Well thinking about how to write that post made me think it would be cool to request a MERGE+REPLACE feature.

le rat wrote:Well thinking about how to write that post made me think it would be cool to request a MERGE+REPLACE feature.

I know what You mean, it would be usefull.

I just reported a bug which I think was there since first versions of xl. When You put the same sample on layer or simult without velocity switch to play them together, You get random flange which is very noticable. I sometimes hard pan the same sound in mono and than change filters and attack on separated LR channels.

^ this has always been the case, even in the akai os days
it's because the mpc is sample inaccurate.

yeah that's why resampling internally can be very useful.

Bugfix wrote:I just reported a bug which I think was there since first versions of xl. When You put the same sample on layer or simult without velocity switch to play them together, You get random flange which is very noticable.

i love that 'bug'! random flange!

it sounds great when you simult a sequence with itself (as long as the program/samples are set to POLY and not MONO).

Nym wrote:^ this has always been the case, even in the akai os days
it's because the mpc is sample inaccurate.

yeah, I even checked os1 & 2, BTW when I put os1 it was like.. OMG!

Sooty_G wrote:i love that 'bug'! random flange!

ah, ok I can live with that LOL , it's not very noticable on discrete sounds

Thanks for reply

Bugfix wrote:

Nym wrote:^ this has always been the case, even in the akai os days
it's because the mpc is sample inaccurate.

yeah, I even checked os1 & 2, BTW when I put os1 it was like.. OMG!

Sooty_G wrote:i love that 'bug'! random flange!

ah, ok I can live with that LOL , it's not very noticable on discrete sounds

Thanks for reply

Yeah, always been that way.. even with akaios. If you listen though the sounds either play together or are offset by exactly the same amount. I mean, the offset is a constant value (with simult at least), but it's random when it happens. I've always thought it strange that if the offset is a constant then how come it can't be fixed.

Out of curiosity I was wondering...Does it happen with MPC which are supposed to have a better clock like the MPC4000 and the MPC5000?

ver2.14 2500 JJ OS-XL

a small bug.


loading a sample.
mode + 6 (trim)
F4 (loop on)
pressure pad7 (reverse) and holding it, turn data wheel.

bit of a weird one ive sent to jj, this is exactly what i do to cause the problem but it might behave like this in other situations too:

2.13
midi in duration bug

quantize=on
loop = 1-8 (8 bars)

1. press overdub & stop (midi wait)
2.hit pads & record sequence
3.seq loops - overdub starts
4. turn off overdub
5.change loop length to 1-4 (4bars)
6.turn overdub on
7.record notes from midi in device (play with short duration e.g. 6-7 ticks
8.stop sequence
9. bug : note durations at bar 2.1.00 and 3.1.00 are very long (other note durations are ok.)

note:
when quantize= off durations are ok e.g. 2.1.01 : note duration is ok

Found a bug in mpc2500_xl214.osx - again related to the Full Level button!

1. Go to Song mode.
2. Press Full Level while playing a song.
3. Current sequence starts looping.

Running JJOSXL 2.15

-Recorded an audio track using my synth (on track 64)
-then (without deleting the track)
-changed the track type to 'drum' and recorded newly created audio track as drum data.
-immediately after recording drum data the MPC reboots. tried this twice, same issue.

-when recording audio track and deleting track once done, then changing track type and recording the audio track as drum data MPC does not restart.

About audio tracks I've noticed a workflow issue.

Let's say you start recording at bar 32
Let's say you stop the recording at bar 36

If you're not satisfied with the recording and press the UNDO button
Next time you'll press REC + START the recording will start at bar 36

It makes the workflow slower and it would be better if after pressing the UNDO button the MPC would return at the bar position you started recording.

le rat wrote:About audio tracks I've noticed a workflow issue.

Let's say you start recording at bar 32
Let's say you stop the recording at bar 36

If you're not satisfied with the recording and press the UNDO button
Next time you'll press REC + START the recording will start at bar 36

It makes the workflow slower and it would be better if after pressing the UNDO button the MPC would return at the bar position you started recording.

Thanks for finding that. It definitely needs to be changed.