Forum to discuss all matters relating to the MPC1000 and MPC2500 operating systems created by 'JJ' (all versions).
By jknievel Mon Mar 12, 2012 3:45 pm
Apologies for asking something that may have been answered elsewhere, I've looked and can't find.

Currently running JJ OS XL 3.16 on my 2500 and would like to transfer my old 2000 files (.SND, ALL_PROG.aps, ALL_SEQ_.all) to the 2500. I've already transferred the zip drives to my Mac (running OS X 10.6.xx). But when I transfer each folder to the 2500 it recognizes next to nothing.

So...

What are the steps needed to make this work?

Thanks in advance and again, apologies if this has been addressed countless times. Seems like it would be a common problem but I'm having a hard time finding a solution.

JK
User avatar
By Bugfix Mon Mar 12, 2012 9:15 pm
Well if you got someone with 2000 you could save sequences as midi.. or maybe separate sequences. An .all file should work, I don't know about others. As for the .snd files you can batch them to 16bit wav's
User avatar
By MPC-Tutor Mon Mar 12, 2012 11:58 pm
Wont work correctly, as JJ OS2/XL doesn't like the layout of legacy Akai programs which run in an odd MIDI Note order (37, 36, 42, 82, etc). So basically when you load them (and yes, they will all load), JJ OS messes around with them to create what I call a 'chromatic 36' program. However, this messes up the MIDI note assignments for your original sounds and also screws up the sequences.

This is the case with any pre-OS2 program, Akai or JJ created.

The way around it, or so I thought, was to ensure your legacy programs were all in 'chromatic 36' format, and your sequences were created with these chromatic programs. However, I've discovered that only OS1 and OS2XL v2.xx play nicely with this. OS2XL v3.xx messes them up again, as does OS2 (v1.36) - only the sequences though, the programs are fine, but the sequences have all sorts of substitutions, e.g. an event originally set as pad A3 (38) becomes A6 (41).

TBH, my head is spinning as I'm trying to sift through all this incompatibility nonsense as it affects certain products in my sample catalogue. And of course, it doesn't stop there, as newer JJ OS programs are not backward compatible with other JJ OS (muted or cliped sounds in programs for example), but also I'm finding OS2XL V3.xx doesn't even like OS1 programs in chromatic36' format, which is definitely not correct (OS2xl 2.xx loads these types of OS1 programs fine).

Absolute mess. Can we forget about all the cool new features and have a bit of order with the file compatibilities please? :evil:
By dtaa pla muk Tue Mar 13, 2012 3:57 pm
Absolute mess. Can we forget about all the cool new features and have a bit of order with the file compatibilities please?


haha. backwards compatibility is one of the most (unexpectedly) difficult parts of development.

imo jj has been smart to neglect it in favor of forward development, and i say that with hundreds and hundreds of projects from os1 and os2 kicking around my mpc hard drive that i may some day want to finish. murai mentioned that os3 will similarly be a tradeoff, and my inference is that os2xl project files will be MOSTLY compatible. the switchover will likely cost me a little time but like with os2xl it will be a positive more for more productivity.

aside from realtime qlink/4th layer stuff, i find that simply recreating an old project in os2xl is a lot easier than trying to port it over.