OS version 3 bugs

le rat wrote: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.

you need to re-enable boot from autoload. it is somewhere in the "load" screen.

distortedtekno wrote:

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.

This was one of the two progs. I used to get the results in the first post. It's highly useful, but I'm not sure if there is any facility to view the messed up "illegal" non-midi messages like in the MAC app. I'd still be good for somebody else to try as my midi interface/music computer setup is all flakey mid-ninetes throwaway hardware that wasn't much good even when it was new. and even less reliable now (it's not the kind of stuff I would ever use for sequencing... jeez, forget it). Still, a modern MAC w/CoreMidi would be much more desireable for this test. People may have their opinions on this but I just don't trust Windows for anything, and accurate midi the least. If it says MAC OSX, Atari ST/Falcon or BeOS i'll take it but Windows midi ughhh.....

'course theres also other stand alone and/or test equpment options in this area but usually only the real midi tech savy folks have that stuff lying around.

i posted this at the first page of this thread, it still happens to me every time:

i have problems with notes not recording at the place i played them. some notes are at the place they should be but the rest was randomly at the beginning of one different bar.

now i found out that these notes record at the beginning of the first loop-bar, even if loop is off. this only works if the stuff i record is before the start-loop bar. if the first loop-bar is before the region i want to record, everything works as it should.

sorry, this is hard for me to discribe. i give two examples.

1. example:
loop: first bar: 30, last bar: end
loop is set to "off" on main screen!
i try to record: bar 5 - 7
some notes i play go to 030.01.00

2. example:
loop: first bar: 30, last bar: end
loop is set to "off" on main screen!
i try to record: bar 35 - 37
all notes record as i played them

can someone try to do this and tell me if he has the same problem?

i already submitted this to jj, but as i'm not from england/us my english is a bit rough and i don't think jj understands what i'm talking about. perhabs someone could translate it to super-easy primary school english?
thanks!

i finally understood.
you need to specify the every actions on the mpc.

press [main] -> main screen
select "loop"
press [window]
set "first bar:" 30
set "last bar:" end
press [main]
"loop:" off
press [record] -> mpc records
tap pads (before bar 30)
error: some notes randomly go to 030.01.00

i have not tried it as i am always in loop mode.

that's it!

*bump*

you need to re-enable boot from autoload. it is somewhere in the "load" screen.

thx for your help ! plus this is described in first JJ's page.
shame on me.

1/ Let mpc be slave to fruityloops
2/ Hit play on FLoops, mpc starts playing
3/ Hit overdub on mpc for specific track to record midi notes
4/ Check recorded notes, all is good

Here is the strangeness, when I go to note repeat and press say 1/16th note, the pad starts playing automatically, ie go shift--not repeat---1/16th note, a pad say A2 starts automatically w/o having to hit it. Now if I press record this pad does not record, but I can record other pads by the hitting them. This is after I disconnected all midi cables etc., turning mpc off rectifies the problem. So there appears to be a problem with midi sync in.

wavemartian wrote:1/ Let mpc be slave to fruityloops
2/ Hit play on FLoops, mpc starts playing
3/ Hit overdub on mpc for specific track to record midi notes
4/ Check recorded notes, all is good

Here is the strangeness, when I go to note repeat and press say 1/16th note, the pad starts playing automatically, ie go shift--not repeat---1/16th note, a pad say A2 starts automatically w/o having to hit it. Now if I press record this pad does not record, but I can record other pads by the hitting them. This is after I disconnected all midi cables etc., turning mpc off rectifies the problem. So there appears to be a problem with midi sync in.

So, you mean the problem stops when you switch to internal sync?

Sorry if I missed this, but is anyone else having problems selecting Program Banks from the "Pgm: No. (x)" popup window? The main PROGRAM CHANGE select seems to work O.K., but if I try to use either the MSB or LSB BANK SELECT options in the popup window I get *no* BANK SELECT messages, instead I get a PROGRAM CHANGE MESSAGE which is usually No. 1 but No. 15 crops up in there as well. This is regardless of the number shown in the MSB/LSB field.

So in short, if I try to scan through the MPC's on-screen MSB or LSB BANK SELECT CONTROLLER messages, I'm instead getting either a stream of PROGRAM CHANGE 1 commands or an alernating stream of PROGRAM CHANGE 1 and PROGRAM CHANGE 15 messages.

Don't think it's supposed to work that way...

I had a bug today where i loded a program i used in 21. fine and when i was recording A3 would then show as A4 and no matter what if i wen to atwp edit or pewssw window button in gri editor i can chage A4 to anything but A3 its impossible to enter a A3 . This happens on no other program ,


Is there someone i should send the program to ?

djdsk wrote:I had a bug today where i loded a program i used in 21. fine and when i was recording A3 would then show as A4 and no matter what if i wen to atwp edit or pewssw window button in gri editor i can chage A4 to anything but A3 its impossible to enter a A3 . This happens on no other program ,


Is there someone i should send the program to ?

i had the same problem some time ago. but i never solved it. i always had to redo the whole pgm..

More of a behaviour that was in 2.01 that isn't in 3.xx:

When hitting a pad with a sample in it and then going to the TRIM screen i was able to bring up that sample in the trim screen automatically and not have to scroll to it. Now it only works if i go into PROGRAM menu and hit the pad then go to trim. if i try the same thing from the main screen the sample does not change.

I dunno if anybody mentioned this yet but im not gonna search through the topic for it.

When I connect my masterkeyboard (CME UF6) to my midi in my mpc all of sudden goes to external mode :S the sequencer all of sudden speeds up tempo.
well i worked around that for a little bit but then i hit MODE+pad11 and then my mpc freezes on me!

elektrik_muz wrote:Sorry if I missed this, but is anyone else having problems selecting Program Banks from the "Pgm: No. (x)" popup window? The main PROGRAM CHANGE select seems to work O.K., but if I try to use either the MSB or LSB BANK SELECT options in the popup window I get *no* BANK SELECT messages, instead I get a PROGRAM CHANGE MESSAGE which is usually No. 1 but No. 15 crops up in there as well. This is regardless of the number shown in the MSB/LSB field.

So in short, if I try to scan through the MPC's on-screen MSB or LSB BANK SELECT CONTROLLER messages, I'm instead getting either a stream of PROGRAM CHANGE 1 commands or an alernating stream of PROGRAM CHANGE 1 and PROGRAM CHANGE 15 messages.

Don't think it's supposed to work that way...

have a go with 3.05. i tried with it and the bank change were fine.