Post your views and questions about the Akai MPC2500
User avatar

By Gab.Gato Mon Jun 04, 2007 10:01 am
- Im one bitching about the Contin.Sample/Midi bug, its a real issue to me, especially during livesets.

- I think its good to have 128 pgms, also if notes are limited i can load lot of PGM instruments together, useful!

- The Sync thing is a very good imo

Also i have to add that the 'Save' issue show up just if i do USB movements, i usually overwrite without problems, but if i do main and big changes i do create a new folder tho. Would be nice to be a bit safer...
I also usually save twice, HD & CF

The Only thing really catchin in the JJos is that realtime pitchin on the ext input, id like to try it live :shock:

By Siver Mon Jun 04, 2007 5:48 pm
episode wrote:Many people act like the save bug is such a big issue. I mean, what's so hard about creating a new folder and not overwriting each time you save.


how is the save bug NOT a big deal? i mean when you pay $1500+ for a piece of equipment shouldn't you be able to save without the fear of a bug that makes you lose all of your work? a saving bug is the worst kind of bug there possibly could be considering that it's worthless using something that doesn't even save properly...i know that there are ways to avoid this issue, but you shouldn't have to save a certain way so that your mpc doesn't get **** up....they did seem to fix the sync issue so hopefully this saving bug is their plan for their next os.
User avatar

By episode Mon Jun 04, 2007 8:04 pm
Siver wrote:how is the save bug NOT a big deal? i mean when you pay $1500+ for a piece of equipment shouldn't you be able to save without the fear of a bug that makes you lose all of your work? a saving bug is the worst kind of bug there possibly could be considering that it's worthless using something that doesn't even save properly...i know that there are ways to avoid this issue, but you shouldn't have to save a certain way so that your mpc doesn't get **** up....they did seem to fix the sync issue so hopefully this saving bug is their plan for their next os.
it's not a big deal because the MPC still allows you to do work and save it, even if you have take save it a certain way. i'd consider it a big deal if the MPC didn't allow me to save anything AT ALL.

By Siver Mon Jun 04, 2007 10:32 pm
episode wrote:it's not a big deal because the MPC still allows you to do work and save it, even if you have take save it a certain way. i'd consider it a big deal if the MPC didn't allow me to save anything AT ALL.


do u agree that it's a big enough deal for akai to fix? i do see wut u r saying but lets just hope that akai doesn't feel the same way you do otherwise it will never get fixed?
User avatar

By Jessiah Tue Jun 05, 2007 5:15 am
Im SO excited about the new OS. thats cool, SO OS... anyway


I was using the original OS on my 2500 for a while... the only thing I had trouble with was it would trigger other pads when I was only trying to hit one pad. It would put other pads in, and really make things impossible, but it would always go away after a while (no restart). Has anyone had this problem before? I'm sure the new OS has some nice fixes in it though... can't wait. I'll be doing my testing tomorrow!!!


Thanks dad!
User avatar

By jahrome Tue Jun 05, 2007 5:20 am
The OS has nothing to do with pads triggering other pads...that is a hardware problem.

By Anabolic Tue Jun 05, 2007 5:44 am
midi sync'd fine, f a save bug! save on your cf and overwrite:)
User avatar

By episode Tue Jun 05, 2007 8:03 am
Siver wrote:do u agree that it's a big enough deal for akai to fix? i do see wut u r saying but lets just hope that akai doesn't feel the same way you do otherwise it will never get fixed?
sure i do. i admit, i've lost a few projects to the save bug. but i've made my peace with it, and i've moved on. would i like akai to fix this issue? of course. but i've learned that creating new folders for making edits is good practice anyway. i've made an edit, saved it, then loaded it up the next day realizing that it's not what i really wanted. so i just went back to the previous save before that. something definitely not possible had i just overwritten my project files.

as for the save bug... bottom line is that at the end of the day, i'm still able to create my music with the bug hindering my performance.
User avatar

By Kayelel Tue Jun 05, 2007 10:57 pm
barznbeats wrote:Midi works perfectly with PT!

I did 7 solo'ed passes and they all started at 00:00 and ligned up perfectly!


Anyone else able to get the 2500 synced with ProTools?
I can't! I think my problem lies in PT - don't know how to set it up to sync the MPC...
User avatar

By dablunt Wed Jun 06, 2007 11:49 am
jahrome wrote:The OS has nothing to do with pads triggering other pads...that is a hardware problem.


J,
On the release notes http://www.akaipro.com/software/OS/MPC5 ... _Notes.pdf it says that bug fix number 2 is "Pad On threshold reduced" - is that not addressing this issue? I dunno?

Number 3 intrests me as well - anyone seen any new error messages displayed?? I ain't.

Yeah, what an amazing update this was. You would of thought that if they were looking at the MIDI mute feature, that they would at least feckin sorted out the Immediate Stop on the samples! Doh. :roll: Still, I suppose you can use it when you are tracking out, (with samples set to Through. )

128 Progs, something that.... Jahrome's (I think) wanted for some time I believe - now to get those 300,000 notes, right ?!

Bug Fixes - so does MTC work 100% like it should now?



db
By soundasleep Wed Jun 06, 2007 8:22 pm
whattup... so i'm really not much for akai-bashing. love the mpc's. love akai.... BUT.... ever since OS1.2 and up akai's midi-beat clock sync has been off for the 2500. numerous people have reported this with protools, cubase, abelton live, digital performer, etc. i use protools and sometimes digital performer and that's how i like to sync so i've had to use OS1.1 so it would sync right.

well when 1.23 came out and some people said the sync issues were corrected i was relieved. finally got around to loading it up just now, and loaded up a beat i tracked out yesterday using OS1.1 and synced the mpc to protools to see how it would sync.... WAY OFF. this problem has not been fixed. i retracked the beat (actually a 2track submix) alongside my original drum submix to check the waveforms, and exactly as 1.2 to 1.22 did the drums are all landing early.

so i finally downloaded the latest JJ OS, loaded it up, and loaded up the beat again and retracked the drum submix and it was pretty much exactly how the OS1.1 version of my beat lined up in pro-tools.

so i finally bought the JJOS for the 2500 (i've been using it on my 1k and love it)

if anyone can tell me how to take a screen shot on my mac i'll show you exactly what i'm talking about with all 3 tracks right next to each other.

this is wack for people who use midi beat clock to sync. a very basic feature.

lame.

long live JJ
User avatar

By jahrome Wed Jun 06, 2007 8:42 pm
So you have exactly what you need now...seems you should be happy.

By soundasleep Thu Jun 07, 2007 12:21 am
jahrome... you're right hopefully i'm straight now with JJ.

here's a screenshot of what i was talking about. the first stereo track is my drums as tracked using akai OS1.1. they fall within the grid like they're supposed to. the second track is the same drums tracked with OS2.3, and the third is using JJOS5.20

this is all wrong and after however long it's been since this problem started akai should have fixed this issue.

Image