JJ OS Bug Reports (ARCHIVE)

Submit bug reports and feature requests for the JJOS-XL and 2XL
 Topic locked Share on Facebook

Re: JJ OS BUG REPORTS

By dtaa pla muk Wed Mar 25, 2009 2:32 pm
DRUM GRID EDIT DISPLAY:

1- load project, set bars to 8
2- create a drum track
3- record a pad performance
4- enter DRUM GRID EDIT
5- hold SHIFT and hit CURSOR RIGHT
6- BUG: grid display breaks.
7- NOTE: this does not occur in MIDI GRID EDIT.
8- NOTE: it appears that this bug creates a bug for NUDGE NOTE

v
--1: create 8 bar sequence
--2: record a performance. record a performance near 8.4.00
--3: hold SHIFT and hit CURSOR RIGHT to A, move to the note, and B, to
recreate the above bug
--4: EDIT note and attempt to nudge it
--5: BUG: a note is not nudged logically.

BUG: SAVE: >4 folders in HD/CF CARD creates problem
1- create 6 folders in HD or CF CARD
2- save a project in folder 6
3- hit MODE pad 2 and load folder 6
4- hit MODE pad 3 (Save)
5- BUG: cursor automatically moves to folder 5.
6- BUG SUMMARY: when >4 folders exist in a directory, SAVE moves to
folder -1 position.
7- DANGER: a user may accidentally save overtop another project.
User avatar

Re: JJ OS BUG REPORTS

By 16squarez Tue Mar 31, 2009 6:28 am
I can't recreate those bugs nym im on 1.13 os2xl (2500).

But i did notice that when you max out the internal memory it states
"FILE NOT FOUND" not "INSUFFICIENT MEMORY"
not really a huge deal but had me nervous about my samples.

Re: JJ OS BUG REPORTS

By dtaa pla muk Tue Apr 07, 2009 3:35 am
OS2xl 1.13

turning INPUT THRU on causes CPU ADDRESS ERROR

1- boot mpc
2- enter INPUT THRU screen
3- turn INPUT THRU ON
4- BUG: CPU ADDRESS ERROR.


very simple one
User avatar

Re: JJ OS BUG REPORTS

By elevated Tue Apr 07, 2009 1:52 pm
Nym wrote:
OS2xl 1.13

turning INPUT THRU on causes CPU ADDRESS ERROR

1- boot mpc
2- enter INPUT THRU screen
3- turn INPUT THRU ON
4- BUG: CPU ADDRESS ERROR.


very simple one


Crazy I haven't run into this... and I turn INPUT THRU on and off almost constantly. It must have to be the first thing you do to cause the bug.

Re: JJ OS BUG REPORTS

By dtaa pla muk Tue Apr 07, 2009 4:49 pm
5 minutes after i posted/sent this, jj wrote back asking if i had held DELETE while turning on the mpc...i must have missed some time when i was supposed to have done that, cuz it cleared the bug right up.

easy solution! thanks though elevated

Re: JJ OS BUG REPORTS

By dtaa pla muk Wed Apr 08, 2009 7:15 pm
BUG: ALL PAD copy/paste in DRUM GRID EDIT is inconsistant

1- load project
2- record performance in a drum track (TC 1/8)
3- enter DRUM GRID, set view to ALL PAD
4- from position 1.01.00, hold F2 COPY and hit the BAR > button.
5- BUG: cursor position = 2.01.47
6- turn TC OFF
7- from position 1.01.00, hold F2 COPY and hit the BAR > button.
8- NOTE: cursor position = 2.01.00. this is desired behavior.

*- NOTE: cursor displacement = TC value -1 tick.
*- why this is troublesome: with TC = 1/8, copy a bar and from 2.01.47 hit paste, paste, paste.
*- NOTE: copied bar "drifts" from intended position.

Re: JJ OS BUG REPORTS

By rarara Mon Apr 13, 2009 8:04 pm
undo bug. 2500 1.13

1) go onto new track
2) set to midi and choose correct midi device/channel
3) record some notes
4) using the 'undo' button removes the notes, but it also removes the midi setting previously selected for the track at step 2
User avatar

JJOS 1, 499j

By arebee Fri Apr 17, 2009 3:01 pm
JJOS1 v499j

FX send bug, FX1 to FX2 'Send : amount' not working

"FX1 type: reverb
To FX2: YES Send: *0-100"

* any change in value has no change on send levels to FX2.

Re: JJ OS BUG REPORTS

By Seneca Sat May 16, 2009 7:54 am
Sometimes, when i press the stop-button after recording a trigger-phrase, the MPC 1000 (JJ OS1 4.99) hangs and i have to power it off... that's really hard and i don't know what to do....
User avatar

Re: JJ OS BUG REPORTS

By le rat Sat May 16, 2009 3:47 pm
os2xl : a random bug which I couldn't clearly identify yet. In trim mode messing with the NDC chop ON/OFF makes it sometimes bug (it stays on OFF) and you have no other choice than reboot.

Re: JJ OS BUG REPORTS

By dtaa pla muk Fri May 22, 2009 5:02 pm
haven't had that one happen to me yet le-rat

here's my latest:

hey there, nym again. it's been a while since my last report.

here is a workflow inconsistency.

INCONSISTENCY: copy in MIDI and DRUM GRID behaves differently.
1- create a midi track
2- record a performance
3- enter midi grid edit
4- copy a 4 bar section using the <= bar => buttons.
5- paste the result.

^ this is desired behavior. now, create a DRUM track. record a performance.
3- enter drum grid edit.
4- copy a 4 bar section using the <= bar => buttons.
5- BUG: data wheel must be used. BAR buttons only allow 1 bar to be selected.

-------------

bug: mono sample will not be crossfaded in playback.

it still exists a bug where a mono sample is looped and crossfaded, but does not crossfade in the sequencer. more testing is needed. i do not use mono samples for crossfade often but this is definitely a bug.

i believe i can reproduce it: the behavior appears predictable.

1- load a mono sample
2- enter trim
3- turn sample to LOOP ON, XFADE
4- NOTE: in TRIM, crossfade works.
5- hit PGM MODE and assign the sample to pad A01.
6- in TRIM PGM MODE, play the pad.
7- BUG: mono sample is not crossfaded.

--------------------------

2nd bug: DRUM grid edit: extra space when copy/paste.

1- create DRUM TRACK
2- record performance.
3- hit f2 copy and move the data wheel so that all of bar 1 is selected
4- release f2.
5- BUG: cursor is dropped at 2.01.48 instead of 2.01.00
6- if a user were to copy, paste, copy, paste, the recorded performance would stray from where it is supposed to be.

* this is a bug i reported in my last report.

----------------------------------------------------

workflow issue: in TRIM, SCRUB does not work for END POINT.

it was discussed some months ago regarding the SCRUB of END POINT in TRIM. i still believe that it is more useful to be able to hear the SCRUB of END POINT when a user's cursor is on END POINT. users have commented on this on the forums.

----------------------------------

workflow issue: simult.

it is still discussed in the forum that the big problem with os2xl is that there is no behavior for OLD SIMULT.
users are frantic about this. it is agreed that this is a severe limitation for users who do not use additional equipment. although i use additional equipment, i agree 100% that OLD SIMULT is essential for DRUM LAYERING. OLD SIMULT is the only way for a user to achieve multiple filters/ADSR for a simultaneous pad playback. NEW SIMULT requires a good deal of re-recording and editing.

viewtopic.php?f=25&t=114727&p=1048620#p1048620
viewtopic.php?f=25&t=111976

the best scenario would be an option for NEW SIMULT mode (both notes are recorded) and OLD SIMULT mode. i do not know if this is possible.

-------------------------------

workflow request: ?+data wheel = change sequence.

"mode+data wheel = change track" is extremely useful and very very quick.
i desire greatly the addition of "?+data wheel = change sequence."
i do not know the best button for this action.
perhaps NUMERIC or REC or OVERDUB?

i know the focus is on JJ sequencer now but i can't help myself.

----------------------------

that's all - thanks for your time. i look forward to testing the jj sequencer. the forums are excited to see that mpc projects can be loaded. this will be extremely useful for users who do not have good sound cards on their computers. it is a cheap and efficient way to bring mpc beats into the computer.

nym

Re: JJ OS BUG REPORTS

By kazakore Sun May 24, 2009 10:29 am
Nym wrote:
--------------------------

2nd bug: DRUM grid edit: extra space when copy/paste.

1- create DRUM TRACK
2- record performance.
3- hit f2 copy and move the data wheel so that all of bar 1 is selected
4- release f2.
5- BUG: cursor is dropped at 2.01.48 instead of 2.01.00
6- if a user were to copy, paste, copy, paste, the recorded performance would stray from where it is supposed to be.

* this is a bug i reported in my last report.

----------------------------------------------------



I mentioned this before the last update and thought this was a reference to it being fixed.

Bug Fixes

3. [GRID]

F2[COPY]+[BAR_R]
Region of a copy is strange.


Did notice it seemed to behave a bit better but been busy of late and hardly played with 1.14 much.
User avatar

Re: JJ OS BUG REPORTS

By le rat Tue Jun 02, 2009 3:13 pm
OS2xl 1.14

1. go to main screen
2. press window on the 4/4 time signature
3. Turn 1,2,3 and 4 4/4 to 5/4 and press do it
4. Repress the main button or go to grid edit mode + pad 15
5. hold shift and press F6 Zoom in
6. Press play start or play
= grid display bug

Hope someone can confirm coz last time i had the same bug with a 9/4 beat and did not get any confirmation.
PEace
User avatar

Bug: JJ 2XL 1.15: Drum Grid—1 Bar Edit While Track is Solo

By elevated Fri Jun 19, 2009 10:00 pm
Bug: JJ 2XL 1.15: Drum Grid—1 Bar Edit While Track is Solo

1. Enter Drum Grid
2. Record MIDI data, such as an 1/8th note hi-hat pattern
3. Solo the track by pressing F6
4. Enter 1 Bar Edit Mode by pressing Shift + F3

BUG: The track is pronounced incorrectly because it is solo (phasing sound)

Sent to JJ-- No confirmation neccessary
User avatar

Re: JJ OS BUG REPORTS

By elevated Sun Jun 21, 2009 12:51 am
le rat wrote:OS2xl 1.14

1. go to main screen
2. press window on the 4/4 time signature
3. Turn 1,2,3 and 4 4/4 to 5/4 and press do it
4. Repress the main button or go to grid edit mode + pad 15
5. hold shift and press F6 Zoom in
6. Press play start or play
= grid display bug

Hope someone can confirm coz last time i had the same bug with a 9/4 beat and did not get any confirmation.
PEace


Is the issue gone in XL 1.15? I just tried a bunch of time signatures with no issues, including the above scenario
 Topic locked
Return to JJOS Bug Reports & Feature Requests