Another issue I have with the Dwarf is the lack of direct editing capabilities on the device itself.
Of course, building an entire pedalboard from scratch using that tiny LCD screen is out of the question — but adjusting a simple plugin parameter should definitely be possible.
With the Performance View, I already have a convenient way to do this, but I want a solution that works directly on the Dwarf, in case it’s ever needed.
Here’s what I’ve implemented so far (apologies for the shaky video).
For sure! When released, we will have two ways of doing changes: with a smartphone in the performance view and directly on the dwarf.
From my POV this is a requirement for real live use, not because you will edit parameters during the performance in this way, but because in case of emergency e.g. if something sounds really bad in the soundcheck you will have the opportunity to fixing it.
This give me a sense of security and control also from a psychological pov.
Oh man, I have essentially a live use of the Dwarf, the bluetooth connection with my phone or my ipad takes so much time, that would be so great, I was waiting this for a long time !
the bluetooth connection with my phone or my ipad takes so much time
I think this, at least in part is due to loading the high resolution plugin images, if these images were replaced with simpler, lightweight ones suitable for use on a phone/tablet, I think this would still be a viable method for editing.
Like @LievenDV, I bind the most important controls in advance, so I don’t really feel a need for on-device editing, but I do like the idea of a low-bandwidth UI for use in emergencies.
I absolutely love this feature.
In this scenario I use a wifi dongle (that’s way faster than Bluetooth), but your proposal is the killer feature I was waiting for.
I’m just curious: have you already thought how to manage the plugins that have a lot of parameters? Do you think you’ll be able to scroll pages indefinitely, or do you think you’ll have to set a limit?
You’re right, I use the allguis method to load images first :
But sometimes it doesn’t work with complex pedalboards. My workaround is to load first a blank pedalboard and then my pedalboard, but it’s time consuming…
I also don’t think that using footswichs would be ideal.
I was only asking because I thought that could be a limit on pages. Anyway,for those particular kind of plugins, I think that the best way to tweak parameters will be the web ui (or your performance view ).
But for anything else, I would gladly use your implementation to operate directly on the device.
I expanded the protocol to just ask the controls count and a set of controls (for dwarf 3 controls each page), so hmi in memory has only the current 3 controls displayed.
All the firmware code is designed with this in mind as I can tell, even if I found the protocol used more complex that it needs to be (it’s designed with the concept of page also server side)
So don’t worry the only limit is pratical: how many times you have to push forward to reach the page
| In those cases, this owuld have been handy
).