Important: 4k bugfix update

OK,

There is a chance that Akai will do a (partly) bugfix OS update for the 4k.
*This is not a promise*.

But before anything can happen at all they need to have a list of *reproducable* bugs. In the transistion from old to new Akai some bug info unfortunately got lost plus new bugs could have been discovered since.

So if you are aware of any reproducable bug or bugs, please post them in this thread or email the info to me.
Please report the OS version with the bug. Latest OS is 1.71.
This means that if you have an older OS on your 4k and do not want to upgrade but do want to report the bug you have to tell which OS it is then.

I'm in contact with the guy at Akai that has something to say about it. He is willing to *consider* a (partly) bugfix OS after such a buglist is available. I'll be the contactperson for that list.
Please be aware that this guy has *nothing* to do with the past of Akai and the history of the 4k. So he has a pretty objective view on the product line. This means he will look if he can find some space for the prgrammers to do a bugfix to fix the most dirty bugs.

Feature requests will not be taken unless it has a clear relation with the reported bug. Again, if this bugfix update happens it won't be a major one. All final decisions what will be done and what not is up to Akai.

Thanks, Boele

Posting the bug to me by email is preferable so I can make contact if I have any questions.

[email protected]

here is this one.

http://mpc-forums.com/viewtopic.php?t=6 ... sc&start=0

OK thanks.
It would help me if bugs described in threads on this forum are tested again first and transfered to this thread (in as short as possible words), including the OS version tested on.
That would save me quite some time. This is not a demand, just a request
When that is done, I can reproduce it myself on my 4k again, and then enter the bug in the 4k bugtracker.

Simple.

Go to Effects assign a DELAY effect on SEND D

next set Qlink 1 to send Ctrl Change

Now turn the Qlink knob.

you will hear static noise, as illiac described a dinosaur chewing on Brazil nuts, then the MPC will crash.

Thanks to Drumtrack for finding the problem.

OK, thanks. OS version?

1.71

thanks betaman

let's get to work guys!!!!

Yes. I hope to raise some enthousiasm here.
Let's be real, even though it is a small chance, it IS a chance to get at least some bugfixes done, let's take that opportunity with both hands.

Also, does anybody know who is the moderator of this list? Maybe it would be good to add a thread where I can put the approved bugs in a list, so people can check if one is already documented or not. That should be a read-only thread to keep things clear.

MPC-Tutor, Prah_860_, elmacaco, Lampdog, Blue Haze, sparq, distortedtekno are the moderators

Do you know who I can approach best for this request?

Blue Haze is always here

and man your gonna need a moderator to keep that thread clean and tight!

Well, actually I want to ask if it is possible to have two threads: this one for reporting and discussing the bugs and another one with privileges set to read only, but me having access to create that clean list.

I'll ask him. Thanks.

Boele

the SEPARATE bug:

record 8 tracks on tracks 1-8
record multichannel midi to track 9
use SEPARATE to split this track and send the individual tracks to tracks 10-18
the drum tracks are gone!!! tracks 1-8 were NOT set as destinations but they were overwritten anyway, in fact ALL tracks in the sequence are overwritten

in fact regardless of how you use it SEPARATE always destroys ALL existing tracks, not just the ones it is writing to. So, combining existing data with incoming multichannel midi, which is surely the purpose of this feature, and something I want to do all the time, is actually impossible

0S 1.71

(of course if this feature were to be looked at it would be great if the SEPARATE page defaulted to the next 16 tracks from the one first one you select, as 99% of the time this is how it would be used - rather than tediously scrolling for each of the 16 times every time, but hey that's an RFE.. and I know i musn't... )

scd wrote:OK,

There is a chance that Akai will do a (partly) bugfix OS update for the 4k.
*This is not a promise*.

But before anything can happen at all they need to have a list of *reproducable* bugs. In the transistion from old to new Akai some bug info unfortunately got lost plus new bugs could have been discovered since.

So if you are aware of any reproducable bug or bugs, please post them in this thread or email the info to me.
Please report the OS version with the bug. Latest OS is 1.71.
This means that if you have an older OS on your 4k and do not want to upgrade but do want to report the bug you have to tell which OS it is then.

I'm in contact with the guy at Akai that has something to say about it. He is willing to *consider* a (partly) bugfix OS after such a buglist is available. I'll be the contactperson for that list.
Please be aware that this guy has *nothing* to do with the past of Akai and the history of the 4k. So he has a pretty objective view on the product line. This means he will look if he can find some space for the prgrammers to do a bugfix to fix the most dirty bugs.

Feature requests will not be taken unless it has a clear relation with the reported bug. Again, if this bugfix update happens it won't be a major one. All final decisions what will be done and what not is up to Akai.

Thanks, Boele

Posting the bug to me by email is preferable so I can make contact if I have any questions.

[email protected]

At his own personal invitation, I sent Robert Ray @ Akai a big buglist about 18 months ago (i.e. during the Numark era). What happened to that?