OS XL bug thread

1) press MODE + PAD2
2) select program file *.PGM
3) press DO IT
2) press MAIN
3) BUG: If hitting the pads before doing anything else, screen jumps to LOAD MODE again

This doesn't happen everytime, but it is quite reproducible.

not really a bug, more something that has been missed, but:

midi devices - from a1 to b16 can be named, nothing after that. even though you can set c1 - d16 midi channels

(to be honest, the naming itself is nice, but lame - why not just one name per midi item, rather than needing to put input say 'juno' 16 times)

Oh man
there many bugs in there.
here the biggest one:

you cant hear loops to audition in the load mode.
only 0.1 seconds.

We are all BETA users !!!

MPC2K500 wrote:Oh man
there many bugs in there.
here the biggest one:

you cant hear loops to audition in the load mode.
only 0.1 seconds.

We are all BETA users !!!

That has to be a joke - right?

(to be honest, the naming itself is nice, but lame - why not just one name per midi item, rather than needing to put input say 'juno' 16 times)

reason, multitimbral modules, and vsts - different instrument per channel

NorthernElite wrote:

MPC2K500 wrote:Oh man
there many bugs in there.
here the biggest one:

you cant hear loops to audition in the load mode.
only 0.1 seconds.

We are all BETA users !!!

That has to be a joke - right?

No Joke

But here is the Fix:
------------------------------------------
Bug Fixes: XL Ver1.01 17-JAN-2009
------------------------------------------
1. [LOAD]

F5[PLAY]
Audition does not work.

2.[PROGRAM]

F2[FILTER]
Behavior of cursor is strange.

MPC2K500 wrote:

NorthernElite wrote:

MPC2K500 wrote:Oh man
there many bugs in there.
here the biggest one:

you cant hear loops to audition in the load mode.
only 0.1 seconds.

We are all BETA users !!!

That has to be a joke - right?

No Joke

But here is the Fix:
------------------------------------------
Bug Fixes: XL Ver1.01 17-JAN-2009
------------------------------------------
1. [LOAD]

F5[PLAY]
Audition does not work.

2.[PROGRAM]

F2[FILTER]
Behavior of cursor is strange.

Thanks - caught that on the JJ site this morning.

Still haven't had a chance to throw XL onto my 2.5k yet - at least it's been fixed quickly though

Nym wrote:

(to be honest, the naming itself is nice, but lame - why not just one name per midi item, rather than needing to put input say 'juno' 16 times)

reason, multitimbral modules, and vsts - different instrument per channel

jeez, are there still people out there using computers??!

i'm a newbie in the mpc2500 jjos2xl so sorry if i'm doing something idiot...
i found a strange behavior in the trim fonction here is what i've done :

1. i imported in the mpc a 37 Megs wav song
2. load it from the compact card
3.mode TRIM selecting the big wav file
4.turn CHOP to ON
5.hit the pad to set the start an end poind of chop 1, chop 2 ....
6.when using the data wheel to set the start if i push the pad simultanously with turning the data wheel, I HAVE ANOTHER SLICE OF THE SAMPLE WHO IS PLAYING DIFFERENT FROM THE ONE I'M WORKING ON !!!

did i do something wrong or is it a bug ?

thanks in advance for your advices.

genko wrote:i'm a newbie in the mpc2500 jjos2xl so sorry if i'm doing something idiot...
i found a strange behavior in the trim fonction here is what i've done :

1. i imported in the mpc a 37 Megs wav song
2. load it from the compact card
3.mode TRIM selecting the big wav file
4.turn CHOP to ON
5.hit the pad to set the start an end poind of chop 1, chop 2 ....
6.when using the data wheel to set the start if i push the pad simultanously with turning the data wheel, I HAVE ANOTHER SLICE OF THE SAMPLE WHO IS PLAYING DIFFERENT FROM THE ONE I'M WORKING ON !!!

did i do something wrong or is it a bug ?

thanks in advance for your advices.

This "bug" is happening in OS2 too when you're using the NDC mode.

Has anyone else noticed that when you go to the Grid edit screen, that when you press pattern and then view, it shows the pattern that you did (and the velocity, sift, and duration functions) but the sound of the sample that you want to edit is gone?

Pi-Pol wrote:

genko wrote:i'm a newbie in the mpc2500 jjos2xl so sorry if i'm doing something idiot...
i found a strange behavior in the trim fonction here is what i've done :

1. i imported in the mpc a 37 Megs wav song
2. load it from the compact card
3.mode TRIM selecting the big wav file
4.turn CHOP to ON
5.hit the pad to set the start an end poind of chop 1, chop 2 ....
6.when using the data wheel to set the start if i push the pad simultanously with turning the data wheel, I HAVE ANOTHER SLICE OF THE SAMPLE WHO IS PLAYING DIFFERENT FROM THE ONE I'M WORKING ON !!!

did i do something wrong or is it a bug ?

thanks in advance for your advices.

This "bug" is happening in OS2 too when you're using the NDC mode.

HI,
I've received an answer from JJ about this :

"In Non-Destructive Chop, the pad is in correspond with a CHOP number.
Therefore, even if it changes a CHOP number, pressing a pad, only CHOP
corresponding to the pressed pad is played."

do you understand the meaning ?
i'm french and my english is maybe poor ... i don't get it

its a real disappointment that the x0x style grid edit/loop edit has gone - surely this can't be difficult to implement. will this ever return?

genko wrote:"In Non-Destructive Chop, the pad is in correspond with a CHOP number.
Therefore, even if it changes a CHOP number, pressing a pad, only CHOP
corresponding to the pressed pad is played."

do you understand the meaning ?
i'm french and my english is maybe poor ... i don't get it

it means if you press pad A1, it plays chop 1. If you press pad A2, it plays chop 2. If you press pad A16, it plays chop 16. If you press pad B1, it plays chop 17... etc.

thank you for your answer
that's what i though first but i don't see how this explains the bug that i have in os2xl OS.

maybe JJ didn't understand that i was wondering why a sample is always playing in NDC mode when you hit a pad and turn the data wheel at the same time. I mean a sample that's is not corresponding to the chop i'm triming...

and this bug is not happening when you trim in a program... and when you trim with the QLINQ.

is it possible to change the value of the sliders for setting start and end points ?
i found it to important to trim correctly, this is not precise...

thanks for your advices
peace