JJ OS Bug Reports (ARCHIVE)

Got a response from Murai about the graphic bug, he told me to press ERASE when booting up even if you switch from OS1 (which I think is very inconvenient).

juno 106 still not working properly with xl . still stops samples from other tracks
when i push the keys, regardless the midi settings i have tried ...
same thing goes with all the jjos´s and also akai os´s .. im gettin frustrated..
do you guys think that theres something wrong with my mpc
or is it just os bugs??? all the midi ports seem to work , and this same
setup worked fine with 2000classic.. not to mention that my oxygen8 doesnt work
at all with 1k ..

OLD SIMULT > NEW SIMULT.

1.The UNDO feature erases more than one backward.
2.When loading program folders, it allows you to load too much then when playing the program samples, a question mark appears before the sample name with no sound.

example:

A01 ?kick
and either no sound or a click

Problem with sustain pedal (CC #64). OSJJ 1 - 4.99.

1) I press a MIDI keyboard note down (a looped note)
2) It sounds
3) I press the "sustain pedal" down
4) I release the keyboard note
5) The sounds is still ON : OKAY
6) I release the "sustain pedal" (up)
7) Sounds is still ON : BAD (((( Why is it so ?

I tried YES and NO [MODE][PAD 10][MISC][SUSTAIN PEDAL...]
but it is the same !

JJ OS 2XL 1.06
Mute groups not working properly.

1. Activate any mute group pair (example below) in a program on track 1.
2. Program a sequence using these sounds.
3. Play sequence.
4. Change active track to any other than the one with the mute groups. Also chose another program or no program for this track.
Mute groups will stop working.

Same problem when using target.

Mute group example:
ClosedHat on A01, OpenHat on A02.
Set both to same mute group (Mode+Pad7; Screen: Mute; Column: Group).
A01 will silence A02 just lite a real hihat.

alamin wrote:Problem with sustain pedal (CC #64). OSJJ 1 - 4.99.

This is not a JJ OS bug. It's the same with all MPC1000 regardless of OS. JJ OS has never mentioned any solution to this, neither has Akai.

The only solution I know of is using an external keyboard that converts CC64-up to midi-off for all active notes. I have a patch for the Nord Modular G2 that does this.

The only solution I know of is using an external keyboard that converts CC64-up to midi-off for all active notes. I have a patch for the Nord Modular G2 that does this.

Hello, that's not a solution, is it ?
Imagine you "hold" a chord, and you release the pedal-up, then all the notes
will be off ??!! and so : no-sound ?

A technical solution to this problem is not so complicated to program, I'm sure.

JJ OS2XL 1.06

1) Mode + Pad 8 to enter mixer
2) F5 to enter input through
3) Pressing F6 will not go to FX screen

JJOS2 v1.22: 16 levels, affects aftertouch/ layers x-fade.

get two samples,
put both on same pad, (samples on layers 1 & 2)
set aftertouch>x-fade 1&2 to on, 100%. (pressure 0-100 will cause the layers 1 & 2 to x-fade)

BUG:
get 16 levels on,
select the pad to do 16 levels /tune for example.
play that pad with aftertouch movement/pressure - aftertouch works (layer x-fade works)

BUT, play any other pad in the 16levels/tune set - aftertouch does not work (only one layer plays)

OS2 v1.22

BUG: Track Mute mode, an Active track doesn't record Q1 realtime movements when "After" is used to replace existing recorded q-real data.

even when the track is made "Active" in Track Mute Mode, Q-Real recording will not occur.

only when the main screen is used, does the "After" button allow q-real overdub recording over previous material.

OS2 v1.22 BUG: Q-real in Grid Edit

BUG:

in Q-Real Grid Edit, "REC"+"PLAY" while erasing ONLY Q-real data, it does not fully re-record over previous note/seq/track data as i would expect .

it behaves more like "OVERDUB"+"PLAY", by only allowing overdub recordings of pad events etc... to occur.

this isnt completely undesirable (it is after all the Q-real Edit page, so mbe it only focuses on Q-real events here, its just more inconsistent, as the transport buttons are lying to us at this point.

EDIT: i'm now thinking this is intentional, for grid/qreal edit - just to be used to record re-record q-real events, while preserving the tracks midi/note/pad content.

im hoping after all these bugs are reported, they'll forget about XL for a bit and tidy up their plush condo/OS2.

instead of building their adjoining garage made of asbestos and fecal horse hair next door.

they said the same callous sh!t about os2 last year...now look at it

they!, I said it,

and it was A _ YEAR! i'm sure XL will be XtraspeciaL one day, but again were here getting toasted by the beta development, meanwhile trying to get on with a full day & nights worklife on the MPC.

me i'm def gonna keep with the most stable, comprehensive solution, at the mo' its OS2, all in all.

i paid for XL, i believe in JJ for that matter - and i feel i can say stuff that may appear unfair to others, but its not unfair from my perspective. i'm sore at the recent very public ditching of the older OS's by JJ........i mean i just hope they continue to fix bugs.