Next Os

ryssen wrote:

MidnightFlyer wrote:this is a big problem. the only way it can work is if I record each of the notes from 16 levels 'tune' into Pro Tools, then bounce them into a wav file and put it back onto the cf card.

Isn´t it easier and more flexible to map the sample on all pads and then tune the pads seperately the way you want them?

then what's the point of using the 16 levels 'tune' if I have to tune each pad separately? that's too much work.

The thing is, when you download most pads or notes, they usually just give you unisons, or fifths, etc.

That does no good, the notes have to be split chromatically to play tunes. IF we want a good bug fix, make the 16 levels tune, do (perform) exactly as it does, (allows you to overlap notes) when not in 16 levels.

gaston wrote:

MidnightFlyer wrote:One thing I find missing that would help me is 16 levels "Tune".
When you hit a pad, then hit another without totally releasing the first pad, it will cut off the hit. Does me no good to divide up a note chromatically if I can't use it exactly the same way I use it when not using 16 levels, tune.

Anyone following my logic, here?

same here.........
so i record those trax in parts.....like -first take: 1st.,3rd.,5th,7th.notes.......-2nd. take: 2nd.,4th.,6th.8th. note

ps: sorry for my explanations, might be some kind of primitive, but doing my best.....(a spanish speaker).

Yes, this is a possible fix, but sheesh, it should be easier. Your English is fine, BTW.

MidnightFlyer wrote:

pad-ophiliac wrote:

MidnightFlyer wrote:One thing I find missing that would help me is 16 levels "Tune".
When you hit a pad, then hit another without totally releasing the first pad, it will cut off the hit. Does me no good to divide up a note chromatically if I can't use it exactly the same way I use it when not using 16 levels, tune.

Anyone following my logic, here?

if i understand you right and you don't want the pads to cut each other off while using 16 level, thats simple man. go mode>program>params>turn from mono to poly in upper right hand corner.

Doesn't work. Do this. Get a note on one of your pads. Now set the 16 levels to 'tune' ..... Now try playing the pads. MInd you, I want it to be NOTE ON, and not ONE SHOT.

Okay, ... whether it's on Mono or Poly, you can't play two notes that overlap, even for a micro-second. It cuts off the note.

this is a big problem. the only way it can work is if I record each of the notes from 16 levels 'tune' into Pro Tools, then bounce them into a wav file and put it back onto the cf card.

Then I can use all the notes, just like I do when 'not' in 16 levels.

Try it.... see what I mean...

well you didn't specify that you wanted it set to "note on". what i mentioned above does work if it is set to "one shot".

pad-ophiliac wrote:

MidnightFlyer wrote:

pad-ophiliac wrote:

MidnightFlyer wrote:One thing I find missing that would help me is 16 levels "Tune".
When you hit a pad, then hit another without totally releasing the first pad, it will cut off the hit. Does me no good to divide up a note chromatically if I can't use it exactly the same way I use it when not using 16 levels, tune.

Anyone following my logic, here?

if i understand you right and you don't want the pads to cut each other off while using 16 level, thats simple man. go mode>program>params>turn from mono to poly in upper right hand corner.

Doesn't work. Do this. Get a note on one of your pads. Now set the 16 levels to 'tune' ..... Now try playing the pads. MInd you, I want it to be NOTE ON, and not ONE SHOT.

Okay, ... whether it's on Mono or Poly, you can't play two notes that overlap, even for a micro-second. It cuts off the note.

this is a big problem. the only way it can work is if I record each of the notes from 16 levels 'tune' into Pro Tools, then bounce them into a wav file and put it back onto the cf card.

Then I can use all the notes, just like I do when 'not' in 16 levels.

Try it.... see what I mean...

well you didn't specify that you wanted it set to "note on". what i mentioned above does work if it is set to "one shot".

Yeah, that's what I thought. Don't you agree this should be dealt with?
I mean, everytime I download notes, I have to break them up in 16 levels to use them.

This is the single most important thing for me, but no one else seems to mind a bit. WTF?

nah, can't say that its an issue for me. a few things i would like though: alphabetized files, scroll by holding down arrow insted of turning dial, simult, and switch in and out of usb mode without unpluging. but honestly, after the last os, i am completely satisfied with what we have and don't expect anything else. 2.1 was truely unprecidented.

then what's the point of using the 16 levels 'tune' if I have to tune each pad separately? that's too much work.

try to make a habit of not being lazy on the mpc...

i would of never bought one if the 2.0 update never came out so for that im happy and i dont really have any bug issuses in mine. All the things i want are impossible like a flip screen or a firewire recording interface instead of 4 outs ect ..............

ryssen wrote:

MidnightFlyer wrote:this is a big problem. the only way it can work is if I record each of the notes from 16 levels 'tune' into Pro Tools, then bounce them into a wav file and put it back onto the cf card.

Isn´t it easier and more flexible to map the sample on all pads and then tune the pads seperately the way you want them?

Would you mind giving a brief explanation how this is done?

a firewire recording interface instead of 4 outs ect ..............

man wouldn't that be dope? ill keep dreaming.

or look into a way to mod an onyx expansion firewrire card into my mpc

I think the roland 606 has this feature in it so i would think it could be done if someone on here were a mad scientiest and killed a 606 for the good of a mpc1000.

MidnightFlyer wrote:

ryssen wrote:Isn´t it easier and more flexible to map the sample on all pads and then tune the pads seperately the way you want them?

Would you mind giving a brief explanation how this is done?

Well, first assign the same sample on all pads in a bank.

Then flip through the pads, tuning each one to correspond to the one before. Just a matter of finding the interval of tuning the 16 level tuning apply between pads.

I think it´s a blank, ready tuned chromatic program to download from stereoriod.com...

Found it and note interval info here:
http://stereoroid.com/music/mpc1000/faq/, almost at the bottom of the page.

i don't know, but this new os overloads easier than the last (new os is good so dont say stop whining and get the old one) but is's fcked up that the beats i did with old os, are too heavy for the new os. one instrument too many, and the main sample is gone. another thing, the q-link trimming is great idea, but its too raw you know, it could be more pasific. im cool with this os, but of course new one would be grrreat.

sixsevenbeatz wrote:i don't know, but this new os overloads easier than the last (new os is good so dont say stop whining and get the old one) but is's fcked up that the beats i did with old os, are too heavy for the new os. one instrument too many, and the main sample is gone.

http://www.mpc-forums.com/viewtopic.php?t=47151 this will help you get all the levels balanced again.

bug fixes first and foremost although i havent really had my shit crash or lose anything(i dont got no harddrive, still got 16mb's of memory) haha yeah im working on the so called "limited memory" but 2 minutes of mono sampling is a hecka long time for me. i dont plan on making influx part 2 ha!

chop shop would be really good to have, just choppin drum breaks super quick...

and a more accurate readout of the timestrech/pitchshift tempos

naugie wrote:

Balls wrote:

naugie wrote:u know what i want? i want a good explanation behind the detect tempo funtion. i notice through mathimatical steps (yes i took manual steps to detect tempo) that the detect tempo isnt always accurate. if its a bug that i caught, ill like to give it a name. ill call it naugtemps, naug for naugie. temps for tempo. and if its not a bug then im a retard and would like to know why it generates wrong numbers on the manual

maybe im asking for an faq cause that be sick, maybe if the community put one together. an updated one

The reason why it fails on detecting the right BPM is that probably that you're trying to find it on a non-percussive sample (ie. strings or something). Of course it couldn't work in anyway when you're not telling it how many bars the sample is... The detect tempo function only works with percussion loops in 1 , 2 , 4 , 8 , 16 , 32 (and so on) bars. That's common sense in my opinion. It's not a bug. And i don't really see the big issue. I don't find it hard trying and listening, until I get it right. It trains your ear plus giving you a better sense of how much difference there is between 1 and a 100 BPM.

ohh snaps thanks mang i never thought of it like that but it makes compelte sense though. ya im still learning sampling theorems. im just groping the surface of sampling. ima make a post about this detect tempo on a later date i have question floating in my head i just dont know how to ask it yet. thanks though

What ever happen to editing by ear.....lol All this beat detection stuff is silly but I am guilty of using it.