Forum to discuss all matters relating to the MPC1000 and MPC2500 operating systems created by 'JJ' (all versions).
User avatar
By astronaut Fri Jun 22, 2012 8:50 am
greets

so I reported to JJ what I thought was bug, but it turns out it's not.

here is my message:

Pad cuts off sample (set to Loop&hold) in another track.

Description:

1) In track 01 create and assign program01 with a Loop&Hold sample01 on A01. 2) In track 02 assign another program, e.g. drums01.
3) go to track 01 and hit A01. The MPC now plays sample01 in a loop continuously.
4) go to track 02 and hit A01, the MPC stops playing sample01 in track 01.


I forgot to add that this happens while the MPC is stopped, so it's not playback of recorded notes were talking about.

Murrai says that this can't be changed since it will create problems.

Do you guys know of a solution to this specification :) ?
User avatar
By m:t:c Sat Jun 23, 2012 2:48 pm
sadzik wrote:I've got similar problem but only when I use midi keyboard. Note is pressed in every program and track, it pisses me off a lil bit


hmm sounds like you got a different issue there. Double check your setup?
User avatar
By damien907 Sun Jun 24, 2012 4:30 am
maybe i dont understand your question, but do you have these samples in the same mute group? maybe changing them to a different mute group would fix it.
User avatar
By le rat Sun Jun 24, 2012 9:16 am
crossings wrote:does it do this if you assign the non-looped sample to a different pad? like B01?? maybe worth trying?...


Putting the loop&hold samples in another pad bank could be a workaround.
For instance L&H samples in bank D, then when going to the next track, bank A and so on...A bit annoying but as it seems to a be a specification problem we are a bit stuck.
User avatar
By astronaut Sun Jun 24, 2012 5:38 pm
le rat wrote:Putting the loop&hold samples in another pad bank could be a workaround.
For instance L&H samples in bank D, then when going to the next track, bank A and so on...A bit annoying but as it seems to a be a specification problem we are a bit stuck.


yep, that's the only workaround I see for now.