Features We Don't Need.

sure sounds good to me
i will always be with the newest os

+ 1 for the idea of 2 JJ OS

anybody using p.mode?

i still think a 'modular' install screen would be better, tick the components of the OS you want, and untick those you don't. have an 'OS Memory available' meter, so you know how much you can cram into it. as you uncheck one feature, more memory becomes available, and allows you to add another feature.

yeah one JJ os for the skeptical guys that think the os has reached to its creativity limit and the other for whatever new you want.

in my opinion, removing and adding new feature would be just fine, if people would spend a bit more time beta testing and reporting small bugs, rather than rushing to ask for more.

to me looks like it is such a minority of people who actually bother to get bugs fixed

i bet JJ receive 50 feature request for every bug report

Mr modnaR wrote:i still think a 'modular' install screen would be better,

Sounds like there could be file compatibily issues there... as in if I try to load a project that I made with a certain feature used that is now currently disabled.... if that makes any sense...

aah yes, i didn't think of that. it was a bit of a stab in the dark really, i mean can you imagine the bug reports? 'i've got the input thru feature disabled, the 64 audio tracks feature enabled, video playback mode disabled...' etc etc. lol

Yeah, could get real crazy real quick...

i don't like the idea of kicking pp out. i like this feature and use it not often but on a regular basis. the only code that could be killed for good (for me) would be screenshots and splash screen.
i don't see why anyone except stan would use this, and i'm sure stan can do his manual with screenshots from an older os-version.
and spash-screen could go as well, cause i use it and it's fun, but it's completly sensless, as nobody ever looks at my mpc booting up...
i don't know how much code these two feature use (i hope a lot!) but i think we should suggest jj to erase them.

In an earlier post someone suggested having two operating systems, but maybe there could be room for several. That way, every subscriber could pick the features that were most important to he or she, and download the closest version.

too much work i guess

i second that modular OS thingy, would be dope ...

Hi nym.
All these time that I have for ten months was spent in order to write the code of MPC.
I was tired.
There is no addition of a new function any more.
However, I receive a bug report as usual every day.
And the bug report which cannot be understood has also collected.
It rests making bug correction for a while.

we are in for a couple months of minor adjustments and many bug fixes. i'd say "stability" is the next goal here but we're already stable. "fine tuning" is what's going on now.

The next project for MPC1000 and MPC2500.
I am planning the specification of AKAI, and EXTRA OS which is incompatible in part.
If compatibility is not considered, what it is more easy to use is made.

There is no plan about any models other than MPC1000 and MPC2500.

i don't entirely understand this, but the hopeful part of me reads it as "the gig is not up"

i hereby renounce feature requests and removal requests (excluding old program mode) in favor of bug reporting and using what we've got.

long live JJ.

i guess it means in JJ language that the extra os will not be compatible with 2.10 and maybe 4.XX. what do you think about that?

completely fine by me. i'm perfectly happy to finish songs i've started on X os and then move on to bigger and better things.

but i leave everything henceforth to the discretion of JJ. i will offer my insight but i'm only a user betatester and fan

jj is THE programmer.
i asked also if he was planning on coding for any other machine otehr than the mpcs, but i think he misunderstood and thought i meant for any other mpcs.

however, if this dude ever codes again for another musical instrument, i will buy it. even if it's an akai instrument - i will buy it, albeit used