OS version 3 bugs

truvc wrote:just installed 3.04


i also noticed that pressing stop 3 times sends a program change = 1 to midi tracks. I wonder if it is a bug or if it is on purpose.
Is there another feature apart from that behind this "pressing stop 3 times" ?

*Bug* confirmed. Sort of. This one is wierd: I can't see why it would be an intentional feature.

Here's what I found: Unless PROGRAM CHANGE messages are blocked at the midi interface or disabled on the recieving device, pressing stop three times will cause a reset to program 1 -- all devices, all channels.

Where it starts to get weird: This happens *regardless* of midi settings. Disabling PROGRAM CHANGE messages within the track does nothing. Even if I start with a blank program w/no midi functions selected in *any* track I get the same result.

Where it gets weirder: I just tried two software midi monitor programs to see if I could confirm this behavior (midiox and the ol' midimon). If I manualy sent PROGRAM CHANGE messages in the usual way (Pgm field select), this is exactly what I see on the midi monitor. However, if I press STOP 3 times, NO PROGRAM CHANGE MESSAGES ARE VISIBLE ON THE MONITOR. The only thing I can see being sent in this case is a 1-16 channel sweep of ALL NOTES OFF CONTROLLER messages (CC123).

ALL NOTES OFF by itself should not cause programs to reset, and I confirmed this by blocking/disabling all controlers. So there's got to be something else in there. My only guess is that the MPC is producing some kind of garbled midi message that's close enough for the synths and the interface to detect as a PROGRAM CHANGE reset but too far off to be displayed as such in the monitor software. This should probably be made clear in any bug report since it may not be viewable when trouble shooting w/midi diagnostics (though I have no idea what JJ is using for this purpose).

I'm interested to know if anyone on here with a *different* hardware/software midi monitoring setup can see anything I can't. My computer/midi interface isn't exacty up to the latest standards...

found a bug with the q-link. if both qlinks are set to the same pad.

_ press [start/play]
_ track 1 play pad1.
_ q link 1 assigned to pad1 tune. [after] is off
_ q link 2 assigned to pad1 attack. [after] is off
_ press [after] q link 1 -> [after] on
_ move q link1 down -> pitch change
_ press [after] q link 2 -> [after] on
error -> q link 1 is reset to initial value.
_ move q link 1
error -> : no change in sound

truvc wrote:found a bug with the q-link. if both qlinks are set to the same pad.

_ press [start/play]
_ track 1 play pad1.
_ q link 1 assigned to pad1 tune. [after] is off
_ q link 2 assigned to pad1 attack. [after] is off
_ press [after] q link 1 -> [after] on
_ move q link1 down -> pitch change
_ press [after] q link 2 -> [after] on
error -> q link 1 is reset to initial value.
_ move q link 1
error -> : no change in sound

I had noticed this bug in V1.x Akai software. I'm not sure if they quashed it in 2.1. Need to try it again...

When using the q-links in trim mode, the after buttons light up. They remain on when going back to main screen, which wasn't the case in 2.1. I don't like having to press and hold after anyway, so here my suggestion: Press after once -> light on -> adjust start / end points with sliders. Press after again -> light off -> sliders have no effect on start / end points. After buttons should be independent in trim / main screen, similar to pad bank buttons in track mute / main screen.

Another thing: I've noticed that after switching MPC on, the hard drive keeps spinning. After loading something from HDD and going back to main, HDD is turned off after a few seconds. Now when scrolling through samples on HDD, this still happens, meaning HDD is turned off and on every couple of seconds. This ain't good. Suggestion: HDD should only be turned off when Memory Card or Internal is selected in Save / Load. When HDD is selected, it should keep spinning.

i did a bit of experiment and timings with the saving to smartmedia.

_ entire memory: 180 samples = 6.12MB
(_ format smartmedia to be sure)
_ save entire memory to empty folder
os3.04 -> save all in 1minute and 40 seconds.
os1.07 -> save all in 30seconds
error: os3.04 saving too slow

sorry guys I'm doubleposting this 'cos it's doing my head in.
To me this a bug, not just a bug but a clanger.
Correct me if I'm wrong.

You know when you set the TC for a pad and DO IT (eg. 56%)
Then you go to another pad and do another different TC setting (eg. 64%).
Then you go back to the first pad (maybe during another session) and you want to adjust the TC slightly, but how the hell can you tell what your original TC setting was?!?! (cos it just reads what ever the last setting you made - ie 64% not 56%)

This is really buggin me bigtime, cos I always use different TC settings on different pads and would like to be able to go around and tweak tc's slightly in different pads in different tracks, but how can i do this if i don't know what the current tc setting is???

(edited after truvc's reply)

joeybells wrote:sorry guys I'm doubleposting this 'cos it's doing my head in.
To me this a bug, not just a bug but a clanger.
Correct me if I'm wrong.

You know when you set the TC for a track and DO IT (eg. 56%)
Then you go to another track and do another different TC setting (eg. 64%).
Then you go back to the first track (maybe during another session) and you want to adjust the TC slightly, but how the hell can you tell what your original TC setting was?!?! (cos it just reads what ever the last setting you made - ie 64% not 56%)

This is really buggin me bigtime, cos I always use different TC settings on different tracks and would like to be able to go around and tweak tc's slightly in different tracks, but how can i do this if i don't know what the current tc setting is???

you can get a rough idea by listening to the track or by having a look in step edit.
at first i thought same as you, but then i realized that there are no need to know which swing has been applied. because you can just try another one...
also, sometimes in the same track i use different swing settings for different pads. in this case swing per track would be a limitation.

You're totally right, you should be able to go into the the TC window and what ever the last pad that was hit, the settings should show up!

This is seriously messing with my workflow, I'm actually starting to write s*** down, and that's counter-productive.

yea but this direct recording issue NEEDS to be fixed.. i want it to work right fer once.


is there a due date fer 3.05 ?

There's no due date that's definite, as far as I know. Let's be thankful that JJ is at least doing something while Wakai just sit around whackin' it

Qwick folloup on my first post (STOP 3 press bug):

Anybody with a modern MAC and a decent midi interface might want to try this:

http://www.snoize.com/MIDIMonitor/


This gives you a second window to see any extra "junk" exiting midi outputs that the MidiMonitor doesn't consider "real" midi. Might shed some light on what's really coming out of this thing.

Too bad I'm running an AMD processor, or I'd install OS X on a separate HD and check this out.

Before I moved to the Mac I used to use MIDI-OX, similar kind of deal to that MIDI Monitor.

http://www.midiox.com

Pendulum wrote:Before I moved to the Mac I used to use MIDI-OX, similar kind of deal to that MIDI Monitor.

http://www.midiox.com

yeah, i slept on that for a while. maybe it's time to look into it, as I'm not really needing to upgrade my processor/motherboard yet.

os 3.03 and 3.04, trouble with autoload. It doesn't boot on autoload, always on internal memory for both OS. i've tried 3.04 yesterday and got a no-reason crash and got my files in autoload replaced by those in internal memory trying to save entire memory.