
By damien907
Thu Dec 29, 2011 9:37 am
sometimes my pads act funny when im making a beat on my 2500.
just to start off im using jjos 2xl v 2.22
it just started happening again so im gona tell you whats happening right now.
i have a closed hihat sample sample on pad 3, another closed hi hat sample on pad 4,
and an open hi hat sample on pad 7 (right above pad 3)
nothing on pad 11 or 15, the other pads right above pad 3 and 7 respectively.
right now when i trigger pad 3 ( it says im playing pad 7 open hi hat), my program verifys that im hitting pad 7 too, but im hitting pad 3.
and when i hit pad 11 the program jumps to (pad a 15) which shows a blank space, but its triggering a closed hi hat sound.
now when i hit pad 15 it says im playing pad A3, which is my closed hi hat. its like sometimes it bumps all of my samples up a pad for some reason, do you think the pads sensors are wired wrong or going out?
i got it custom made, do you think the guy that made it had messed up the sensors some how?
what do you think i could do to fix this?
sometimes it just goes away and fixes itself, but it seems like its locked on pretty good right now.
have any of you experienced something similar to this?
just to start off im using jjos 2xl v 2.22
it just started happening again so im gona tell you whats happening right now.
i have a closed hihat sample sample on pad 3, another closed hi hat sample on pad 4,
and an open hi hat sample on pad 7 (right above pad 3)
nothing on pad 11 or 15, the other pads right above pad 3 and 7 respectively.
right now when i trigger pad 3 ( it says im playing pad 7 open hi hat), my program verifys that im hitting pad 7 too, but im hitting pad 3.
and when i hit pad 11 the program jumps to (pad a 15) which shows a blank space, but its triggering a closed hi hat sound.
now when i hit pad 15 it says im playing pad A3, which is my closed hi hat. its like sometimes it bumps all of my samples up a pad for some reason, do you think the pads sensors are wired wrong or going out?
i got it custom made, do you think the guy that made it had messed up the sensors some how?
what do you think i could do to fix this?
sometimes it just goes away and fixes itself, but it seems like its locked on pretty good right now.
have any of you experienced something similar to this?









