What I dislike The Most About The 2500

is how easy the black shinny area around the pads scratches. No big deal at all considering that it doesn't effect anything, but it still sucks when little scratches start to appear. It's like a scratch on a car..Lol...Anyone else notice this and has anyone been able to get rid of any scratches?

you are kidding right....how bout the TC , or not syncing with ProTools or Not being able to Simult Layer filters .... I guess it's all bout looking cool and not how it works for you?

it was kinda a joke...lol....wut problems r u having with TC?

Siver wrote:it was kinda a joke...lol....wut problems r u having with TC?

haha. you lie.

Simult was never an advertised feature.....

If Pro Tools can transmit Midi Clock, then the 2500 can sync to it. The 2500 can also act as both an Midi Clock and MTC master. The word is still out on whether it can sync to MTC (like the MPCs of the past) as a slave though.

TC should be working just fine.

its such a solid mpc, How can you even dislike anything? bugs can get worked out the product is 150% as is though!

ZAM13 wrote:you are kidding right....how bout the TC , or not syncing with ProTools or Not being able to Simult Layer filters .... I guess it's all bout looking cool and not how it works for you?

2500 V1.20 Slaves to PT with MIDI Beat Clock as well as with MTC

Siver wrote:it was kinda a joke...lol....wut problems r u having with TC?

I meant note repeat ,which has been addressed on the new Os , yeah and I realize the protools options I was just bringing up issues other that the crappy paint that has no bearing on how it works ....

Yup, mine has a few scratches near that pads & I baby my machine, don't even wear a watch. I have a 2nd hand 60II and it doesnt' have a single scratch on it. I guess the powder coat or whatever isn't very durable.


D

boomspot wrote: I have a 2nd hand 60II and it doesnt' have a single scratch on it. I guess the powder coat or whatever isn't very durable.


D

No wait till the mysterious CROP CIRCLES show up on your 60.

jahrome wrote:Simult was never an advertised feature.....

If Pro Tools can transmit Midi Clock, then the 2500 can sync to it. The 2500 can also act as both an Midi Clock and MTC master. The word is still out on whether it can sync to MTC (like the MPCs of the past) as a slave though.

TC should be working just fine.

only if you use os 1.1 or earlier. if you lock to protools with 1.2 and up it locks up but not on beat. the mpc will play early.

The Maker wrote:2500 V1.20 Slaves to PT with MIDI Beat Clock as well as with MTC

read what i wrote above.

soundasleep wrote:
only if you use os 1.1 or earlier. if you lock to protools with 1.2 and up it locks up but not on beat. the mpc will play early.

Specifics?? As a SLAVE or Master. Also, have you tried inserting blank bars at the start within the MPC and/or Pro Tools? It may be possible to make settings within Pro Tools to get it working right.

jahrome wrote:
Specifics?? As a SLAVE or Master. Also, have you tried inserting blank bars at the start within the MPC and/or Pro Tools? It may be possible to make settings within Pro Tools to get it working right.

whattup jah...

this has been covered in two previous threads. one that i started relating to protools and another relating to nuendo (i think).

but basically if you slave the mpc to protools using midi beat clock using os 1.2 or later the mpc hits (quantized on the one in mp) fall before the beat a little bit. it locks up and stays consistent but it's always early. and i always add blank bars. i've tried with digital performer also and had the same problem. i've been using 1.1 because of this. and any sessions that i had started before 1.2 were not locking up if i tried to slave the mpc to add anything. it's a real drag and i'm not the only person who's having this problem.

soundasleep wrote:

The Maker wrote:2500 V1.20 Slaves to PT with MIDI Beat Clock as well as with MTC

read what i wrote above.

Not for me it doesn't???