Forum to discuss all matters relating to the MPC1000 and MPC2500 operating systems created by 'JJ' (all versions).
User avatar

By m00k13 Wed Jan 02, 2008 12:38 am
sound good and are good examples of the INST programs. Thanks dude.
User avatar

By Antonym Wed Jan 02, 2008 12:55 am
you bet.
User avatar

By HoodE Wed Jan 02, 2008 1:27 am
Good lookin on the download. Definitely appreciated.

Beyond that, I have a question and have yet to find it anywhere on here. Don't think there's anyway to find it on here anyway given the INST feature has such a limited amount of letters that the search function turns up too many hits. I wish JJ had a good manual up but I have yet to find anythin that explains how.

What I don't understand, or really have the first clue as to how to set up an INST program. Seems like a great idea if it does what I think it does, but I really don't know enough about how to set it up to try it out. Or maybe I set it up right. Who knows...
User avatar

By konc3pt Wed Jan 02, 2008 2:38 am
thanks for shaing, thought os2 dont come out til march or april ?
User avatar

By Antonym Wed Jan 02, 2008 4:36 am
we're in between alpha and beta stages right now, koncept. it's gettin there.

hoode, what i suggest doing is loading one of my multisampled INST programs, looking at the GPE note assignment "SAMPLE" page, and then create a new INST program.

then, recreate my program...note that in TRIM, each sample has a note assigned to it. ie, if the sample is hammondG2, the note in TRIM has been set to correspond to G2. this is a reference point.

then, depending on how many other samples in the 2 range i have, i set a range over which that hammondG2 has been grouped.

Image

say, E2-#A2. note that both E2 and #A2 are 3 semitones away from G2.
rinse and repeat. it's tricky at first and there are a couple places where you can screw up. to test your program, just play all pad banks from 1-16. you'll hear if it's right and you'll hear if it's wrong.

the more you do it the easier it is. i could do it blind now, having rigged up so many of these damned things.
User avatar

By HoodE Wed Jan 02, 2008 7:11 am
Thanks for the tip. That worked out great. Plays a little quieter, but that can be adjusted later anyways. Thanks again.
User avatar

By goobadrum Wed Jan 02, 2008 8:41 am
love your work nym , thanks for sharing an caring , much appreciated.

these will be the first thing I fire up with os2 , should help level out the learning curve :wink:
User avatar

By Chulukinat Wed Jan 02, 2008 11:09 pm
OMG is this what im thinking? does the MPC1000 finally support multisampled instruments which can be played on the keys?
User avatar

By Antonym Wed Jan 02, 2008 11:35 pm
you bet. but you gotta make them from within the MPC1000. it's a new way of making programs that you have to learn.

my idea is to make a humongous bank of community-shared MPC1000/2500 INST programs that we can either permanently host on my domain or use YOUSENDIT and sendspace to keep dropping these monster zip files of wavs/pgms to share.

make an enormous free multisample bank, so that basically when people buy os2 they instantly have hundreds of multisampled pgms for free...this in turn would encourage a jjos2 purchase.
User avatar

By Chulukinat Wed Jan 02, 2008 11:38 pm
damn thats sum ill shit nym!

i dont know how legal it is and how much mb's it would take... but in fact it should be possible to sample modules like the motif and the fantom right?

ive been waiting for this :lol:

By Rendr Thu Jan 03, 2008 12:12 am
man, i thought it was sick when the os made the 1000 work like a 2500. Now it's gettin closer to a 4000. Many thanks to nym for sharing the knowledge.
User avatar

By Antonym Thu Jan 03, 2008 12:14 am
i'm not too concerned about legality. if it gets to be a problem, i'll remove the offending material. example - mpc-tutor's stuff. sharing that would be a clear example of shting where you eat.

however, patches from synths etc should not be a problem at all, and until it becomes one i say have at it. mb wise, i have uploaded 41 programs. the zip is just under 100 megabytes. that's about 2 mb per program. i got lots of bandwidth, too, and if need be i'll ask for community donations to pay for more.

the community/developmental potential here is just too great to let something as silly as bandwidth limitations get in the way, know what i mean?
User avatar

By Antonym Thu Jan 03, 2008 12:16 am
man, i thought it was sick when the os made the 1000 work like a 2500. Now it's gettin closer to a 4000. Many thanks to nym for sharing the knowledge.


hah you're damn right. in fact we've got a couple functions going on that no mpc has ever seen before to the best of my knowledge.

try making a drum pgm, then putting 2 long samples on layers 1 and 2 of a pad. turn the aftertouch to Xfade up to 100, then push on the pad and alternate your pressure.......that's something i haven't seen anywhere else before jj.

By Seasinz Thu Jan 03, 2008 4:24 am
couple quick questions as i dig deeper into the new features and try and figure out how to adjust my workflow.

noticed that autochromatic is either gone or in another place, did that get replaced for INST programs ?
think this was covered way back but i cant find the thread.

no way to use a chop point as a sample for an INST program ?

thanks in advance.
User avatar

By Sooty_G Thu Jan 03, 2008 7:04 am
Antonym wrote:try making a drum pgm, then putting 2 long samples on layers 1 and 2 of a pad. turn the aftertouch to Xfade up to 100, then push on the pad and alternate your pressure.......that's something i haven't seen anywhere else before jj.


this is a really good feature but what's holding it back a bit is that you can only use it in a DRUM program. I think this feature would really shine in an INSTRUMENT program. i really want to set up the crossfade & then have it easily mapped out across all the pads & use it with the filters, etc.

i realize this could cause some possible confusion or conflicts since the aftertouch could also be controlling filters, lfo, ect. but i think they could work well together simulatneously if wanted. otherwise it would be great to assign a qlink to the crossfade, and be able to crossfade across all 3 layers.

does this make sense? maybe this would be better in the requests thread...