OS 2.1 Pains - Please read first post.

d_loc wrote:No, there's a delay after you lift your finger off of Stop, before Play will work. This worked smoo0thly in older os, now it donesn't.

ok, i finally understand, thanks.

the best thing to do is to report it to akai support.

Another bug: Normally, you can select the digit to be altered by pressing shift+< / shift+>. In Seq Edit mode, it doesn't work. You can select the digit, but the one altered is always the last one.

Did anyone realise you can stutter the start of sequences by going to 'Next Seq' and keeping your finger on 'Sudden' whilst tapping the appropriate sequence button? You have to be tight with the timing but if Play/Stop isn't working this could be O.K.

I am really appreciative of the new OS and for a lot of people's input from here.

The biggest thing I was looking forward to with the new os was being able to bypass using recycle with zoning on the 1000. I'm liking the zoning feature (this is my first MPC), but I dont like that you are forced to do it in mono, looking only at the L or R part of the sample. This has already come in handy on a couple new beats, and I like having this as an option, on some samples it sound like crap. I see you can get around this with just using the extract feature, but has anyone found a way with just zoning? The closest I came was with panning the sample far L or R, then resampling that thru the main out in Mono, not stereo, then chopping that mono sample. This can sound a little better, but not as nice as just a plain stereo sample. Anyone have any ideas, or is this just the nature of the beast?

not sure if anyone else has experienced this but.........when im using the mpc as a midi sequencer for my motif rack the volume of the sounds will jump back to 100 anytime i record a new track. so basically....i have horns at volume 66 and when i go to record ie. bass on the next track, the 66 will jump back to 100....and this is for EVERY dam track i record in midi interruption of the work flow is NEVER good!

someone tell me im trippin and need to go read more lol...

figured out a work around. i inserted a cc message for volume

recording realtime w/ qlink slider creates extra bars at the end of the sequence

Antonym wrote:recording realtime w/ qlink slider creates extra bars at the end of the sequence

Weird, I haven't run into that. What was the exact process?

thynctank wrote:

Antonym wrote:recording realtime w/ qlink slider creates extra bars at the end of the sequence

Weird, I haven't run into that. What was the exact process?

i never ran across that either. Ant, can you be more specific?

sure.

i had 1 sample that was quite long - a tune drop that i had done on the sp404. thing is with the sp404, when you pitch shift the timing stays the same. so what i like to do is have it drop on the sp404 and resample it in the mpc. then go and assign it to qlink and make that drop as well - this effects the timing and the double pitch drop is a cool effect since both machines do it differently. very interesting sound.

on the same track i wanted to blend out a synth i had going in the previous 8 bars, so i resampled it from reason and did a tune drop on that w/ qlink as well. i did a couple sweeps overtop each other to get a weird grainy sound (As i've described before).

in perfecting these sweeps, i found that bars were somehow being added to my seq. i'm almost positive this is due to realtime filter sweeping....maybe of a really long file? ie if your file BECOMES longer due to the fact that you're stretching it beyond 8 bars, maybe it pushes the seq longer.

got me? it's no problem, just takes a little truncation, but i thought id mention it.
peace
nym

I'll see if I can duplicate that tonight. I've done a few passes of sweeps before but never ran across either your glitchtech sound thing or this extending bars issue. I guess I'll have to get crazier with it huh.

Anyway, long as you have a workaround for now... hopefully Akai will [someday] put out at least one bug fix revision for this OS.

-tank.

glitchtech - take a long sample and set it to qlink and then just record 2 sweeps from hi to lo or vice versa. make sure you're just overdubbing. the result is that the qlink records its position at different intervals, so the previous sweep still exists. what happens is that both sweeps are going to same place, but take slightly different times to get there. so the sweep becomes a bit garbled. the same stuff happens in reason and other midi sweepable apps.

beautiful noise, great for transitions.
peace
nym

Ant, i take it you have loop on on the sequence? if so it might be one of those things that happens when recording midi loops. i get it in reason quite a bit, where if you hit a note that's supposed to be at the beginning of the bar a little early while the cursor is still at the end of the looped portion, it'll put in a note that extends over the right hand loop marker.

hope this helps.

There's a setting on the MPC (under Other maybe?) that's supposed to prevent sounds from going beyond the end of the sequence, etc. Forget its name...

thynctank wrote:There's a setting on the MPC (under Other maybe?) that's supposed to prevent sounds from going beyond the end of the sequence, etc. Forget its name...

Its the 'Over-the-end-of-a-sequence-note-stopping' feature. Page one hundred and twenty-twelve in the manual. simply turn it on.