JJ OS Bug Reports (ARCHIVE)

midi grid edit, os2 1.19

1 - create a program, assign samples to it
2 - change the MIDI NOTE assignment to your pads
3 - turn track to MIDI
4 - record pad performance (using pads from step #2)
5 - play back your performance.
6 - BUG: the incorrect pads play back.

you can use this drum program as an example:

http://nymantics.com/EXAMPLE.zip

BIG Thanks to someone, who successfuly reported this few versions ago:

[MAIN][GRID]

[<<BAR][BAR>>]
Auto repeat dose not work

haha i was one of those who reported it. OS2 1.19 very small workflow trouble : while waiting a next sequence to play in main screen, pressing play or play start won't change the sequence.

Please help!

I made some beats last night, saved it all, then this morning got up and wanted to hear what I had done. I turned everything on, and played thru the songs, everything was fine. I went outside for a few minutes, then....

I came back in to an error message on the screen, and after I turned it off and on, loaded up the same project again. The pads started to all fire at once. I hit MODE and held it down and it started jumping from different screens, record>mixer>progroam> etc....

I called in AKAI and they told me it was probably the OS...

Anyone ever had this problem>?

THanks

le rat wrote:haha i was one of those who reported it. OS2 1.19 very small workflow trouble : while waiting a next sequence to play in main screen, pressing play or play start won't change the sequence.

Thanks again, this was driving me nuts.. I send report once, but I guess one voice doesn't always matters.
Yeah, that playstart thing was very helpful, he should bring that back.

JJ OS2 1.19:

When I to to MIDI/SYNC (Mode + PAD9) and go to the NOTE menu, I can't switch between the four banks. I can do this in JJ OS 1 though, so this definitely is a bug.

kraku wrote:JJ OS2 1.19:

When I to to MIDI/SYNC (Mode + PAD9) and go to the NOTE menu, I can't switch between the four banks. I can do this in JJ OS 1 though, so this definitely is a bug.

confirmed. you should report this to JJ.

Discovered a strange thing today:
- Go to Record mode (Mode + PAD5)
- Select "Mono L+R" as the input source
- Press "Record"
- The screen reads "waiting for input signal..". Regardless of threshold and input signal level, recording doesn't start. When input source is "Mono L", "Mono R" or "Stereo", recording starts automatically as it should.

I dont got my mpc hooked up so i cant check, but Mono l+r is the recording mode, not the input source...

Edit: stupid me, thought maybe the error was on your side, but even without hooking it up i could test it with the main out as input source.
And you are right, bug confirmed.

yeah i noticed this in 1.19 but forgot to report it. just checked on 1.20 and its still there.

ive reported it as follows
0s2 1.19 and 1.20

1.enter record mode
2.change mode:MODE L+R
3.input level above threshold
4.press F6 record
5."waiting for input signal" message
6.record does not start until f6 start is pressed : threshold setting does not work.

NOTE:if threshold:-infinity threshold setting does work.

also this should be in bug reports sticky.

oh i thought it was something i was doing wrong.. happened a couple of times.. will look into it again when i get home

yeah i'd noticed this a couple months back

I never noticed this either. Haven't had much time with my MPC this summer.

Yeah, this should have been posted in the bug reports topic. So I'll attempt to merge this topic in there.

has anyone noticed if LFO sttings arent working on their Patched Phrases?

if i set up an LFO on a pad thats got a PP assigned there, eg: a fast (0.12) rate LFO, say full pitch : 100 & zero delay: 0.00 (just to be absolutely audible).

the LFO doesn't actually begin to modulate anything until the pp's at the end, as if its not in effect until there's a "note off".

in one random case i managed to get it to kick in half way through a long PP sample, no idea why or how.

does anyone know if the adsr's have anything to do with altering the lfo in JJos2? i had a suspicion it was maybe interfering with the lfo's here.

not a big deal but for instance if i create a NDC program with 9 pads, some samples will be replayed on pad 10 to 16 after.