Mod Duo X not correctly saving pedal board control assignments

true that! my workaround is to to always include a “P3” (or whatever page it is) in the text fields of the two endless encoders; since those fields have more characters available, i can always find a way to include that plus a parameter label. and, yeah, i always have to butcher parameter names in all the other fields to have short labels which are just enough to remind me what they are without actually necessarily naming the parameter.

3 Likes

Thank you! That’s an excellent workaround. I really think the Mod team need to rethink the onboard GUI on the Mod devices. I also wonder whether a firmware upgrade couldn’t do something to improve the type script resolution, or allow it to be altered further than can be achieved using only the brightness and contrast controls, because if you think about the relative total clarity we expect from today’s smartphones, having a screen with such a woefully inadequate resolution on a high tech product such as these seems like a bit of a slap in the face when you look at the commercial alternatives.
Would it have cost them so much more to have provided a decent quality screen with at least the resolution one would expect from any of today’s low tier smartphone offerings? I just feel that it really cheapens the appearance and performance or usability of these products, which is a real shame. Back in the UK we have a saying which really applies here: “Don’t spoil the ship for a ha’peth of tar!”

Bear in mind we are talking about a device that was released in mid '19: we cannot compare it towards nowadays screens :man_shrugging:

1 Like

also: i’ll take a little more CPU power for DSP, rather than using it to compute a higher resolution display, any day! :wink:

2 Likes

You have a point…

I actually didn’t know that! I thought it was much more recently released. In any case, from what you’ve told me it’s easier to understand why the display is as it is, although it must be said that although the displays were not full colour, some of the Roland processors which came out in 1999 had a very crisp and clear display, and there were several other makes releasing devices with displays with a similar quality to Roland, so in a way that’s not really a good excuse.
I don’t expect the display to be full colour, but it should have been crisp and clear at least.
If I had been involved in the project back when it was in development I would have suggested having an additional function which would allow the left screen to show much the same information as it does now, but with the option of zooming in on whichever control was being manipulated on the second screen, showing the text exactiy as it was saved when configuring the control assignments, so one could see precisely what effect the control was having on the plugin being used.
Another option would be to be able to transfer the screen content to another device such as an iPad via Bluetooth. That way you could see the content of the screen more easily and be able to tweak more precisely, then save to a snapshot or whatever…