samples cutting out

samples laid out with drums and everything else, and my sample cuts out for a few bars then come back in. What is this? Is it the OS? I think I had something like this happen with 2.1

check if your program is poly or mono by going to program mode

this could be anything from the automatic "mono" that gets applied to pgms when you make them OR polyphony mismanagment. keep your eye on the voice detector in the global screen, or in the top right in pgm mode.

so what does this need to read? poly or mono? when is one wrong or right?
The problem Im having is the sample plays but as I hit the pads on a different track the sample cuts out and comes back when I stop

yup. sounds like polyphony mismanagement.

go check out the voice counter and see what it's reading. start w/ all tracks muted then go 1 by 1 turning em on. look at the VC each time.

so the vc should read what? everything is poly

Are the other pads you hit that cause the sample to cut part of the same program? If so, could this be a mute group issue? From memory mute groups are changed in the PROGRAMS=> PARAMs page.

hope this helps

the sample is in a different program.

It does it after the 3rd bar when going into the 4th. It doesn't matter the settings or what type of sound it is. It's a bug.

Does it still do it if you mute all your other tracks??
Sounds like you over your polyphony limit fo sho

i do have this problem, when i use the next seq feature my new sequence is sometime buggy (some parts don't play and arrive "randomly")

I run into this issue all the time. Especially when using the 16 levels feature. I find making the sample mono helps. But the situation really frustrates me and make me feel that the hardware is very limited. This is one of the reasons I like using Reason as a sound module via midi from the MPC because I never have any issue like that with reason.

mkl... wrote:i do have this problem, when i use the next seq feature my new sequence is sometime buggy (some parts don't play and arrive "randomly")

damn, it reminds me an old bug introduced after the recordable track mutes i think. did you report that ? did JJ answer ?

yes i did it several times...

Man I hope they hurry up and fix this problem.

I went back to 4.44 and loaded the same beats that I'm having trouble with. They do it in there also, but if I load all the samples and rebuild the beat the same exact way, it doesn't do it.

All my beats made with 4.51 up are bad. Damn what a bummer.