JJ OS Bug Reports (ARCHIVE)

BUG: drum grid edit: shift+cursor (move to next note) causes a grid to become strange.
1- load a program
2- enter drum grid edit
3- zoom so that not all bars are visible
4- record a performance
5- from 1.01.00, hit SHIFT and the RIGHT CURSOR button. continue to move to consecutive recorded notes until the end of a sequence.
6- BUG: a grid display is strange. cursor moves into the TRACK DATA column on the left.
7- set bar count to 18
8- zoom all the way out
9- return to 1.01.00
10- hit SHIFT and the RIGHT CURSOR button.
11- BUG: a grid disappears.

Nym wrote:bug: TRIM; hitting LOOP does not cycle to LOOP, ALT LOOP, LOOP OFF.

I noticed this and was hoping the procedure had not changed. I love how it worked before...

meeeeee too.

I've just messed with tc strength and it's quite buggy. os2xl 1.0

context : making a 4 bars drum pattern which consisted in boom boom bap boom bap with a 1/8 hi hat swing 61%.

Whatever the original TC strength setting if you change the strength it's ending in one bar and a half only playing, half a bar playing or just the first kick playing. So it's a random bug difficult to track down.

Second bug i have my kick simulted with a sub, while recording the simulted pad is not played.

Third observation, the grid in drum grid edit is pretty wack, bad delimited, you got big squares if you play closed pads. The grid on OS1 was far better for me.

Anybody can confirm the tc strength strange behavior before sending a report?

i don't really understand much of your reports...please give step by step reports when you post bugs.
also, only report bugs for the current version please. we're at 1.02 now.

i haven't noticed any bugs with quantize strength yet. been using it pretty heavily all day.
simult, too, so far so good.

Third observation, the grid in drum grid edit is pretty wack, bad delimited, you got big squares if you play closed pads. The grid on OS1 was far better for me.

again, please be more detailed. closed pads? os1's drum grid was unusable for me because of the lack of zoomability. i've been testing os2xl's drum grid edit thoroughly since last night and i've reported a bunch of bugs.

edit: are you referring to this bug?

Nym wrote:BUG: delete selection is very large in DRUM GRID EDIT when ZOOMED IN

1- load program
2- record a busy performance
3- enter drum grid edit
4- zoom far in
5- hit DELETE over a note
6- BUG: DELETE selection is huge. delete selection cannot be made smaller than 4 cursor wheel increments.

EDIT this is dependent on TC setting.
TC=1/8th, the DELETE block covers the whole 1/8th note.
this is lame when you're not using 100% TC strength.
"delete" should not be by block, but by NOTE/RANGE

Understood, i will try to do my best to describe the bugs i had to deal with.

firstly i upgraded to 1.02 then I loaded an old os2 beat ( the only folder i have drums in)

1. I used a random new sequence at 100 bpm 4/4.

2. The original TC settings were TC = 1/16 strength 50% and swing 61 %

I did a basic beat which structure for one bar was
K K S K S
HH HH HH HH HH

So you see it's very basic.

First thing to say, my kick simults a sub. While recording after the first cycle of 4 bars and after having played my kick, the sub is not simulted while playback and when recording still loops.

Second thing to say I tried to reduce the strength on this basic drumbeat
here is what happened reducing :

50 --> 40 made only the first kick to play
40 --> 30 made only the first kick to play without the simulted sub
30 --> 20 same
20 --> 10 first kick + sub
10 --> 0 same

You can say that i should not use strength like that but whatever settings i used it ended in problems during the playback ( sometimes it was half a bar, one bar and a half, only the first kick...etc)
I didn't try from 50 to 60, 70, 80 to 100 but the first time i had the same kind of bugs.


As for the grid edit drum layout, I wish it was the same as os1 with the possibility to ZOOM IN and OUT. Matter of preference.

I Hope it's clear now and it can help the community.

See ya later.

excellent. this helps a lot, thank you.
i will look into these.

nevermind

1.Power on
2.[shift] + [f6]
3.Input thru:on/off is highlighted
4.Turn Jogwheel right to turn on Input thru
5: Mpc crashes - screen reads... "Illegal general instruction exception
PC(eda4e138) SR(4000106b) TEA(00000000)
------stack dump (sp =88affe70)--------"
6. Happens everytime



anyone else?

I don't confirm that bug in a blank project with os2xl 1.03 on my mpc.

got a note from jj telling me to hold down erase while booting up... fixed it.

os2 xl 1.03

GPE track change name bug.
1.example set up:track 1-program1 track 2 -program2
1.enter gpe on track 1
2.press mode and move data wheel to change to track 2
3.track changes
4.BUG: sample names do not change. they are the same names as program 1 when they should be the names for program 2

note: 1 pads play the correct sound, it is just the names of samples that is wrong
2 the bug is the same when chnaging between any tracks.

sent to JJ:

this is a BUG with OS 2XL version 1.04. DELETE SEQUENCE

1. have 2 (or more) sequences loaded.

2. in MAIN screen - put cursor over SEQUENCE & press WINDOW.

3. move cursor to last sequence & DELETE IT

BUG: when a user is returned to the MAIN screen, the cursor is over the MODE area.
when the cursor is moved from this area, DRUM is automatically selected as the MODE and the sequence is recreated.
therefore, a delete is impossible.

perhaps instead:
after DELETE the cursor should be returned to the SEQUENCE location & the previous sequence selected ?

one more sent to JJ:

this is a BUG with OS 2XL version 1.04. changing a TRACK name.

1. in MAIN screen, place a cursor over the TRACK name of a track that has not yet been named.

2. press WINDOW

BUG: a character " ^ " is displayed in the place of the letter " r " in " Track "

I've just tried to make a beat with os2xl 1.04
I've found few little bugs and workflow problems.

Firstly, a graphical bug in input thru



It happens when you choose mode L R then panning L50 and R50 and finally moving the out to ST.

A bug that bothered and stuck me :

I have a one bar 9/4 chorus and in grid edit it only shows the first bars (only the first 4 ones at maximum zoom in). Moreover that makes a slight graphic bug too.

Stuff that needs workflow improvement in my mind :

When you do overd dub+rec you don't see the little screen with the counts.
When you delete events in erase mode and go back to main, it returns at bar 1.
When your in trim mode and you mess with the loop on/off button it resets the zooming.
When adjusting a loop it seems that when you press the range of pads which are not note on it seems than nothing happens when moving the end point of the loop.
IN GPE I didn't see the range for "ALL".

That's all for the moment