JJ OS Bug Reports (ARCHIVE)

stan steez wrote:Today it happened that - even though [WHOLE] fur Tune was selected - only the pitch of the currently hit pad could be changed. I exit GPE, then tried it again and it worked as supposed again...

WHOLE is a bit buggy, if a pad is hit, the whole selection at that time is lost temporarily as the pads' selected.

whole is only active on all pads when re-selected.

i'd pay an extra 10 bucks for a real working MTC implementation . maybe if homeboy focusues on fixing what's already there before adding new features....i know its a completely crazy thought..

e.g. in GPE :

Pad:A01
Layer sample v range
1: sound1 127-101
2: sound2 100-50
3: sound3 49-0


1.enter trim edit:
2.pgm mode:ON
3.hit pad with layered samples. (e.g. pad: A01 as above)
4.sample waveform changes when you hit at different velocities
5.sample name doesn't change when you hit at different velocities
bug: trim pgm mode: Sample name doesnt change with sample layer, only layer 1 sample name is shown.

edit: forgot to say this was os2 1.13, although it should be obvious for because its about trim/program mode.

sadly i think theres already a bug in here;

TRIM + "PgmMode" [F1]........"zoom in" [F3] is lost when a pad is struck.

ie: if you're in TRIM, and are using the new PgmMode, any recent zoom setting is immediately reverted to normal as soon as any pad is activated.....

i imagine its something to do with the os now having to 'consider' the samples in relation to pads, and losing the plot somewhere else.

os 2 1.13
click sample bug

1.Enter Click screen
2.Change accent/normal to "sample"
3.select sample
4.enter main screen
5.re-enter click screen
BUG: accent/normal is now assigned to different sample(s)

note: no bug when accent/normal is set to CLICK.

DOUBLE NOTE: just tried to recreate this and everythings behaving normally! weird??

..and now ive loaded up a different folder and its doing the bug again..hmmm

still 1.13
ok i think ive managed to narrow down the click bug from above.

1.assign click to sample.
2.go in/out of click screen
no bug:click sample stays the same

3.Load up a folder (which doesnt contain click sample). F2 CLEAR
4.click samples are missing.
5.reload click sample and assign to click.
7.go in and out of click screen.
8.BUG: click sample changes.

ALSO: at step 3: reload sample instead of loading an entire folder: BUG is still there
click sample changes every time you re-enter the click screen.

it seems to start at the end of the list and work its way backwards everytime you go out and back into the click screen.
if anyone checks this let us know,
thanks!

OS1 4.99h and OS2 1.14:

-When chopping a drumloop into 64 slices, the last slice is to short.
Record drumloop-set start and end ponits-chop-slice-slice to 64-edit-F2-release 0-create new program yes. Result last slice to short.

-Only a limited amount of sound files are showed in the trim section, but you can load more into the mpc. When saving the entire memory it will only save the soundfiles that are shown in the trim section. The other soundfiles, that are in the mpc, are not saved.

(I have emailed these bugs several times to the creator of the JJOS, but no fix yet. This sucks.)

-When you record Q-link (realtime-tune-track) movements into the track (eg track 1) of a sequence and then change to an other sequence the tuning of the samples in the new sequence track 1 is changed. Very anoying in life situations. I have only tried this bug with OS1 4.99g not with the 4.99h version and OS2.

If this can be fixed I will be a happy user of the JJOS.

Can people reproduce these bugs? Or am I the only one with this problem?

Patat Met wrote:OS1 4.99h and OS2 1.14:

-When chopping a drumloop into 64 slices, the last slice is to short.
Record drumloop-set start and end ponits-chop-slice-slice to 64-edit-F2-release 0-create new program yes. Result last slice to short.

Fixed.
Thanks.

I've got a strange bug right now..

it's like there's a ghost in the mpc or some maniac hitting my pads as a possessed..

under the ''pgm'' all samples are flying over the screen in a furious fast tempo
and also the notes under ''drum'', exact the same..

what i tryed to stop this is;
-turn off and on
-usb cabel dissconnect
-power cabel dissconnect
-new JJ OS 2 installed (i had 1.15, now installed 1.16)

but still the same damn shhit

*edit, the machine does this on his own, i haven't touch it.
from time till time it takes a break on a12, and it goes further..
also in OS 1


** edit, bad pads i think

i tryed different pads but still the nightmare continues

When Recording Midi Random E3 Notes are placed in the seq.

First time i'm trying this so I'm not sure this is a bug, with os2 1.17 in a midi track can you manage to press do it or all track when you choose TC OFF ?

effect reset bug: found in phaser

when using a couple of different effect sets....like this:

effect set 1, reverb(1)&phaser(2) - with a phaser sweep rate = 30
effect set 2, phaser(1)&delay(2) - with a phaser sweep rate = 66

when effect set is changed manually or by an "effect" event entry in step edit, in this case the phaser sweep rate remains at last value, and does not update to use the value previously assigned in its effect set.

eg: as above - if i switch from effect set 2 into effect set 1, the phaser sweep rate does not change from 66 to 33, but remains at 66 and is audibly sweeping at 66, yet the display shows 33......that is until the value is adjusted by the user with the cursor/data wheel.

anyone get this?

[i really thing its something to do with the two different phasers being not in the same fx'slot' (ie: not both phasers in slot 1 or slot 2 exclusively).......im thinking that if i'd had the phasers in the same 'slot' the old values are really replaced with the new values, but as they're not in the same slot in my example, the value update gets messed up.]

hi, ive found a bug re: (mode:other:master level) and (input thru:level) - does not correspond

when 'Input Thru' is 'ON', (in this case; ANALOG, L+R input) Level=100.
If the 'Master Level' is changed (mode:other:global) Example : from 0dB to -42dB, reducing overall output volume to 0....

BUG - the 'Input Thru' level remains audible at full level, and is not reduced corresponding with the 'Master Level'.....until the value of 'Input Thru' level is touched by any value change, as soon as this value changes the 'Input Thru' level now corresponds with the 'Master Level'.... in this case, all the way to 0.

BUG - if the 'Master Level' is then turned up from -42dB to 0dB, (and the 'Input Thru' level was 100, but was audibly silent due to the 'Master Level' being previously '0') the 'Input Thru' level remains audibly silent.