any new bugs/problems since OS2.10?

i'm starting to think that since i upped to v2.10 my MPC isnt sending program changes, anyone got this problem?

i decided to revert to v1.07 and it sends them fine, (i've been using 1.07 all last year using prog changes to outboard synths shitloads - no problems like this).

but since i went to v2.10, and recenently dug out some of last years material, i noticed it wasnt playing right, traced the problem to it not sending program changes....so i'm certain its the new OS thats at fault.

AKAI, sort yer shit out.

i think the sequencer side of things have been neglected in 2.10, due to all the bitchin by the choppers. Have you noticed it now sends out a program change to prog 1 if you tap stop 3 times, i've mailed Akai 'bout this but had no response yet, for me the enhanced sampling features are less inportant to me than a fully functioning sequencer.

ive been geting wrong file when i try to load a sample or a programe. i dont know what it is.

ok - shame.

i havent had the same issues as you guys, but yeah, leads to a common thread: swap OS's when u need what it can do best.

i totally depend on this prog-change feature 'cos i use the sequencer onstage, sending patch changes to my nordModG2 engine etc....but i'm more likely to use the v2.10 at home in the studio for messing audio up, getting sounds, composing etc..... then i'll have to load v1.07 for live shows, to perform what i made.

seems stupid, but hey, this is all product of the modern age isn't it? i got used to software being released before it got finished, now hardware is more s/ware dependent, we see the same deal.
good luck y'all,
rB)

yep, i get that 3x 'stop' = midi send.

definately a case of "shit lads lets make the mpc1000 do all those wicked dsp tricks everyone was rinsing five years ago, oh , and make sure you frigg all the dudes who can compose decent midi!" hehhe

only joking really cos i guess any improvements would be interesting on this little box, i love it still.... but you'd expect a less flakey development/bug finding strategy that surf the users forums for complaints after the updates release.
rb)

os 2.10 does send program change. have a look in the new manual. (ctrl + F in acrobat, and you'll find it in less than a minute)

no, i know it says so in the manual, what i'm saying is that i think my mpc100 aint doin' wot it should.
and i think its cos of the new os.

Akai need to take a customer relations lesson from www.scratchlive.net.

Not only can you request features there and actually be heard, you can freely beta test the software months before release and give your feedback on any problems. This is then looked at, commented on and in many cases resolved by the Rane/Serato team themselves, all whilst keeping the customer fully updated.

More companies should learn from them, it equals one very happy customer base.

hy'all,
yeah i have a running dialogue with one of the guys at akai support right now, he's trying to help, really is.

but it appears that i'm the only one with this problem(!?) cos he can't find the same problem on his mpc......i even have two mpc's sat here, a brand new one - just out the box, and my trusty old(er) one....and both show the same 'bug'.

V1.07 mpc can send midi program change entries in sequencer tracks fine, but in v2.10 it doesnt work.

help! - can any one try sending a few program changes to one of their outboard midi synths, see if its working on their gear?

i've read and searched the manual, but see knowhere that really gives me the impression that i have something set up wrong.....especially as these sequences work fine in the earlier OS's.

rB((

scratchlive's customer support is absolutely incredible. i've never seen anything like it. what a great goddamn program.

best of luck for your problem, man - that must be really frustrating.

i was having some issues last night with my mpc/midi...
i recorded 4 bars of midi (using one of the program change programs (No.1)), and it would play fine for acouple loops then gradually fade away until the module wasn't recieving any info on that track. Really strange, and somewhat annoying. I think the sequences and programs are more prone to data corruption or something with the new os.
Anyone else have this particular problem or a solution for it?

they've figured it out at akai/numark.
it appears that any old sequences (those made before os V2.10) that may have program changes in sequencer tracks.....have their p-changes off by default.

and in order to get them to send the changes, prg: 'no.1' (or any no. 1-128)
has to be set to the right p-change number for the desired p-change to occur.

it doesnt

but hell, that means if i want to use old (4weeks old!!!) patterns with p-changes, i gotta edit ALL my seq's.

i'm weakened!