Layered sounds doesn't sound consistent!

jacey714 wrote:

dmarz45 wrote:

dmarz45 wrote:U need to adjust the start time and decay time and play with it until it sounds right...

It does sound off if you play it in 32nd notes but I dont know who uses 32nd note kicks at all? Does it really effect your beats that much? It does happen on my machine too but it still sounds fine and doesnt effect the way I make beats...

It's just another test that I did...The original problem with multi-layered samples is a huge problem for me cuz I can hear it go in and out constantly...I use a lot of multi-sampled sounds for my drums so it's absolutely imperative that it works the way it's supposed to...Also, for a machine that costs $1999 it SHOULD just work!

yeah I agree with you that it just should work but hopefully they fix that but its outta our hands...

This past week I went to 2 different Guitar Centers and tried out the MPC5000 and found the same problem in both units...so this seems to be a problem with the entire line and not an isolated problem with few machines...I tried the MPC2500LE right next to it and it played layered samples with no problems...

So if you own a MPC5000 you probably have this problem and probably don't know it yet. If you haven't been layering samples, you probably haven't looked into this problem...but it's there...

I do a lot of layering of kicks, etc. so this is definitely a deal breaker for me...If this problem doesn't get solved in the next OS update (if there is one)...this one is going straight on Ebay!

yeah, ... too bad the velocity you strike the key of a steinway grand piano effects the timbre, or else it might've been a good instrument.

oneday2one wrote:yeah, ... too bad the velocity you strike the key of a steinway grand piano effects the timbre, or else it might've been a good instrument.

What was the point of that statement ? I dont know but it was funny

or the blues might have been good music if it was in tune........

It sounds like a phasing issue - and it could just be the specific samples have greater phase difference than other layered sounds.

I dont know if your MPC is broken. I dont have mine in front of me to test this out either.

One possible work around would be to resample the layered kicks and make them one sample. That will save polyphony as well.

Hope this helps.

noisetheorem wrote:It sounds like a phasing issue - and it could just be the specific samples have greater phase difference than other layered sounds.

I dont know if your MPC is broken. I dont have mine in front of me to test this out either.

One possible work around would be to resample the layered kicks and make them one sample. That will save polyphony as well.

Hope this helps.

I have 4 kicks layered that need to be EQ'd separately...and also goes back to the fact that for $1999 it should just work without having to work around it...

i just want to know when they're going to fix that damn steinway!

okay, here's my point. i, personally, resample down to a single .wav file, but that's just me. i haven't truly noticed yet this happening from my machine, but if you have already tested on several machines, then i believe you. you have convinced me that the mpc5000 does a wierd thing.

the only advertised feature is for it to play the layers within a programmed pad at random.

but that is not what you are experiencing. so lets say you are 100% scientifically correct, .... that it simply sounds different when you hit the pad on different occasions inside the space-time continuum.

and lets say you are also correct that a $2000+ machine should not be doing this.

okay, ... we'll accept it all.

so what is it that you exactly want to know now? you already know your machine does this. you already know you don't like how it costs as much as it does. are you hoping we are going to create some miracle and make what is not true now, become true in the future?

or do you want us all to band together, trash all our mpc 5000's, and boycott akai forever? or at least the 5000 part?

i simply can't understand your angle.

maybe 2 or 3 pages ago i thought your angle was to investigate the problem, ... but the problem's been investigated, the outcome is clearly apparent, ... so what is it that you're after?

when something doesn't work in the army, i'm airborne infantry, ... so when a .50 cal machine gun doesn't work as advertised, (which is the case 99.999% of the time), .... what do we have to do? we can't just go get a new one, and even if we did, it'd probably have problems of its own.
so what do we do? ... we just deal with it, .... we 'make it work'.

if you have the time and money, get rid of the 5000 and get something else, ..... or just 'make it work'

oneday2one wrote:i just want to know when they're going to fix that damn steinway!

Even with that terrible velocity/Timbre issue, I've heard that one or two people have actually managed to get a reasonable tune out of a Steinway Grand Piano.

Some people can make music with any old thing huh!?!

oneday2one wrote:...if you have the time and money, get rid of the 5000 and get something else, ..... or just 'make it work'

I think your sense of irony is being lost on a few guys,

What you're really trying to say is "Y'all shut the F@ck up and start making some music instead of complaining like a bunch of little girls!!!!!!"

Right?

Yeah I hear ya.......

I thought this forum was for people to post things that concern all MPC5000 owners. This problem is definitely something that needs to be addressed by Akai and is a legitimate problem. For you to tell people to just accept the problem and find a way to get around it is absolutely ridiculous. Why do we even have a whole section on "2.0 Bugs"? Just tell people "good luck" and find a way around it. I have a legitimate problem that affects the way I make music. I can't spend hours going through ever drum track in Protools for odd hits every time I track a song. I don't want to turn this thread into a place for smart ass arguments. This thread was started to first find out if the problem was isolated to a few machines or the entire line...and now that the problem is found we need to get as many people to mention this as possible so Akai can fix this on their new OS...if there will be one that is. Just keep in mind that it's 2009...and any irregularities in music should be done on purpose...not cuz the machine is out of wack.

jacey714 wrote:I thought this forum was for people to post things that concern all MPC5000 owners. This problem is definitely something that needs to be addressed by Akai and is a legitimate problem. For you to tell people to just accept the problem and find a way to get around it is absolutely ridiculous. Why do we even have a whole section on "2.0 Bugs"? Just tell people "good luck" and find a way around it. I have a legitimate problem that affects the way I make music. I can't spend hours going through ever drum track in Protools for odd hits every time I track a song. I don't want to turn this thread into a place for smart ass arguments. This thread was started to first find out if the problem was isolated to a few machines or the entire line...and now that the problem is found we need to get as many people to mention this as possible so Akai can fix this on their new OS...if there will be one that is. Just keep in mind that it's 2009...and any irregularities in music should be done on purpose...not cuz the machine is out of wack.

It is yes and that's why there's a sticky OS2 BUGs thread at the top for you to post ANYTHING which may be a glitch or bug.

Akai are already aware of this particular issue, it was raised as a bug during OS2 beta testing and is already documented on Akai's bug tracker.

Will this issue be fixed in the next OS update? I don't know at this point, but the word on the street is that there will be a further OS uplift to tighten up the 5K OS and fix up some of these niggles in OS2. You never know Akai may even have a few functionality improvements up their sleeve. That would turn a few heads wouldn't it...

Just be patient, document it in the bug thread and work around it if you can until the next OS update.

All this negativity is starting to wear people down and that's why a lot of the visible support on the 5K threads has dwindled.

We used to have a good 5K community with a lot of very experienced 5K users and a group of Beta testers who would regularly contribute on these threads, most don't visit regularly anymore because of the 'complainers' and the 'haters'.

Try and keep it a bit more positive guys - the future is bright!

NorthernElite wrote:

jacey714 wrote:I thought this forum was for people to post things that concern all MPC5000 owners. This problem is definitely something that needs to be addressed by Akai and is a legitimate problem. For you to tell people to just accept the problem and find a way to get around it is absolutely ridiculous. Why do we even have a whole section on "2.0 Bugs"? Just tell people "good luck" and find a way around it. I have a legitimate problem that affects the way I make music. I can't spend hours going through ever drum track in Protools for odd hits every time I track a song. I don't want to turn this thread into a place for smart ass arguments. This thread was started to first find out if the problem was isolated to a few machines or the entire line...and now that the problem is found we need to get as many people to mention this as possible so Akai can fix this on their new OS...if there will be one that is. Just keep in mind that it's 2009...and any irregularities in music should be done on purpose...not cuz the machine is out of wack.

It is yes and that's why there's a sticky OS2 BUGs thread at the top for you to post ANYTHING which may be a glitch or bug.

Akai are already aware of this particular issue, it was raised as a bug during OS2 beta testing and is already documented on Akai's bug tracker.

Will this issue be fixed in the next OS update? I don't know at this point, but the word on the street is that there will be a further OS uplift to tighten up the 5K OS and fix up some of these niggles in OS2. You never know Akai may even have a few functionality improvements up their sleeve. That would turn a few heads wouldn't it...

Just be patient, document it in the bug thread and work around it if you can until the next OS update.

All this negativity is starting to wear people down and that's why a lot of the visible support on the 5K threads has dwindled.

We used to have a good 5K community with a lot of very experienced 5K users and a group of Beta testers who would regularly contribute on these threads, most don't visit regularly anymore because of the 'complainers' and the 'haters'.

Try and keep it a bit more positive guys - the future is bright!

+1