Would it be hard to use an lcd of some sort to have some feedback from the hardware when not connected to the computer ? Like visualizing parameters values, patch name etc .
Just wondering .
Connecting LCD to Axoloti
Parameter editor
@sovietpop its going to be both a software and hardware challenge, so depends upon your experience.
I can't say much on the hardware side,
but can on the software (as I've been digging around with this on the Ableton Push).
First you have to be an experience C/C++ programmer, as your going to need to understand the firmware code, and your going to need to write your own 'driver' to drive the LCD.
The code is kind of in place to push an image to an LCD with the functionality of 'axoloti remote', see the virtual version in the GUI, but you would have to tailor this depending on size of display etc.
but this is a bit limited in some ways e.g. it cannot visualise step sequencers, and has no notion of units.
with the push I've taken a different approach which is to query the parameters directly, and have got the same level of functionality and beyond, with the real advantage i can organise things exactly as I want.
but... there are currently some limitations, and I think mid-term we will need to enhance the parameter/controller interface a bit.
I plan to do a bit of this to implement the push, and of course its also likely to be addressed when/if @johannes resurrects AxolotiRemote ... when we do this, its very likely the API will be a bit more open, so that controllers can be added., and of course if the code is open source, it will allow people to have a reference to see how its done.
so summary is, yes its possible, but on the software side you will need to be a reasonably experienced programmer.... and also probably good with hardware too
but watch this space, its definitely an area which I want to make improvements in.
Hi,
Thanks a lot for answering my question.
I was thinking about the axoloti remote current implementation though i haven't had the time to check the code yet.
I did some C at school but im a Java developper by trade so i guess im not going to be completely lost but i understand its going to be a challenge.
Im curious about your 'push' implementation, great idea i think though im not familiar with this controller.
Cheers.
if you check the firmware, updateDisplay() its reasonably clear.
as Ive pointed out previously, its subject to change... since when we fully implement controllers like Push/Axoloti Control ... the requirements will become clearer.
(e.g. currently updateDisplay pushes a rendered image, they may or may not the final solution)