Important: 4k bugfix update

So there is some hope of renewed life in getting these bugfixes dealt with.

dabmeister wrote:So there is some hope of renewed life in getting these bugfixes dealt with.

man ....dont hold your breath....just dont hold your breath

AWW_NAWW wrote:

dabmeister wrote:So there is some hope of renewed life in getting these bugfixes dealt with.

man ....dont hold your breath....just dont hold your breath

Ha...sounds like deja vu then. At least we'll see if this turns into something positive.

best of luck to all of you
you have the support of a vocal 22 year old honkey

I would call this a bug however some may argue its a feature.
When in the seq edit page using the step controls with the view set to notes as you step through the beats you hear whats played set it to anything other than notes and as you step through you can't hear anything.
That to me is a bug!

g

Good one. Thanks.

Don't know if anyone has ever had this too.
I have created three 4 layer drum programs the same thing happens on all of them.
Every program has 16pads with 4 velocity levels per pad.
When I go to the track mixer and change the PART level the top velocity level isn't affected by the top third of the volume slider for that part. BUT the other three velocity levels are affected and go down in level as I turn the part down as they should. Net result the PARTS cannot be mixed as the top velocity level is unmixed for the first third where as the other velocity levels move with the part level!

I can meter this on my mixer! to prove my ears are not imagining this!
Anyone else ever had this problem?
geoff

scd wrote:

renegadebliss wrote:The other main bug is Sysex. I don't know how many of the Feline's list include Sysex
issues.... It's probabably about time that we dig down and make sure that at
least the Sysex works as expected.

Maybe we should start a seperate thread of known Sysex commands that work
and known ones that don't work.

It shouldn't take any Code Space to fix the Sysex, since it's already taking the space. We just need them to correct the ones that don't work....
Dave

I'll pay special attention to sysex later.
I'll need to talk to akai to see what's possible in that section. But again, we all want at least a good list of working/non working strings right?
Same goes for the CCs by the way, but that is less work.

I've been working on it over the weekend and it will take a little bit more to work it all out and document it. Basically keep 2 lists . One, the items and strings that do work, and Two the Items and Strings that don't work. I think right now, between myself and McSmooth we should be able to work a good deal out. I'm doing it on the BCR2000 and I think he's doing it on a Bit Stream Pro 3x. Once I've gotten a good list, I'll start a seperate thread... of working sysex strings.

Dave

McSmooth wrote:I have been spending a lot of time with sysex, so will report anything I find, however, I don't think it is quite as bad as people say as most of the commands I've tried so far do work. The biggest issue I've noticed is that there are missing commands, often from features that were added in later OSes. There is absolutely NO sequencer functionality documented at all, only the midi file playing feature from the Z (which doesn't do anything on the 4k). There are also commands in the documentation that are simply not 4k features... they were probably possible future features that never made it to the OS.

Here is an example: I wanted to control the tempo through sysex. There are two tempo parameters in the documentation. One is for midi song functionality on the Z, and does nothing for the 4k. The other is for multi tempo. Unless I'm missing something, there is no such thing as multi tempo, tempo is determined by the sequence or master setting.

I saw the Multi Tempo as well over the weekend whle going through the Sysex guide. I'm guessing that's for the Z4/Z8 to set a Tempo for the Multi so that any LFO sync can follow that setting.

I also saw in the Sysex code Multi EQ's...
and in the Front Panel Control for Mouse Click and Mouse Double Click for use with Remote Operations. Not sure if etiher of these are operational.


It's also weird that they have Song Sysex control but no Sequencer Sysex...

Would be very nice to get the actual Syesex documenation for the MPC 4000 for OS 1.71.....but I don't think that'll happen. but the best we can do is to document what doens't work...


Dave

renegadebliss wrote:I saw the Multi Tempo as well over the weekend whle going through the Sysex guide. I'm guessing that's for the Z4/Z8 to set a Tempo for the Multi so that any LFO sync can follow that setting.

It's possible, but I'd guess no since the Z can take incoming clock and I never saw that option when I had one. It's also not in the manual and shows it does not trasmit clock, just receives it and sends to LFO1/2.

I also saw in the Sysex code Multi EQ's...
and in the Front Panel Control for Mouse Click and Mouse Double Click for use with Remote Operations. Not sure if etiher of these are operational.

These and a few other things stand out when you read the document, but appear to be future ideas that did not get implemented.

It's also weird that they have Song Sysex control but no Sequencer Sysex...

This is actually referring to MIDI sequences, not songs like on the MPC. The Z has a feature where you can play standard MIDI files against a loaded multi. I have found that most of section 28 (except playing songs) actually does work on the MPC and refers to loaded sequences. Section 2A and 2B don't help at all though, so the 4k either needs these sections expanded or its own sections for sequencing and songs.

Would be very nice to get the actual Syesex documenation for the MPC 4000 for OS 1.71.....but I don't think that'll happen. but the best we can do is to document what doens't work...

That would be nice, but I'd be more than happy if they simply add the missing commands and fix broken ones in this rumored OS fix. scd asked for help with a list of sysex bugs. So far, mine is pretty short, so I am wondering if we should start a seperate thread for that purpose? I have a much bigger list of commands that are missing. I have to say, I have little faith that anything will come of this fix, but if it does, it would greatly change my opinion on the new Akai.

I'm almost ready to post an in depth guide on sysex, so hopefully that will get others using it and possibly finding other bugs we missed.

McSmooth wrote:scd asked for help with a list of sysex bugs. So far, mine is pretty short, so I am wondering if we should start a seperate thread for that purpose? I have a much bigger list of commands that are missing. I have to say, I have little faith that anything will come of this fix, but if it does, it would greatly change my opinion on the new Akai.

I'm almost ready to post an in depth guide on sysex, so hopefully that will get others using it and possibly finding other bugs we missed.

Please do not open a new thread with sysex bugs. I would like to have *every* issue in the one thread. For completeness and easy browsing.
Thanks a *LOT* by the way for doing this, it's a real timesaver for me (since I need to betatest the 5k as well, which has of course priority for them).

I am still getting signals this will happen. Akai first needs to get out the 5k which will take only another few weeks. After that I am going to ask them for a timetable. In the meantime we should have the list as complete as possible.

bugs are coming in on my email as well. Thank you all!

McSmooth and Renegadebliss: since you're on it and both the BCR and Bitstream can do this easily: could you also check the CCs? Don't feel pushed, if it is taking too much time I will do it myself.

Thanks! Boele

Anyone else experienced the velocity level + part mixer problem i posted?

I would just like to know if anyone else gets this problem too as its currently annoying the crap out of me.
cheers
geoff

God damn it this is criminal.
What I posted goes further no wonder I have had mad problems getting things balanced in the mpc.

If I assign a sample to a Pad, now go to 16 velocity levels to make sure I am hitting the same velocity level each time.
Now move to the sixteenth pad (hardest velocity) now I set the Part mixer to maximum and move the part mixer gradually down.

There is almost no change in output for the first third of the fader travel.

Now repeat the sam thing but at a different velocity level pad 12.
If I move the part mixer fader the same distance I now meter approx a 7db change.

So one velocity level is moving -7db whilst the other more like -1db

This is totally and utterly unacceptable in every way.
I am furious!!

Can someone double check this for me?
just in case there is some parameter somewhere that could cause this???
I am on the latest OS.
cheers
g

foge1

I have a lot of difficulty following what you posted.

Can you post a real simple step by step instruction so we can try to replicate your bug....

at the moment I think you probably have a problem with your pads or your pad sensitivty settings... but as I say, its not so clear what you mean

Incredible.

The one that really bugged me was that all the aftertouch settings weren't saved.