JJ OS Bug Reports (ARCHIVE)

I'm getting terrible slowdowns while using some instrument programs, so it would be nice to have a cpu usage monitor (or something) hidden somewhere.

I thought about reporting this as a bug to jj, but could be that i'm doing something wrong...

^^^^^
is this when you go into trim mode?
if so this a long standing issue, it could also be just the way it is though, for most people some playability here is enough. (you couldnt do anything in trim mode while the seq plays on the akai os)

mikolo wrote:^^^^^
is this when you go into trim mode?
if so this a long standing issue, it could also be just the way it is though, for most people some playability here is enough. (you couldnt do anything in trim mode while the seq plays on the akai os)

No, it's happening in main screen. It would be cool to know what's happening, that's why cpu monitor would be awesome.

ah ok cool,or not cool rather,im not sure what that is, although i haven't been taxing my mpc too hard with programs and such.

On another note i have noticed that "whole" is missing from the layers view of GPE,im sure this cant be a deliberate removal but perhaps an oversight from back when os2 wasn't going to have layers?

i've also had the MPC slow down/lock up on me when usage gets heavy. i push the machine a bit but i didn't think i was going THAT hard on it. my voices are usually pinging around at the maximum & i'm making heavy use of the stuff in the PROGRAM window (ADSR, filters, fast LFO's, etc.). first thing you notice is the midi grid moving line in the main screen starts to lag a bit & if you push the tempo up a bit it gets worse until the machine locks up. your sequence will keep playing but none of the controls will respond anymore and you have to restart. i think we definitely need a cpu limiter since with all the new stuff in os 2 were going to be pushing the processor that much harder on average.

could you post up a project folder where that occurs?

On another note i have noticed that "whole" is missing from the layers view of GPE,im sure this cant be a deliberate removal but perhaps an oversight from back when os2 wasn't going to have layers?

+1, yeah i think that's all it is.

Nym wrote:could you post up a project folder where that occurs?

hey Nym, i'll do that tomorrow. i have it all ready to go but i forgot to put it on my laptop before i came to the internet cafe where i am now (stupid landlord messed up my internet!).

per Nyms request, here are a couple projects that i've made that will overload the MPCs processor in OS 2. these aren't complete works by any means, just some sketches i was working on.

http://www.mediafire.com/?9ht23wugdbd

make sure tempo is set to SEQ & not MASTER. also make sure that Simultaneous Sequence is active (once you start the sequence playing you have to turn the Simultaneous Sequence off & then on again for the MPC to register it.( i probably should report this as a bug ). start increasing the tempo and when you get above 200 bpms you should start to see the grid display lag a bit. approach 300bpm & moving the cursor will become difficult. these projects shouldn't lock the MPC entirely but it you add a track or 2 or turn on INPUT THRU & run it thru the fx, they probably will.

in the 1st project, the cpu overload is probably due to my using the delay AND reverb, since they are processor intensive effects. the second project doesn't use the reverb so it's probably more down to the density of the note data.

any processor can be overloaded, so the only thing that i consider a bug here is the fact that there is no built in limiter to keep you from losing control of the machine when usage gets heavy.

thanks for those, i'll look at them.

meanwhile
bug: qreal display is strange.

1- power on
(CONFIRM: bars=2)
2- enter 6 pad grid edit
3- enter QREAL, TUNE
4- NOTE: display ends after 2nd bar.
5- enter MAIN. increase bars to 8.
6- reenter QREAL edit. NOTE: display stops after 3.
7- record QREAL performance.
BUG: when record+playstart is pressed, "3" disappears. SCROLL of sequencer is strange. only LEFT portion (occupied by bars 1 and 2) are utilized.

sooty: i gave this a go in 1.07:

*** BUG: a display is strange. the CC data display does not clear. display "overlaps" from channel to channel.

and it appears to be fixed. i was flipping cc numbers endlessly, while recording, while playing, etc. i definitely remember seeing that bug before (though i never figured out how to reproduce it), but in 1.07 it appears to have been fixed.

confirm?

Nym wrote:sooty: i gave this a go in 1.07:

*** BUG: a display is strange. the CC data display does not clear. display "overlaps" from channel to channel.

and it appears to be fixed. i was flipping cc numbers endlessly, while recording, while playing, etc. i definitely remember seeing that bug before (though i never figured out how to reproduce it), but in 1.07 it appears to have been fixed.

confirm?

yep. JJ fixed it. i tried all the old stuff that was causing the problem before & it works fine now.
he made a note of it in his bug fixes text:

2. [GRID]

Track Type=MIDI
SHIFT+F1[CONTROL CHANGE EDIT]
A display is strange when a CC number is changed into REC.

good work, thank you. that was bothering me.
i just reported the strangeness that currently exists in QREAL edit.
i hope to see QREAL edit and CONTROL edit merged in the future.
it is silly to me that they are apart.

Nym wrote:i hope to see QREAL edit and CONTROL edit merged in the future.
it is silly to me that they are apart.

agreed!

it might not be possible but i would like to see midi CC become the 'universal language' of the MPC. give as much stuff as is possible a midi CC # and a channel, and then just have the Qlinks send CC, which you can route:

internally (to control a multitude of MPC parameters)
externally (to control external hardware or software)
or both (to control both simultaneously!)

and this of course also allows the seamless integration of external hardware controllers with the MPC.
added bonus is that the midi CC is recordable! so all of this crazy realtime tweaking your doing can be recorded into the sequence, muted, soloed, etc.

the biggest hurdle is an interface to manage all of this new control & avoiding overloading the processor with all of this CC data.

Just bought JJOS2 (1.07) today and have been playing with NDC samples.

1. I trimmed a 4 bar loop to 32 slices. assigned them to my program and made a nice little sequence
2. saved entire memory and went to watch some hockey.
3. Reloaded the project and the sequence would click on every pad event (BUG)
seems like the NDC sample did not load.

tried the exact same sample with NDC but turned NDC off before i saved. reloaded and it would load the whole sample perfectly. I had to manually turn NDC on the sample on again. It would remember the slices and play them again

Can anyone confirm this?