JJ OS Bug Reports (ARCHIVE)

distortedtekno wrote:

g4s wrote:MPC freezes when I load a few samples used in OS1 into 0.66 - assign to pad screen. Screen display becomes garbled - a bit like the crashes I used to get on the early MPC2000XL OS.

G4s

Yeah I just noticed the same problem a few minutes ago. The first time it crashed. The second time it didn't. I was able to exit to the main screen.

The same bug is still occuring in 0.68. Luckily the MPC hasn't crashed. I can still assign samples to pads, even though the odd characters make it difficult to read. So I just reported that.

distortedtekno wrote:OS2 version 0.68

1. Load pgm from ADSR EXAMPLE folder with sample
2. Hit MODE + PAD 11 (GPE)

BUG: "under construction" message appears, the same as MODE + PAD 7 (PROGRAM).

NOTE: This bug does not appear when a sample is not loaded.

NOTE 2: When F2 or any of the F keys are hit in MODE + PAD 7, the screen turns blank and boot screen will appear. but will not reboot.

JJ's response:

It is not a bug.
GPE for INST is still incomplete.

Thank you.

My response:

There is no INST selection for a track.... only DRUM, MIDI, and AUDIO.
I can load a drum sample, but when I go to GPE, the DECAY and SUSTAIN
levels are the same when making a change on either of them.

JJ's response:

GPE is still incomplete.
There is a bug in GPE of DRAM until GPE for INST is completed.
After GPE of INST is completed, we recommend you to use GPE.

Thank you.

I believe there's a typo in his response. The word "DRAM" was mis-spelled for DRUM.

I'm still getting familiar with the changes made, so the more time I can spend testing the OS, the better off things will be. Some time, patience, and persistance will move things along rather well. Nevertheless, I'm very optimistic.

after my huge initial testing day last week, i have been studying like crazy and writing papers for the end of the semester. in my free time, i've been working on old songs in reaper...found a bug last night but it's probably just an incompletion

luckily my first bug report on .65 was so huge i think they might still be working on them.

i'll get back to work asap.

a few little bugs in 0.68 :
1.SIMULT PAD doesn't work
2.Main screen: Alt loop samples, click sound at the beginning of the sample.
3. Trim mode:Turning loops on/off>hit pad>digital noise.

1.SIMULT PAD doesn't work
..but this might be cause GPE isn't complete?

i need that akai blue box editor ,im losted the program and wiv out, im losted . i downloaded it here a here ago and now i '''''''''''ve not got it . i have the mpc500 and recyle and wiv out it the mpc 500
a long ting can some one sort us out peace

xbass wrote:i need that akai blue box editor ,im losted the program and wiv out, im losted . i downloaded it here a here ago and now i '''''''''''ve not got it . i have the mpc500 and recyle and wiv out it the mpc 500
a long ting can some one sort us out peace

then u are lost - yeah check 'versiontracker' - or even google?

os 4.97 not a bug though, may sound as a dumb question.

I was first dealing with shift timing in grid mode and then with step edit mode. I got a snare at 2.02.00. How come if i want to shift-time it i can only go at 2.01.95 and not 96,97,98,99. On the contrary it works for 2.02.01 and so on.

Is that Akai specification?

le rat wrote:os 4.97 not a bug though, may sound as a dumb question.

I was first dealing with shift timing in grid mode and then with step edit mode. I got a snare at 2.02.00. How come if i want to shift-time it i can only go at 2.01.95 and not 96,97,98,99. On the contrary it works for 2.02.01 and so on.

Is that Akai specification?

this is akai specification indeed.

the resolution is of 96 ticks, hence going from .00 to .95

thx for your answer truvc. I should try not quantize then.

I'm in os2 .70---- and he mixer doesn't work--it doesn't affect the volume of samples/pads-- anyone else experiencing this---seems pretty basic--but I've never run into this problem before

the new mixer mode works with tracks no?

here is a bug in TRIM mode.

1 - load multiple samples.
2 - enter TRIM mode. select a random sample from sample list.
3 - perform a TRIM function (discard, etc) on the random sample
4 - NOTE: trim moves to different sample after completion
5 - select a different random sample in TRIM. perform TRIM function.
6 - NOTE: trim moves to different sample after completion.
7 - BUG: different sample is displayed after trim function.

here is a bug in INST programs:

1 - load inst program
2 - record multi-note performance with overlapping notes (chords, etc)
3 - play performance. note POLY playback of program
4 - turn program to MONO
5 - play performance. bug: playback is still POLY. changing program to MONO does not change performance.

this is a bug and an inconsistency in SLICE. first, the bug:

1 - load a drum break or suitable long music file
2 - enter TRIM. make sure that CHOP=OFF
3 - select F5 CHOP.
3 - hit F1 - cancel.
4 - NOTE: on top, CHOP=1.
5 - BUG: non-destructive chop is turned on by F5 CHOP.
6 - SLICE the drum break into 17+ parts. hit edit, f2, convert to sliced samples. Create sliced samples.
7 - enter trim and view sliced samples. NOTE: since parent file had CHOP=ON, all new files have CHOP=ON.
8 - in trim, play sliced samples. trim bug: sample plays panned and strange.
9 - NOTE: turn CHOP off. play again. NOTE: sample does not play panned and strange. only a sliced sample with CHOP=ON plays panned and strange.

NOTE: it is good that the parameters of a parent file are given to sliced samples. for example: it is good to turn a parent file to ALTERNATE LOOP. this way, sliced samples are all ALTERNATE LOOP. this saves time. however, the bug where SLICE turns CHOP=ON is undesirable.

second: chop/slice inconsistency:

1 - load same drum break file.
2 - enter trim. note: F5=CHOP. do not press F5.
3 - turn non destructive CHOP=ON.
4 - note: F5=SLICE.
5 - inconsistency: SLICE and CHOP appear at different times.
6 - suggestion: in trim, with CHOP=OFF, F5 should = SLICE, not CHOP.

last, two unimportant suggestions.

LOOP ON/OFF/ALT in TRIM.

1 - load sample, enter trim
2 - hit F1, loop on.
3 - hit F1, loop off.
4 - current specification: hit F1 one time=loop on. hit F1 again=loop off.
5 - suggested specification: hit F1 one time=loop on. hit F1 again=alternate loop. hit F1 again=loop off.

VERTICAL ZOOM in TRIM.

1 - current specification= SHIFT+UP or DOWN controls vertical zoom.
2 - suggested additional vertical zoom specification= SHIFT+DATA WHEEL up or down controls vertical zoom.
NOTE - this finger movement is less awkward for a user than SHIFT+up/down.

yo - its more helpful if peeps quote which os 's theyre finding the bug in.


ta homeys

0.71

go to mixer mode
pads will play in pan screen.
pads will not play in out & fxsend screen.