1000 timing sloppyness proven

Ok so I had a friend take a seq of mine and play it in his 2500 and record for me. Results was that none of the sloppyness I've been seeing was present. Maybe due to the cpu in 1000 possibly being weaker (their explaination why there was no timestretch in the 1000 initially).

This seq only had about 12-15 tracks total (I do house/techno). While not what I'd consider minimal it deffinatly wasn't that heavy or dense.

I solved the timing issue buy taking some of my sounds and loading into an S5000 and triggering that from midi. Seems the 1000 can trigger midi fine but not internal samples which is fairly ironic since thats what its supposed to be good at.

soundfile examples pls?

also, anyone know re: cpu.. i had a feeling the 1k and 2.5k have the same cpu, anyone know for sure?

No repost, no double post.

I have started to ntocie some timing issues also but thats because of latency i guess. Im using that east west collosus plugin and drums on the mpc.The drums are like a full 5 seconds quicker than the plugin. All i do is just shift time then mpc drums later by about 4or5 ticks, problem solved. I think the 1000s timing is too precise, maybe thats the problem. Turn of quantize and this will help.

Totally off topic but Medway have you got any house tracks to post up?

Back on topic, you could always make a sequence and save the entire memory with the samples and programs etc then send the folder to me and i'll open it up on my 2500. You can then resample the track into an audio file, i'll do the same and we could post both tracks to compare them.

I was under the impression that the CPU on both models was the same though.

can someone confirm this once and for all please? i thought the timing issues (if any) were nailed in 1.07? did akai ever acknowledge any timing issues? i may pick up a 1k bk but this is a dealbreaker (i'm from planet 60ii where timing is tighter than albas a55crack)

i still never have a problem with this, and again my stuff is very dense.

Antonym wrote:my stuff is very dense.

trying.....to......resist.......humourous........put-down.......can't.............hold.............it...............much......................longer....................ahhhhhhhhhhhhhhhhhhhhhhhhhhhh.
LIKE YOU, there i said it.

i'll take that.

medway do you think you could post an audio example, maybe with talkover?

I've always been rather annoyed with the 1000's timing issues. I used to be heavy into filtering the same sound, (it really only becomes bothersome when working with loops), and layering them to give it a new sound... but I can't count on the sequencer to playback with out occasionally causing the two sounds to start phasing. Sometimes it actually sounds kinda cool, but most of the time it sounds like crap

never had an issue and I layer my drums like crazy

nothing I couldnt fix in step edit. and if its something I need to fix there then it wasnt the mpc with bad timing - it was me.

deadbeat #1 wrote:I've always been rather annoyed with the 1000's timing issues. I used to be heavy into filtering the same sound, (it really only becomes bothersome when working with loops), and layering them to give it a new sound... but I can't count on the sequencer to playback with out occasionally causing the two sounds to start phasing. Sometimes it actually sounds kinda cool, but most of the time it sounds like ****

Hello,

Just a question to clarify - are you talking about two samples layered on a single pad, to trigger simultaneously, or two separate pads with different samples that are meant to trigger on the same tick?

If you're talking about the latter, and are setting up two samples on separate pads, one 'normal' and the other one passed through one of the MPC's filters, this could cause phasing, I would guess, since I would guess that the MPC's filters introduce a phase shift anyway. This is a wild guess at what the problem could be - it might not be timing.
ben

Hypes wrote:never had an issue and I layer my drums like crazy

nothing I couldnt fix in step edit. and if its something I need to fix there then it wasnt the mpc with bad timing - it was me.

drums aren't an issue because they're very short sounds and most of the time different sounds... although, if you want an example of how off the timing can be, try something like putting the same exact sound ( a snare for example) on two different tracks. I'm not sure what the exact conditions are to reproduce the phasing... whether the sounds have to be on different pads or what not. I do know that I used this this to my advantage once... I put the same snare on two pads and recorded them over each other on different tracks with the same timing and same swing... It will randomly phase from time to time while the sequence loops. It has no set pattern to when it will phase and when it wont. I've also encountered problems with filtering a loop into its high and low sections, and then getting a random phase. Maybe its just the fact that they're on two different pads... I never put much effort into figuring out why it was doing it, I just stopped doing a lot of filtering to my main loops.

I'll maybe fiddle with this a bit later. I've certainly experienced this kind of phasing when playing back a MIDI module sequenced by a PC DAW in sync with an audio track that I had recorded of the same sequence previously. Normally does denote some kind of MIDI jitter...

Yup, I recreated it. Sounds just like a MIDI jitter problem to me.

It's easy to recreate. Start a new sequence, set the loop length to 1 bar, and on the first track just place a full-level snare hit (I used nuskool, pad 6) on each quarter note. Replicate this exactly on track 2, and then hit play. On mine at least, you get the phasing effect every few bars or so on one or two of the snare hits.

Still love the 1k, though - for me it's the workflow...