v1.71 bug reports please!

Okay guys, I have an Numark/Alesis/Akai customer support guy waiting for detailed reports on how the v1.71 bugs can be re-created. He promises they will make bug fixes as soon as they can reproduce the problems.

Please give me step by step list (if possible) that reproduce the bugs.

I mentioned the hanging while browsing bug, the wrong sequence number display bug, and the lost sequence data bug after a record session.

all the freakin time. there is no pattern! it all just happens randomly..

Didn't you also report the sequence name/number display problem when switching between the Song and Main pages? If so, could you at least describe that bug so that they can reproduce it?

Maybe, just maybe when they've found that bug, they can also explain the record bug, where a complete sequence + tracks disappeared. Some sort of general current sequence number mixup bug, you never know.

The only problems I had so far were two lockups of the mpc during file browsing, when looking for a sound. Just using the dial in a directory sometimes results in the lockup.

I'm having trouble reloading 1.70...I tried loading from cd & usb,to no avail this 1.71 is crazy, they need to act fast & through in os 2.0 with free monitor!

Rob wrote:Didn't you also report the sequence name/number display problem when switching between the Song and Main pages? If so, could you at least describe that bug so that they can reproduce it?

Maybe, just maybe when they've found that bug, they can also explain the record bug, where a complete sequence + tracks disappeared. Some sort of general current sequence number mixup bug, you never know.

The only problems I had so far were two lockups of the mpc during file browsing, when looking for a sound. Just using the dial in a directory sometimes results in the lockup.

"when go from song into main, the sequence disappears: blank" Not all the time of course, just sometimes for no reason
quote ikke "I go into recording mode, record a sample. I add it to a program, go to main, i hit play, then record + play to get recording. I record the recorded sample. I go to program window, go back to main and bang the entire sequence just disappeared. BLANK! Sequence_001: unused. m*therf*cki@%* "
uhm..
"When go from main into song, the cursor displays its on the right spot, but as soon as you start playing or scrolling, you re suddenly on another sequence."
"Auditioning samples causes error or causes the mpc the hang."
Aksys is buggy again: error, usb maybe unplugged? grrr
"Scrolling through samples in folders on the HD too fast causes hang and eventualy error or other crash"

Good news: "Editing parameters from programs and multis while playing a sequence or song seems to be a lot faster" Tell them not to forget this!!

And while you re at it, ask for a new quantizing feature ( with strenght: 0-100 % ) and copy segments of bars from an entire sequence. And maybe let them double the amount of sequences, instead of 128, ask for 256!
(I would be in heaven with those three features! and I think Im not the only one.. )

Does that also apply to bugs that I reported to Akai that were new to OS 1.70 that haven't been addressed in OS 1.71?


Thx...


Dave

Well give it a shot. The guy is listening because I sent a report about the buggy v1.71 to Akai, but I can ask if he's interested in other bugs/requests.

MPC4000 OS 1.71

When running at 96k, copying a multi freezes the MPC

- set system clock to 96.0 k
- after reboot go to MULTI
- create a multi
- select the multi and press WINDOW
- press COPY[F6}
- press DO IT [F5]

the following fatal error occurs:

=============================
Fatal Error! "Data Abort"
[ ID: 00000003 I: 00100CFC ]
[ FSR: C0005003 FAR: EA0042C5 ]
=============================

I did a OS 'back check'. The bug occurs since OS 1.60 (I also checked 1.51e and 1.51t > 1.51w, no bug)
If I remember correctly 1.60 was the OS in which the Multi format was changed for fixing the FX level drop, so I guess it has something to do with that fix.

At 96k the 3rd and 4th FX slot are discarted. Does the Multi copy function check that correctly in OS 1.60 > OS 1.71 in comparison to earlier OS-es?

Timecode bug

Timecode (MMC) resets to 00:00:00:00 at bar 01:11:35:00 when locating

- Create a sequence with 999 bars 4/4, tempo 30
- I used framerate 25
- in the now field locate to position 537.04.464 (time 1:11:34:24)
- increase the location with one tick to 537.04.465

As you can see the time is reset to 00:00:00:00 in stead of increasing to 01:11:35:00
This time is also send out off the MIDI port when MMC send is assigned to that port in the sync window

This is a looping problem at the next 01:11:35:00 it is reset again. Maybe a wrong data type or % ?

<you may know more about this last comment than I do Rob please remove it if I am talking nonsence.. thnx>

UI bug

Wrong on screen loop end / punch out marker with certain time signatures

> Create a new sequence
- set tempo 30 bpm
- set n.o. bars to 1
- set timesig to 16/4
- set n.o. bars to 999
- Make sure the loopmarkers are set to: 001 - end
As you can see the end marker in the time ruler visualy is somewhere at 66 measures.
When you scroll the loop-end position down with the jog wheel, the loop end marker scrolls to the left, offscreen. sometimes it flips over to the other side of the screen.

- turn on punch
- set to "punch in - punch out"
- set the positions to 001.01.000 - 999.01.000
As you can see also the punch out marker is also visually stuck at the same on screen position as the loop end marker.
It looks like a bug in the on screen scaling.

I did some further testing and this type of behaviour occurs with time signatures 8/4 > 16/4 & 15/8 > 16/8.

UI bug

Minor display bug in time signature window after decreasing number of bars in the bar field

The now field is not automatically reset when the n.o. bars is decreased. This results in a display bug in the timesignature window.

> Create a new sequence with a lot of bars.
> Locate to lets say 40.01.000

> Change the numbers of bars to 1 in the bar field.
(now field still indicates 40:01:000)

> Go to the time signature field and press WINDOW
As you can see there is no cursor (it is still in the 40st bar)
When you move the jog leftwards, the cursor moves from the right into the window.

If you press WINDOW twice you can see the cursor is gone again, back to 40...

I encountered this bug the other day. I have a sample thats about 4 min and change long (vocals). Everything works fine, but when i went to chop it up, it only plays the right side of the sample. The left side comes out real low, and a bit distorted. I checked all my connections, as well as my crappy headphones i use for late nights, and everything checked out. When i chopped part of the sample out, maybe 30 seconds long, it played fine. Not sure about this one.

Okay, I just sent all the info to the customer support guy, and CC'd it to [email protected] as well. Let's hope they'll fix all of these, especially the problem with the sequence. Looks like v1.71 has problems with the idea what the current sequence is.

originally posted by rookie

I'm having trouble reloading 1.70...I tried loading from cd & usb,to no avail this 1.71 is crazy, they need to act fast & through in os 2.0 with free monitor!

I posted this in another topic before. I just tried it out and it works (like a charm everythime)!!

I find it useful to keep all of the mpc4000 os's on the "4000's" hardrive. Two reasons why i think this is a good idea.

1: It is very easy to load an os this way (and pretty quick also, but never tested the difference in speed compared to the other ways.

2. If you every have a problem loading files created on an older os (some people still use older os, some by choice/ others by, well you know ), all you have to do is just open the folder containing the list of os's, and load it like anything else you would load on your 4000's hard drive.

The only way to get the os on the hard drive though is through akai sys. What you do is create the folder in windows, mine is called akai os, and when you put all the os's in the folder (unzipped), drag it into your 4000's hard drive via akai sys. Loadind the os should be self explanatory.

so rookie, im on os 1.71, and just loaded 1.70 while typing this, and it works fine using the method described above.

Hope this helps you out.

Easy