wrong sample is triggered on playback

Hey guys Im just kinda getting back into the 1K and I have been getting some weird sequencing problems. I threw together a program today with stuff in three of the banks. Uploaded everything from my g5 mac to the MPC. All mono samples at 16bit 44.1k. All the samples trigger fine through the pads but on play back Im not getting the sequence as I played it. Samples are being substituted for others in the program or they are just not being reproduced period. I tried reloading everything multiple times but it will just not sequence the way its played.

I tried to search the forums but couldnt find anything about this issue.

I am running the most current version of JJ OS...

Anyone have an Idea for me on the problem. Sorry if this is a noob issue but Im dumbfounded

make sure you got the right program selected for the tracks you got sequenced.
i still do that accidentally.

yeah man it is in the right program...Its crazy I know

Are you loading from CF drive? If so, did you remember to reformat your card after you installed JJ OS? The reason I ask is that it is possible you have corrupt data that was saved with an AKAI OS. Is it happening with all your projects or only certain ones?

Go to Step Edit and try to play the recorded notes from there (F6). This might give you a hint where the problem is.
Also check on polyphony (program or pads set to Mono ->) and mute groups.

Rub-ISH wrote:Hey guys Im just kinda getting back into the 1K and I have been getting some weird sequencing problems. I threw together a program today with stuff in three of the banks. Uploaded everything from my g5 mac to the MPC. All mono samples at 16bit 44.1k. All the samples trigger fine through the pads but on play back Im not getting the sequence as I played it. Samples are being substituted for others in the program or they are just not being reproduced period. I tried reloading everything multiple times but it will just not sequence the way its played.

I tried to search the forums but couldnt find anything about this issue.

I am running the most current version of JJ OS...

Anyone have an Idea for me on the problem. Sorry if this is a noob issue but Im dumbfounded

Check the midi assignment of the pads your program, this is most likely the problem you have. MIDI note data overrules pad number data when there is conflict, this is probably why your sequence does not playback OK. Set the track to MIDI then DRUM and see if the playback is affected.

Thanks guys I will try all that stuff. It is only happening with one program so far. If I change the desired program and then tap out what I want with an alternative program then switch back to my desired program the sequence plays fine.

There must be some event in step edit that causes a program change.

I'm having the same problem on one of my programs. I had some drum samples on Bank A; I loaded a bunch of bass samples on Bank C and imported a MIDI sequence to play the bass line. I altered the MIDI notes in Bank C to match the bass notes and the bassline played fine, except when the note coincided with a drum pad on Bank A, in which case it played the drum sound instead, so I would change the MIDI note on Bank A to be out of range and the bassline played fine. Then I put some Hihats on Bank D and recorded a track with the hihats. When I play back the sequence, that track triggers the wrong samples. When I look at it in step edit, the track shows that it's triggering samples on Bank A, and when I try to change the note in step edit it won't even show any notes in Bank D.

I think it's got something to do with the way I set up the Bass instrument MIDI notes in Bank C, but I haven't figured it out. If anyone has some insight into this little puzzle, I'd much appreciate a tip.

thanks.

Well in case anyone's following this, I solved my own problem:
it turns out to be pretty easy actually. In program mode, when in the note assignment page, there's an asterisk (*) next to notes that are not unique, so you just spin around the data wheel 'til you find a note number that's not taken. Now it works fine.

barneyjones wrote:Well in case anyone's following this, I solved my own problem:
it turns out to be pretty easy actually. In program mode, when in the note assignment page, there's an asterisk (*) next to notes that are not unique, so you just spin around the data wheel 'til you find a note number that's not taken. Now it works fine.

yeah it sounds like the same pad was triggering 2 samples, and possibly the pad wasnt set to poly, or there was a mute group involved... glad to hear you worked it out

when you load the PGM in bluebox, you can quickly scroll through the pads to find any conflicts, its alot easier than checking all the params in MPC