MPC1000 OS V3.0 beta ?

cyklops wrote:

medway wrote:

cyklops wrote:Since the 25k and 1K share the same CPU i fell this should not be a problem for JJ Linn to to sort out, but i tested it now with a set of 808 snares and although the problem is still there it sounds different, its like it phases differently as it did with OS 2.10 but to me its still clearly there not sure if its improved but its for sure still there.

interesting.

for me I play a full bar smooth then the very next beat the sound phase's consistently for the next 3 measures then its fine for a full bar and a half, With OS 2.10 it would be more on off on off kinda like phases , but maybe I too am imaging things

ps Medway I always buy on beatport and nice tracks man, quite inspiring to hear the level of quality your tracks have.

Ya I swear its a bit tighter but who knows. I'm also getting random phasing when layering a copy of the same ample on top of itself (to get more volume, I know theres other ways but this was quicker). Sometime sit plays perfect other times I get phasing for a few hits or a measure or two, weird...

Thanks glad you liked them. The original mix to the new track I have on there called Motivo is pretty much all 1000, and a little S5000 mixed down live into wavelab. The other mixes were done before I had it so are Sx3 mixes.

co-sign..seems tighter to me too

phasing???? of course there is phasing when u play two sounds together, that is how a phaser works!!!!

if you play two sounds sample accurately on top of one another, there will be no phasing, just amplification of the signal.

however, no mpc is (yet) sample accurate in it's playback of samples, therefore phasing ensues.....

Vincepro wrote:Question: What do you guys that are excited about Grid Edit use it for? I have Grid Edit on the 4000 but dont get why you would ever want to input your drum hits on that grid rather than just playing them on the main screen. It seems counterintuitive to me so I'm curious.

Depends on what kind of thing you want to program. If you're doing IDM and want complex polyrhythms or glitchy beats, you're not going to want to bash that out on pads.

Vincepro wrote:I hope this guy works on the 4000 next...

Question: What do you guys that are excited about Grid Edit use it for? I have Grid Edit on the 4000 but dont get why you would ever want to input your drum hits on that grid rather than just playing them on the main screen. It seems counterintuitive to me so I'm curious.

I hope he simply does'nt get caught because this OS is a complete ownage...

Put the TC to off and go in the grid edit..Thats right 96 lines for a beat. It would be really cool to see the PPQN of the position while scrolling around.

Mr modnaR wrote:if you play two sounds sample accurately on top of one another, there will be no phasing, just amplification of the signal.

however, no mpc is (yet) sample accurate in it's playback of samples, therefore phasing ensues.....

not all the time tho. as i said in my post it was random. it would play for a few measures spot on and then phased for a bit and then back to none.

it doesnt need to be sample accurate timing to play two layered samples sample accurate. even the S1000 has a stereo coherence settign that locks the playback of two samples to be perfect.

since both samples are set to the same pad they should trigger exactly on top of each other. and generaly it does, just not 100% of the time.

Vincepro wrote:I hope this guy works on the 4000 next...

Question: What do you guys that are excited about Grid Edit use it for? I have Grid Edit on the 4000 but dont get why you would ever want to input your drum hits on that grid rather than just playing them on the main screen. It seems counterintuitive to me so I'm curious.

Im curious as to why it seems counterintuitive to you. Explain the intuition you have that this long running (longer running that step edit) and popular method or programing/editing runs counter to and maybe we can help you out?

Personaly im amazed if you cant see how it could be useful.

i'm finally able to put all of my drum samples onto one pad without having to only view one at a time. now, in grid edit, i am able to see them all do their thing

but i am also reconfiguring the way i make my drum pgms
since i use multiple kicks/snares/hats, i'm gonna do from the bottom up - 4 kicks, 4 snares, 4 hats, 4 cyms/rides/misc

that way i can see em all ordered up.

Haven't read the whole topic and I know we should not write our wantlists overhere, but I was just wondering if the 1000 or 2500 could also do 960ppq
instead of 96 with a software update. This would be a verry nice enhancement.

Sander wrote:Haven't read the whole topic and I know we should not write our wantlists overhere, but I was just wondering if the 1000 or 2500 could also do 960ppq
instead of 96 with a software update. This would be a verry nice enhancement.

that would cause these models to blow their pads clean off. only the big daddy 4000 can handle that sort of weight, and thats thanks to the little japanese woman inside

or at least cut the 96 in half
that'd be enough for me
man that'd be sweet
even though i get by with 192 as it is. i'd rather have 284.

Antonym wrote:or at least cut the 96 in half
that'd be enough for me
man that'd be sweet
even though i get by with 192 as it is. i'd rather have 284.

u mean 384

medway wrote:it doesnt need to be sample accurate timing to play two layered samples sample accurate. even the S1000 has a stereo coherence settign that locks the playback of two samples to be perfect.

i was talking about the playback of the samples (ie the sample-playing engine) rather than the midi sequencer timing, as these are two different things. i believe the 'timing' problems go away when external gear is sequenced? if so this suggests that it is the latency of the sample-playback engine that is at fault here.

medway wrote:since both samples are set to the same pad they should trigger exactly on top of each other. and generaly it does, just not 100% of the time.

yeah you're right they should, but due to inefficiencies in the cpu or programming, they don't. let's hope the guy doing 3.0 can sort something out, although imho he is adding more functionality to a <possibly> overstretched cpu/dsp so it's unlikely to happen.

peace

Im curious as to why it seems counterintuitive to you. Explain the intuition you have that this long running (longer running that step edit) and popular method or programing/editing runs counter to and maybe we can help you out? [/code]

Well if I'm programming a drum track, I'll just listen to the metronome click and play it out like a drummer while the metronome runs. I dont understand why anyone would rather input the notes in the grids. I can see how it would be useful for editing what you have already recorded...say, I want to be able to "see" where my badly played kick is and it is faster to find the dot on the grid than listen to it...but other than that, please tell me..Do a lot of you guys input the drum hits dot by dot on the grid as opposed to just letting the metronome run and bang it out? Why? Thanks!