JJ OS Bug Reports (ARCHIVE)

I'm sorry, I figured it out: you have to manually punch the tracks back in after recording. It's all good now

can you confirm this bug i've just discovered using loop mode and sliders :
1>take a quite long sample w(e.g. ride)
2>hit loop on
3>st : 00000 /loop (eg) : 00015000 /end (eg) :00035000
4>go to GPE (mode+pad11) assign your sample to a pad
5>set play mode to note on on this pad
6>go to slider mode (mode+pad1)
7>follow those settings : note on : s.end :100>track
8>press the assigned pad and let the sample play until it repeats try different q link values but when you're above 60 (between 60 and 100) there's a glitch where the first sample play and then another sample is taken randomly...

can you confirm this one guys?i just woke so i'm not sure...

Just reported:

1. Load Project
2. Mute a track
3. Go to a different track
4. Go to Grid edit
5. Press "window"
6. Turn "Step sound" on
7. Press close (F4)
8. Turn Jogwheel
Sound of the track muted will sound too.

1) Turn on MP
2) Press MODE+Pad 11 (GPE)
3) Press F2 (Filter)
4) Cursor over to ATK (Attack), DCY (Decay), or FLT (Filter)
5) Press F6 (WHOLE)
6) Press WINDOW button
7) go to any param control and hold [SHIFT]+TURN DATA WHEEL

*BUG*
Will not increase or decrease in increments of 10.

Reported.

Anyone care to confirm?

hereo wrote:1) Turn on MP
2) Press MODE+Pad 11 (GPE)
3) Press F2 (Filter)
4) Cursor over to ATK (Attack), DCY (Decay), or FLT (Filter)
5) Press F6 (WHOLE)
6) Press WINDOW button
7) go to any param control and hold [SHIFT]+TURN DATA WHEEL

*BUG*
Will not increase or decrease in increments of 10.

Reported.

Anyone care to confirm?

JJ hit me back. Will be fixed in 4.83. Coming soon!

I've been experimenting with using my 1k as a sample synth, I've sampled the raw waveforms from a Virus TI and have been looping 1 cycle of sample. for e.g. a saw wave pitch A3

My drama is that i am getting clicking and what sounds like aliasing (almost like a phase running down the note) that I can only put down to a bug in the MPC, the looping is perfect, I just can't work out what could possibly causing this.

I've tried using longer samples of up to 5 seconds where the cycles again are a prefect 360 degrees but i still get a click when the sample loops.

*Edit* Sorry- double post

My version 4.84 just wigged out on me big time.

the screen got all garbled then I figured it was a refresh issue so I went into a screen and then back to main the it did what looks like a hex system dump.

I powered off and back on. Started playing around with recording a simple sequence, the tempo auto adjusted from 100.00 to like 163.9 or some odd number, then the bars are set to 256...

trying to see if I can duplicate this issue.

ok, I was able to duplicate the tempo issue.

I don't know if it's a bug? seems odd to me though.

i power cycled my 1k

it comes up, the bars go from 0 then are set to 256.
I try using the numeric entry to set it to 2 but it doesn't retaing the value. I use the data wheel, it allows me to set it to 2 and retains it.

I press REC+PLAY it counts in, I play a simple bass and snare

It only happens when I hit on pad 15, the tempo goes mad. 200+ and back down to 170+

It's somehow has pad 15 assigned to tap tempo, so maybe it's not a bug.
The other garbled issue is obviously not normal, so I'm not a complete lunatic.

as my post was locked i copy and paste here

Q: 1 main mode
　2 keep pressing tap tempo + 1/16 (F3)
　　= Q 1 after + numeric button highlight
　3 If pressing tap tempo + 1/16 + numeric = next seq mode
　 4 if pressing tap tempo + 1/16 + pad bank A = play
　 5 if pressing tap temo + 1/16 + pad bank B = 16 levels highlights.

A: This is not a bug.
　　It is a problem of hardware.
　　OS of AKAI is also the same.
　　There is no problem functionally.

le rat: i think what jj is saying is that it's the hardware that's causing those problems. akai never allowed for someone pressing lots of buttons at once because they assumed you wouldn't. this is part of the design of the electronic circuits in the 1000, and nothing to do with the os.

yeah but you know i only press these buttons cause they highlight by themselves. I didn't check all the keys combination in the mpc.
Anyway as it is a hardware issue nothing can't be done.

just sent this:

hey hey, nym again.

i have a bug report and a comment.

first: a comment: recently, I create my drum sequences within MIDI grid edit. i enjoy programming in MIDI grid edit because of the ZOOM IN/ZOOM OUT function. i enjoy ZOOMING OUT until all bars in sequence are visible.

it is very good that we can ZOOM OUT and keep TC OFF in MIDI GRID edit. this is different than PAD grid edit, where there is no ZOOM IN/OUT. the way to zoom IN/OUT in PAD grid edit is by using TC. programming drums in MIDI GRID edit is very powerful and allows for excellent human timing, while viewing all notes in a sequence! funky!

next: the bugs. one is a bug, the other is a fruit fly.

first problem: qreal data copying.

1 - enter QREAL GRAPH mode
2 - record any QLINK data in the 1st bar
3 - select a portion of data from 1.01.48 to 1.02.00
4 - copy data
5 - scroll to 3.01.48 and PASTE
6 - BUG: original copy is referenced from 1.01.00 (added space)

2nd "bug" - in MIDI GRID edit and QREAL edit, F4 (PC) functions as delete even without overdub

1 - enter MIDI grid edit or QReAL edit (not ALL)
2 - record performance
3 - scroll data wheel while holding f4 (PC)
4 - "bug" - notes delete!
5 - NOTE: this is a GOOD bug, because it does not require OVERDUB to be on for a DELETE. it is a convenient method of DELETING note data.

finally, one last note:

1 - enter midi grid edit
2 - record performance
3 - scroll to a note
4 - hit EDIT
5 - navigate to VELOCITY
6 - inconsistency: TAP TEMPO does not increase increment.

not a big problem, but worth noting.

have a good day, and thank you for your efforts!

nym

1. on any track, go to 'step edit' and scroll to time position
2. go to insert->type->track mute
3. press f5 'do it'
4. track mute gets written to track 1 every time

os 4.85

in grid edit i want to copy a line of events

i press overdub but when pressing tap tempo/note repeat + F3(copy)
or F6(move) it changes the TC resolution or worse put TC off.

sounds a bug for me. anybody confirm?