no the Push 2 has a high res, RGB display which you can access via USB (proprietary protocol, detailed here - it makes it a fantastic device for custom applications 
however, part of oKontrol is also going to allow for midi learn, so then you can assign a CC to each organelle parameter too. I want do this as a ālive mappingā rather than hard coding CC.
whats going on here , is the Organelle is using my oKontrol external , which then communicates with my āMECā application via OSC , then in turn renders on the Push 2. all this is done running on the Organelle, but it could be distributed across macOS, rPI, Organelle (basically at this stage its a ādistributed parameter systemā)
(oKontrol is all C++ , so its the same code used in the external and within MEC, just different callbacks etc)
of course, as its sending out OSC messages, potentially I can do this with anything that can process OSC.
anyway⦠for non-techies, the idea is simple, write PD patches once (I can add other language support), and then run on different platforms, using different controllers to control the patch. also if you read the post on C&G youāll see that its really easy to add these parameters to patches.
my personal goal is pretty simple, I want to write generic patches, and then run them on Organelle, rPI+PiSound or Bela depending on its needs⦠(oh and test/develop on mac/linux) ā¦
(also I was frustrated at the effort i was spending on the display side, when writing PD patches⦠so I wanted it simple to do, and to test)