future jj OS's

arebee wrote:where's the midi edit/ qlink / cc control pages?

the 1k's got it but not the 2500.

sheeeeesh.

It makes no sense to compare.
The 1k is in it's what version of paid O.S.?
The 2500 is in it's what version of paid O.S.?
The physical differences prevent him from simply porting the 1k to the 2500.
That's what he was doing with the earlier free versions and it always broke a function of the 2500.
The 2500 gives him more to work with so it's clear it will eventually do things the 1k can't but there's no need to rush since the 1k market is still much more viable.
The reason being if you take a factory 2500 it's still ok, while a 1k without JJ should be illegal or the price of the MPC500.
Just give it time he just really started to attack the 2500.

The 2500 gives him more to work with so it's clear it will eventually do things the 1k can't but there's no need to rush since the 1k market is still much more viable.

hopefully there will never be a rush to put things into the 2500 that the 1000 will not be equipped with, unless it has something to do with using 4 qlinks simultaneously

but since the specs internal hardware wise of the 1k and 2500 are the same the os's should always be as functionally identical as possible, ie no function to one machine that isn't soon to be implemented into the other (300,000 notes for the 1000, qlink control of midi ccs for the 2500)

there's no reason to cripple one machine, especially the 1000, since 1000 users have been jj's biggest business

Antonym wrote:
but since the specs internal hardware wise of the 1k and 2500 are the same

Similar not the same

Antonym wrote: there's no reason to cripple one machine, especially the 1000, since 1000 users have been jj's biggest business

if your car does 0-60 in 5.9 sec you will get a speeding ticket.
Why because you have the available resources and want to use them.
Same is true of the 2500.
Remember JJ's 1k market came from the 1k being so worthless for lack of better term.
Look at how much Akai added from the original 1K and then how much JJ added to that.
The 2500 just started with so much more going for it but still has a lot more that can be added.
The biggest thing will come from JJ having to find a way to get more memory for features on the 1k.
So if he can't steal it from the Flash ROM then he will have to start dropping some existing features to make room.
Currently JJ is crippling the 2500 O.S. by treating it like it's an expanded 1k.
Still I am greatful for his O.S. and thankful that v5 cleaned up and re-arranged some of the screens.

The biggest thing will come from JJ having to find a way to get more memory for features on the 1k.

do you have any reason to believe that the flash rom of the 2500 is bigger than that of the 1000? i don't think it is, or at least i never read that it is.

as arebee posted in another thread, the cd functions of the 2500 actually limit the flash rom of the 2500 by taking up valuable space.

you say similar, but not the same. could you back this up with a link or something that i may have missed?

if you have an honest conversation with the right people from Akai they will share info with you.
You would be surprised at how much of what is discussed about the MPC's is just speculation.

that didn't answer my questions.

Antonym wrote:
hopefully there will never be a rush to put things into the 2500...

We seem to agree as of late. JJ should continue using the 1000 to beta test the new OS for the 2500 (which I think Akai was doing by accident). I/we really do appreciate your hard work and efforts in this regard. I wish we could do something about your pads though. Maybe the MPC 2500 users should donate $1 to $5 each to help you in your quest to rebuild the pads of your 1000. Maybe Tutor can provide a Pay Pal link at the top of every page for the Nym-fund

Antonym wrote:that didn't answer my questions.

Actually it did, go to the source.
Have a phone conversation with Akai.

Yesterday I recieved my Alesis MultiMIx 16 Firewire which was the final peice I was waiting for in my setup so I sorted everything out and reinstalled windows, cubase, etc on my pc and taped all my wires in place for a nice clean start.

While I was doing this and getting everything nice and ready to use I thought I install JJ OS 5.0.3 and bingo, this time it's solid as a rock and is working perfectly so I can now happily retract my comments about it being unstable. Only thing I still would like changing the viewing tracks after track 6 in 6 Pad grid edit, I would like the tracks to scroll rather than just the bottom track changing.

Anyway, that was great and I was really happy with everything.....then the MultiMix died after just 3 hrs or use

jahrome wrote:I wish we could do something about your pads though. Maybe the MPC 2500 users should donate $1 to $5 each to help you in your quest to rebuild the pads of your 1000. Maybe Tutor can provide a Pay Pal link at the top of every page for the Nym-fund

hahah thanks for the kind thoughts
that would be nice, but unnecessary, broke ass broke as i feel right now, i have enough money to bulk order materials right now

materials will cost me $500 for a handful of units that i'll make, sell, and buy more materials with. all said and done i'll probably be spending $5000+ on materials unless i find better sources/they cut me a break on bulk sales

sad thing is i'm really no businessman or scientist i just exhaustively tried sht til i found stuff that works

i need to start collecting my neighborhood's kids and putting them in my basement under florescent lights and with nothign to eat but oatmeal and ramen, with soldering irons and materials...

just kidding...it'll only me in the sweatshop
and seeing as how i'll be making 50+ of these things it really will be borderline inhumane!

as far as the 2500 goes i mean they don't have to "test" stuff on the 1000, like they don't have to only gvie new features to the 1000 and get bug reports there because as we've seen porting the features over does give bugs. i'll be curious to see how features get introduced now, one machien at a time or both simultaneously. i'd just really liek to see some sort of compatability between files so we could swap prj zips across machines.

but i don't mind having done the bug reporting which hopefully eased the slide of the jj os into the 2500. 2 birds with 1 stone as far as i'm concerned, i think it's awesome to have had a part in it, especially when bug reporting very rarely gets in the way of pushing the envelope with new beats...and also because it gives me an opportunity to make quiet, humble suggestions....like midi ccs from external source controlling qlink!!!

it's very nice to feel as if we have some part in the design of these machines code, which is really getting powerful and reason-esque...reason in a smaller box with a better sequencer and more limited synthesis concept

dunno if you saw this but it's from from jj faq:

1.24 Programs ==> 99 Programs
2,Q-LINK Slider ==> MIDI CC out.
MIDI in CC ==> Q-LINK.
These are under plan.

i was just talking abuot how nice this would be for those with midi controllers...esp those with only 2 qlinks, but even for those with 4 qlinks!!

Antonym wrote:
as far as the 2500 goes i mean they don't have to "test" stuff on the 1000, like they don't have to only gvie new features to the 1000 and get bug reports there because as we've seen porting the features over does give bugs. i'll be curious to see how features get introduced now, one machien at a time or both simultaneously. i'd just really liek to see some sort of compatability between files so we could swap prj zips across machines.

From the activity in these threads...it is logical that way though. More 1000 users jumped at the chance to install the OS and have been more active abut reporting bugs. This appears to have had a positive impact on the OS development of the MPC 2500...there has been less bug fixes. Just looking at the JJ page, you have an entire Burger King menu of operating systems to choose from

As far as compatability...tracks created on the MPC 2500 should playback on the 1000 and vice versa. Are you saying that they don't or you don't know? This can should be easily solved by asking the few here in the forum that claim to have both to test a few tracks...

i had issues with the 2500s ALL files, the 'seq' element of the pack, would crash the 1000 on loading that bit,

but if i loaded the elements ('seq' effects' etc) seperately, it would work.

was a workaround......but its not the way it should be