Forum to discuss all matters relating to the MPC1000 and MPC2500 operating systems created by 'JJ' (all versions).
By objektivone Mon Jan 26, 2009 4:00 pm
I have OS1 right now on my 1000. I pretty much know the answer to this question but just need it reaffirmed, because I have had problems in the past with things like this....

None of my beats or sequences will get messed up if I upgrade right? It will read all the files, pad attributes, etc all the same right?

Thanks. Like I said, I just affirmation on this not a debate.
User avatar
By sonseelye Mon Jan 26, 2009 4:21 pm
what r u upgrading to??
not sure if you are upgrading os or mpc
if just mpc,then u should be fine,,
for os,im not to sure..
User avatar
By arebee Mon Jan 26, 2009 4:54 pm
no, it wont read them completely as u would like,

there's different attributes attached to various elements in the new OS,
say in earlier OS created Programs for example, i found t a cut off slider note variation recording will actually end up being assigned to pitch note variation, and no way to resolve it, and other parts of the program will be given mismatching settings - like OS1, OS2, XL have different filter setups, layer setups, adsr & velocity, aftertouch, responses etc......etc..........etc.........mainly because there aren't the same features across the board with these three OS's.

you're best off moving a copy of all your Programs, Sequences, Projects etc, into a folder named with OS1.

then open the projects in the new OS , bit by bit, or at least edit the settings bit by bit, then resave them in a new OSXL folder.

thats the only way to push old projects through to the new OS and retain the originals untouched, because there's every chance that they're not backward compatible either!
By objektivone Mon Jan 26, 2009 6:13 pm
Thanks.... I won't be switching for awhile then. I don't have time to mess with that BS. That is probably the biggest BS I have heard about OSs ever. Don't get me wrong I love JJ and his OS, but man.... that is whack. I also understand that some of the changes made are unavoidable, but no backward compatibility?

I might not switch for a long time now.... I thought maybe a few tweaks here and there but that laundry list you just gave me.... :roll:
By dtaa pla muk Mon Jan 26, 2009 6:21 pm
full backwards compatibility is a bigger feature than any other feature ever given to the mpc
takes more work, produces more bugs, and is the least easily done.

unfortunately non-programming, non-beta testing end users simply don't know about how implausible backwards compatibility is.

progress > history. i've found that recreating even complex old tracks in os2xl takes very little time.
By objektivone Mon Jan 26, 2009 6:53 pm
Nym wrote:full backwards compatibility is a bigger feature than any other feature ever given to the mpc
takes more work, produces more bugs, and is the least easily done.

unfortunately non-programming, non-beta testing end users simply don't know about how implausible backwards compatibility is.

progress > history. i've found that recreating even complex old tracks in os2xl takes very little time.


LOL. I can understand how it can't be backward compatible. I completely understand it. I just wish it wasn't so. I could easily recreate the tracks in OS2XL... I just don't want to. They are already created.

I will just bounce them down to audio files and back them up before I switch. But I can't do that for awhile because I have that many MPC backups I have to bounce down
By Sovereign Mon Jan 26, 2009 7:55 pm
You don't really have to recreate them as much as you have to tweak certain parameters.
Once you get a feel for what's different it's a lot easier to repair work from previous OS' levels.
Then of course there is the beauty of simply loading the OS they were done on when you need to use them.
User avatar
By arebee Mon Jan 26, 2009 10:21 pm
thats the way i'd put it, just load up a copy, tweak it till it sounds the closest. there are examples ive found that really wont ever be replicated. so u just have to figure out whats best for u at that time.

but old projects in limbo can be well rejuvinated in later OS's to better results, and garnished with new possibilities.

but dont bother reviving something nearly finished, cap it off in the OS it was designed in, and seal it up with a bounce or a track out or whatever u do. then start something fresh in the new OS, and u will get the wildest results (my experience there).
By nanoloop Mon Jan 26, 2009 10:48 pm
arebee wrote: but old projects in limbo can be well rejuvinated in later OS's to better results, and garnished with new possibilities.


wise words there bro, i went thru this ordeal with the transition from os 1 > 2
By Sovereign Tue Jan 27, 2009 12:17 am
Once I realized that XL brings more to the game than it takes away I pretty much stopped complaining.
It's still not the 4k but it's really starting to turn into something that's pretty functional.

I only have one thing right i would like to see and that's the ability to come out of record mode automatically after first pass.
It's one thing i really like about the MV.

With MPC's I always have to deal with stopping the sequencer after the first pass so it will playback and not record.
By dtaa pla muk Tue Jan 27, 2009 1:35 am
sovereign, curious - why do you have to stop the sequencer? could you just turn off OVERDUB and let it keep on playing? or do you find that recorded notes don't play til you hit stop (os2 behavior)?

i never thought i'd say this (simply cuz it's all but an empty function) but maybe a footswitch is in order for that.

also, do you still have a 4000?
By Sovereign Tue Jan 27, 2009 3:19 am
Nym wrote:sovereign, curious - why do you have to stop the sequencer? could you just turn off OVERDUB and let it keep on playing? or do you find that recorded notes don't play til you hit stop (os2 behavior)?

i never thought i'd say this (simply cuz it's all but an empty function) but maybe a footswitch is in order for that.

also, do you still have a 4000?


Because of my physical setup when I am actually sitting at the 88 playing I'm not really close to certain other pieces.
I may start out with a certain number of intended measures but feel something else while playing.
This allows me to try out something additive without affecting the part I originally wanted to keep.
If the sequencer goes through and stops recording on the second pass I can experiment without having to move.
As it is now I would have to stop the MPC from recording as I try variations.
It would be pretty simple to make the sequencer have 3 options;
1-Record No Overdub=comes out of record after first pass
2-Record Overdub=continues to record on multiple passes
3-Overdub=adds to existing on multiple passes

I currently have the 1k, MV, 4k and 5k, V2 will help me decide the fate of the 5k.
I recently sold my 500, because of that false polyphony Akai gave it.

The small display on the 1k does make a difference, but my whole thing about the 1k is JJ is such an unknown factor you have to stay open to that option.
Right after I sold the 2500 JJ made some OS changes that were attractive at the time so I tend to not try and anticipate what he may throw out the hat at you.

I'm just waitnig to see if he takes the SIMULT back to the old style or twaeks the new in a way that makes us forget the old.
By nanoloop Tue Jan 27, 2009 4:21 am
sounds like u need some foot pedal action, as nym said. i used to have great fun jamming on the keys and using the foot pedal to start stop the sampling on an EPS16