It seams the Pi-stomp “team” has done some work here, so there may just be a merge from their github ?
(never tried a pi-stomp but it seams to work without a computer)
Sure the screen is colorful and seams to have a bit more pixels, but the way you can change parameters for each plugin doesn’t seam to need a lot more pixel or any color than the Dwarf offers, no ?
I would like too to change any param direct on mod equipment without manual assignment.
The software that controls the mod devices screens is closed source, so there isn’t possible to contribute this with the mod team.
I can’t even imagine how you could achieve that realistically given the routing flexibility on the Mod devices.
The Boss GT1000 has a good system in place but it has a pretty linear signal chain aside from the odd parallel divider. Most people I spoke to favoured editing via a computer regardless and in a live situation being able to manually set parameters you could tweak on the unit would have been an improvement instead of trawling pages of fx blocks.
Hi, so we do not have the ability to build pedalboards on pi-stomp, but we do expose all of the plugins parameters in our UI to be able to change things on the fly. This is done through our own “API” injected into mod-ui. Not sure it would work on mods hardware as they don’t show all the plugins on the main screen like we do.
Well, creating pedalboards would be really hard, but tweaking parameters should be feasible: one first screen with a browsable list of all the plugin instances on the current pedalboard, clicking on one of them you could enter on a list with the plugin parameters
OTOH i still can’t see the benefits compared to having a tablet close to it, except maybe that you can’t enter in navigation mode (select pedalboard and snapshot) when the web ui is connected… and that the web ui uses some cpu… Ok, there would actually be some benefit 
Maybe merge this post with Parameter assignment directly on the device and Access every plugin parameter from the Dwarf screen since we have the same request:
Being able to modify plugin parameters at any time without restrictions (no need to previously map it to a button).
I embrace the flexibility on Mod devices and the clever web interface but modify parameters on the fly is convenient (like a normal guitar pedal…)
The way it has been done on the pi-stomp seems clever to me and only with 1 knob
Maybe you can collaborate and turn this into the OS itself? And then add ability to add/delete/move plugins
Seems sensible doremi.
Thinking about it, in order to assign parameters on the unit first you have to be able to find the parameter, then assign it (I realise I’m starting the obvious!). So being able to select the parameter and tweak it would be half-way there.
Being able to then optionally store an assignment for that parameter would be the icing on the cake of course!
Or would that just make it easier for the Mod Audio crew to ignore if it was a single post? I acknowledge that with most things they’re very involved in what we ask for even if it’s just to say “no” or “not right now,” but there are three or four different threads on this (at least two of which point out it was a promised feature in the original press drop) and NOBODY from the company has chimed in on any of them! At a certain point it’s not paranoia; they really are ignoring it on purpose.
Creating complex pedalboards might be really hard, but perhaps stringing together a mono board with effects in a straight series (and rearranging them) shouldn’t be that tough. Even the Zoom MultiStomp pedals let you do that.
While idea of complete standalone configuration sounds appealing, I can’t imagine a way how the flexible and sophisticated pedalboard routing of the MOD platform could be expressed via a couple of knobs without being unbearable. ( Even in the much simpler linear configuration of the classic BOSS processors, configuring presets was at least uncomfortable, and I had switched to setting parameters from the PC app quite fast)
I guess the best bet here is to have a lightweight simplistic interface for the mobile devices (phones, tables)+ good access point wifi mode support with wifi functionality leaving the “experimental” territory.
I see it like something similar to puredata flow diagrams:
With a full plugin bitmap graphical ui replaced by the minimalistic autogenerated ableton style controls:
This could help to do some pedalboard tuning on the fly with no PC, and be fast enough to work even through bluetooth.
“Don’t you guys have phones” (c)
I totally agree with @doremi here.
The fact that I have to connect my mod to the computer, open up that browser (which also very often doesnt load the gui on the first attempt) just for swapping a chorus effect for a flanger really puts me off and made me switch to a zoom multi fx instead of mod for guitar related stuff.
The mod is still in the setup but more for synth related stuff, running cardinal and as a usb midi router. Since these are more complicated tasks I don’t mind using the editor here so much.
So as a start it would be great if could at least do these things in standalone:
Maybe it is the software developer in me, but also “simply swapping” two effects is not “simple” because the absolute freedom offered by the system when ut comes to define pedalboards.
What if it is not a simple Daisy Chain? What if the output of one effect goes to more than other plugins? Or viceversa? What if one is mono and the other is stereo? It will be really hard to define those special cases…
Maybe it could be enough to have a lighter and simpler UI which can be used without affecting navigation mode.
I once suggested to allow inserting a plugin between two connected ones by dropping it onto the joining cable (by default, it would use the first input and outputs if multiple ones are present, but why not allowing developers to design more complex behaviours using an optional set of rules ?).
We could also have an extra suppress button that keep the connection between the upstream and downstream plugins. Combining these two feature could greatly speed up the editing of pedalboards, especially on moblie platforms.
You mean :
Since developing a lighter/simplier UI, why not the one that even the dwarf could use it with 3 buttons and the b&w screen ?
The most basic UI could be a way to list all the plugins on the pedal board, show an list of the inputs/outputs, and add a “connect to” which shows a list of the potential ports to connect to. But the user experience would not be super great. It could be improved by being clever with the ordering of the lists though. Also one would need to be able to discriminate between two identical plugins if more that one of a given type is used…
Another approach could be to show an ascii art matrix of tiles and to be able to add plugins onto it, and then to select a pair of ports by navigating the tiles with two buttons to create connections. That would be visually a bit better and easier to select the right plugins, but there would then be a difficulty that the positions on the matrix would have to kind of reflect what we see in the Web UI.
As I see it, there are a lot of potential approaches, but they all have the problem of a quite cumbersome UX and the added complication that they would have somehow to reflect what is happeneing in the Web UI for consistency. We don’t want to confuse the user with a totally alien representation of a pedalboard compared to what they can see on the Web UI.
Of course, if we consider them as just “emergency” editing tool when no computer/phone is available, any UI design would be good enough. But the problem is that MOD would then be trapped into maintaining it without the ability to refurb it too much after that. Unless it’s considered a beta thing all along. UI should normally be thought well from the start otherwise you run into all sorts of issues.
I also thought of a quite orthogonal approach (and quite geeky), that actually encompasses a lot more than pedalboard editing, which is exposing a shell on the device itself.
Users could then do pretty much anything on the device without needing an external device. It would require a way to use the buttons to type in stuff, but maybe allowing using a small USB keyboard could also be a thing.
And it could then also be possible for the user to write scripts/python app taylored to their own needs (for instance an ASCII pedalboard editor), instead of relying on the MOD development team to do it.
Is that something you could consider @gianfranco @jon @falkTX ?
Nowadays they call it “using an app”… more or less like when you connect your bluetooth phones and open spotify, you know…
Because it would work better and faster, and would allow for full operations (e.g. creating/modifying a pedalboard)
OTOH having access to the full list of plugins and parameters could be usefull and not impossible
Personally i’d love it but not many musicians would like to use VI to configure their pedalboards 
Especially with a virtual keyboard where you use rotary buttons to select letters 
However, I think the idea is more to allow running arbitrary commands, and more importantly, ascii-art apps. If the current UI had a beta option to allow to select a user written app from a list, we could start writing our own pedalboard editors and share them, and the one most prefered by the user would get a chance to become “official”.
And that would also allow a lot of other things to happen.
hm, i wonder if the dwarf could work with a mobile USB monitor (like an ASUS ZenScreen touch)? that would be cool: plug it in, configure with the flexibility of a desktop, unplug and go.
That would need additional drivers on the unit, which might be too much of a hassle I guess. Also, if we start needing too fancy extra hardware, why not use a phone or tablet?