Forum to discuss all matters relating to the MPC1000 and MPC2500 operating systems created by 'JJ' (all versions).
User avatar
By le rat Sun Aug 29, 2010 10:46 pm
Hello,

I'm doing some scratch chorus from time to time on the MPC.
I HIGHLY recommend os2xl for that purpose. On previous JJ OS the audiotrack workflow is too badly thought and you always have to use workarounds.

I don't know about the FREE OS sorry.

I'm in a hurry so I can't sum up the changes between the different between JJ OS right now.
When I'll have one or two hours free next week, I'll reply in details.

PEace
By the.dude Mon Aug 30, 2010 1:53 am
Cheers, thanks for the responses guys.

I won't take up 2 hours of you time to walk me through it. I'm sure you got better things to do with your time :wink:

I'll install os2xl and read through the manual. I'll come back if I get stuck. I'll try the quantize thing. Apart from that is there anything else i should know that isn't in the docs?

http://www7a.biglobe.ne.jp/~mpc1000/os2xl/manual.htm
By the.dude Tue Aug 31, 2010 12:33 am
Installed and tried os2xl and it works great as far as laying down a scratch track to my beat. Sync was waaay better.

before I go ahead and spend the coin on this I checked the comparison chart and I think that os2 can be a good option for me.

I was wondering if there is any useful info that isn't on jj's site about the two os's that I should know about… mainly bugs or stability issues. I'm only really looking to lay down some scratches. Don't need to get too fancy. If I change my mind I can always upgrade too.

Thanks again for all your help guys.
User avatar
By le rat Tue Aug 31, 2010 1:11 am
If you go backward from os2xl to os2 you'll notice for audiotracks that :

- no song mode compatibility
-no effects or q link
-unable to set one sample for a bar i.e. one audiotrack = one track = one sample
-unable to start the recording where you want but only at the beginning of a bar

Here are the main drawbacks. For me song mode uncompatibility is the most terrible.


Otherwise I've just noticed that you can use the "wait for pad or key" function in os2xl by pressing REC +¨STOP.
It seems there is a small bug too, that function ignoring the LOOP configuration on the F1 tab and starting at the beginning of a bar where the cursor is located.