JJ OS Bug Reports (ARCHIVE)

os2xl 3.05 - decay does not show up in NV list in grid mode, unless it has been recorded using the q-link. About to install 3.06 so disregard if that's been fixed.

here we have two folders for reporting bugs in 3.06
http://ul.to/2sg9yv8d
1) images of empty cells ( 1 buggy).
2) Please load the project, press play and what you hear? ( 2 bar buggy ?) why?

so uhh... how do I get to the SAVE screen when I'm in this mode?


I thought I was having some weird errors with pasting before that, the last beat missing from a bunch of tracks, but I can't be sure that wasn't my fault.

I think I found a bug with the Purge function.

LOAD two programs with samples
Create a new DRUM program
Put loaded samples on that new program
Go to the program list
Delete the old program with sample purge : NO
Go to MAIN
PRESS a pad and window over a sample name
Press PURGE
Back to main
=> bug at the program level i.e. wrong sample at the wrong place

I'll report it and see what they gonna say. It's not easy to reproduce by the way.

. It's not easy to reproduce by the way.

I was in the jungle v3.06 for 2500 and great things were happening, like bugs, the type max / msp (improvised ) that I could not describe ( man vs. machine) sorry guys. But it was something related to : layer .

Yeah it's hard to track when it's a random bug.

Another strange thing . Every time I press the STOP button , the same sample was heard.
How ?
I do not know.

Found a bug in 2.30. Read the 3.xx Bug fix list, it is not mentioned there.
So, if somebody would like to check if it still occurs in 3.06, I could report it to JJ then.

Both 2.30/3.06 manuals say in "Behavior selection of the Next sequence" section:

"Note
Selection of behavior can be performed during playback of a sequence.
Moreover, it can select on the screen of NEXT SEQ and TRACK MUTE."

Bug:
In NEXT SEQ screen, cursor can not be moved to "behavior of Next Sequence" field during playback. If the cursor is in "behavior of Next Sequence" field when playback is started, cursor jumps to Sq: field.

I think I found a bug with the Purge function.

LOAD two programs with samples
Create a new DRUM program
Put loaded samples on that new program
Go to the program list
Delete the old program with sample purge : NO
Go to MAIN
PRESS a pad and window over a sample name
Press PURGE
Back to main
=> bug at the program level i.e. wrong sample at the wrong place

I'll report it and see what they gonna say. It's not easy to reproduce by the way.

It has been finally identified. It will probably be fixed in a next update. A concise formulation could be a sample was assigned if the sample list window was left with the main or window button.

re-creatable freeze

1) load a project with 2 or more sequences.
2) select midi channel field
3) start playback
4) press and hold NEXT-SEQ and try to rotate the wheel

at this moment my mpc freezes.

2500 xl 3.06

1. Create sequence "Bars: 8"

2. "Lp: 7 - End"

3. Change "Bars: 2"

4. "Lp: 7 - End" still displayed.

5. Press play. MPC freezes.

consuming wrote:2500 xl 3.06

1. Create sequence "Bars: 8"

2. "Lp: 7 - End"

3. Change "Bars: 2"

4. "Lp: 7 - End" still displayed.

5. Press play. MPC freezes.

just tried that on my mpc1000, it freezes when it gets to the end of the second bar.

Other bug in 3.07

http://www.youtube.com/watch?v=9qXvoTW4Uto

BYE!

full memory bug:

1)Turned MPC1000 on.
2)128MB free memory
3)recorded a percussion loop in looper mode ( just a few bars), assigned to a pad
4)back to main mode. Hit the pad to hear the percussion looping to record a midi track to it
5)try to record into midi track, MPC says "MEMORY full"