Yeah, so can't we just ask and know exactly what's going on? JJOS is a hacky third-party niche operation, there's no reason for secrecy. Is there anyone in deep communication with them, who can understand both English and Japanese? There shouldn't be need to speculate based on incomplete info when the full story should be a phonecall or email away.
The big LCD thread is... big, so I haven't tried to read it all before, but there are some tidbits in there I'll hunt out to try to better understand what's happening.
mpcstuff.com wrote:Some people had mentioned a possible "JJ OS3", I am not at liberty to give any info at this time in regards to a possible "JJ OS3". I do assure you all though, if and when JJ OS3 is released it will have support for the MPCstuff XLCDs 
mpcstuff.com wrote:You will not be forced to use this larger screen with JJ updates. No worries on that. I do think that it would be beneficial, to get the most of your machine BUT you will have a choice 
mpcstuff.com wrote:Their will be separate JJ OS's for normal 1000 and 2500 screen and the XL Large LCD Screens. So the JJ Updates will not require the new XL screen. So basically if you have the XL screen you will have a different OS available to you but if you chose to use the small one it will be fine. JJ will support both screen sizes.
mpcstuff.com wrote:The new screen brings in a whole different JJ OS set. So its kind of like having two different units in a way. Before the OSes were for MPC1000 and 2500. Now you will have two more sets of 0Ss for MPC1000XLCD and MPC2500LXCD. So JJ will now have 4 OS sets.
For small screens:
-OS3 is still in the works, and when finished will be for when upgrading from OS2
For large screens: (separate versions for 1000 and 2500)
-OS128 will be the FREE one that comes with the screen when ordered ( I will demo this one in a video)
-OS128XL will be the first edition of the paid JJ OS for the XLCD. (as for functions I will have to talk to JJ more about it as I am not 100% sure yet what all is going to be incorporated in the first go around)
mpcstuff.com wrote:I am quite sure (although havent spoke to JJ yet in depth about it, so no guarantees) that the PAID JJ OS128XL will have most if not all the features of the new OS3.
mpcstuff.com wrote:For those that are current paid JJ OS users, not to worry the OS128XL will evolve. If you choose to wait for it to evolve before purchasing the LCD, that would be totally understandable.
As for some of the missing features from OS2XL: Please realize these features are missing from this ORIGINAL BETA version of the OS. We all know JJ always updates the OS and that is the fun of it (kind of). The OS WILL evolve. There will be a slight curve where you may see some things missing since this OS has been built from the ground up. Just hoping you guys will be a bit more patient before passing judgement when it comes to the PAID OS.
There was talk about how JJ started from scratch, ditching the original Akai foundation, and how this new OS128XL was clean and a new start. It looks like all that came from this single remark, "this OS has been built from the ground up". I don't see any other indication of that being true. More likely, he took the XL code, started stripping away functions to make up for increased CPU load of the larger screen, then began branching it out again, modifying the GUI to utilize the higher resolution.
That's supported by a quote from JJ:
JJ wrote:The load of CPU is large, or since a problem arises, OS128XL does not have the following function.
Simul Sequence
PATCHED PHRASE
Q-link is only REAL TIME.
There are not SAMPLE START of Q-link, SAMPLE END, and CHOP.
OVER RAP mode of PROGRAM (INST)
ADSR
Pad Aftertouch
Pitch Bend Sensitivity
Bars loop
There is no function to control the value of the parameter of an effect by a MIDI controller.
The mixer of a pad is uncontrollable by a MIDI controller.
There is no function to assign the mode to the NUMERIC button.
If you start from XL, it's already pushing the limits of the CPU. So you remove some function to minimize the load, but then some other function depends on that, so you have to move or modify that, and it cascades down until you've had to prune out big chunks of code.
Then since there's never been any other screen, there's been no need to design it in a way where the graphical interface is setup to handle multiple presentations. It could've been a lucky situation where it happened to be setup in a way where adding that would work. But more likely it was baked in so after pruning functions he started modifying the presentation in a way that doesn't work automatically across both screens. Then in order to share code, it requires more hands-on merging and modification, rather than simply using the same exact firmware for both, but with a toggle depending on screen resolution.
But I don't know how this hardware is setup, if the CPU handles all the drawing of the screen, and if so, why merely doubling the amount would be a significant hit.
Nym wrote:this is somewhat of a miscommunication. CPU strain is apparently not a big issue here - i have acquired a translator to assist with future difficult communications.
JJ wrote:OS128XL is not the higher rank version of OS2XL.
OS128XL is completed as an original OS for large LCD.
I think that OS128XL is superior to any past OS.
It will upgrade in the future and will become better.
That last part about being superior, and upgraded in the future, adds credence to the idea that the big LCD is the new flagship, and it could become the primary focus and interest of JJ development.
mp3 wrote:Didn't realize though that it's actually not as wide as the original screen so when running os2xl the fonts etc are a little smaller.
Okay, after going through the entire thread, there's still no clear information about what exactly the current and future situation is for JJOS.
I wonder why mpcstuff.com didn't seem to talk about this before it was done. There's no competition, so there's no need to protect ideas to get out the gate before they can catch up. I would've expected a huge thread where they propose to the community, sharing 3D models, going over finer points with people who would be interested in buying, etc. This just came out of nowhere.
I hope it works out for them. I also hope JJOS development is smart enough to manage this nicely, so everyone benefits. In its current form though, there's reason to prefer OSXL, not just because OS128XL is missing features. Watching videos, the interface looks more difficult to parse visually. There's more big boxes in some screens, with text positioned more dispersed. In OSXL it's condensed, and setup in a way that's easier to scan visually.
Like the pad sensitivity screen:

That's the kind of design style being used in some screens, with big boxy tiles, each having their own little set of details. To parse that, you can't just quickly scan a condensed row or column, you have to kind of look at each one individually.
In comparison here's OSXL:

It's all in a row, with a single details pane on the side. Much better in a way, because you can simply look at the details pane at the "Velocity", and as you hit each pad, your eyes don't have to move to see the relevant info. But with OS128XL, the info is all scattered, so as you hit a new pad, you have to visually scan to find the location of the data to read.
If you wanted to quickly compare 2 pads far away from each other, with OSXL you can do it quickly by just hitting each pad after the other repeatedly, while staring at a single point. With OS128XL you have to keep moving your eyes to find the spot you need to look, which may not sound like much, but it is, and puts a cramp in workflow.
Also, if you want to look at the graphical bar to show the pad velocity or pressure, a grid breaks it up spatially, so off the top of your head, if I say to look where it'll show pad 5 do you know where to look? With OSXL it's in a straight grid, from left to right, so it's easy to quickly know that to look for one of the lower pads, you look more to the left.
However, in this case what's on the screen in grid form spatially relates to the spatial input of the pads that are also in grid form. So, for pad sensitivity mode, it could be that this grid layout is better. In OSXL, if you wanted to go through each pad from 1 to 16, your hand has to go in 4s, changing position with each new row, while your eyes are trying to relate that with a straight line. It doesn't match, so there's a mental conflict. Whereas in OS128XL, you can sync your eyes to your hands spatially, so if you move your hand over to the left one, then up one, you match your eye movement, which keeps it in harmony and there's no conflict. So actually it might be easier to know where to look for pad 4, since you have to find it on the pad grid anyways, and once you do you automatically know where it'll be on the screen.
This is the pad sensitivity page, which you don't use often, but this same kind of thinking is what's going into other pages where there's less of a relation between pad grid and screen grid.
Like the new loop edit mode:

Which has that same kind of big and dispersed feel in comparison to the condensed:

But, you do gain more visual information. In condensed form, a hit is a hit, and you can't sense visually how hard it is. In OS128XL, you can read it and hear it in your head. Just looking at this screenshot, you can have a more accurate sense of the data in the recording. Whereas if you tried to guess how the OSXL one sounds, it's all full level. In one sense, having more information is better. But, in another, it's better to minimize the visual info, and rely on ears. It can be frustrating, because we're essentially crippled, partially blinding ourselves to force the ears to take dominant role, when usually it's our eyes leading the way. But that often works better for music production. Otherwise, you end up in a very visual DAW, where instead of hearing the sounds you're paying more attention to what you see, and it becomes like Photoshop for music. That's great for technical engineering stuff and complex composition, but it's not so great for raw expression and artistic performance.
A major reason why I choose to pursue something like an MPC as a tool for audio production over the more flexible PC software is simply because the smaller fixated screen forces the developer to design in a condensed way (assuming they don't just lazily add a thousand sub-menus to do anything). Whereas with a windowed PC GUI, you've got all these floating flexible layouts everywhere, so you have to engage spatially, and go navigating to find things in space. It changes the mode of your mind, where you can't as easily lock into tight auditory-based awareness. It's like if when you're driving a car, in order to shift you can't just reach down and move a stick, but instead have to search the dashboard for a floating control.
It's like the difference in your Explorer or Finder of the icon view, and detailed. The big grid of icons with their own floating labels force you to search around in a more broader way. In detailed view, there's a fixed list of items, ordered in a condensed predictable form, so you can quickly scan.
By minimizing the visual load, you maximize the power of your auditory system. This is why closing your eyes and beating a drum is always going to be more freeing and expressive than composition using any electronic tool with a screen. It's a constant struggle to find a balance between what comes natural and allows primal forces to flow, and what is techie in a restrictive way, forcing you to think and do math rather than just open your mouth and shout.
... and if there's still any confusion about whether or not OS128XL is started from scratch, looking at the manual it's very clear that this is XL with modifications.