I have been having issues the past few days with my Mod Duo X. Sometimes I save a pedalboard and it’s fine, other times, I get the message that it saved, but when I load it something goes wrong and it doesn’t work. I had one where once I went to the second page of assigned parameters on the hardware, I saw none, and then every page was blank - no parameters.
I have noticed that when I go to my list of pedalboards in the browser, some do not have a screenshot, but have the purple zero. What specifically does that mean? The pedalboard just doesn’t have a screenshot? or it is broken?
This happens to me from time to time. Usually, saving again and waiting for the image to generate usually works. However, I only experience this on a 1-at-a-time basis, and not all the pedalboards at once.
What I have seen lately is that there can be a plugin instance referenced on the pedalboard that is not actually used, but didnt get fully removed properly. Can happen if, for example, loading the template/new pedalboard that includes a plugin that was removed (which makes it spread to all saved pedalboards) or if something crashed during add/remove plugin action and then the pedalboard page was reloaded.
Maybe happens in more cases, but I have seen these 2 as triggers of this issue.
Are you saying that if you have a reverb sitting in the pedalboard, but not wired to anything, that this will cause an issue? Because I do that all the time. When I’m working on complex pedalboards, I will have reverb settings I want to keep, but need to move things around, so a few plug-ins sit ‘in waiting’ without being wired to anything, but with the settings I want for each.
I am having the same problem i can’t upload my pedalboard because screenshot fails.
Firmware version i am one down the latest available i think (dwarf is not connected at the moment so i can’t check right now)
Since there are quite a few pedals it might be that i have some dirty settings from previous pedals and pedalboards i have removed.
The lack of general grid that shows all of the current settings clearly make things complicated to debug.
@falkTX is there a way to debug this problem from CLI?
There are some fixes for this in the upcoming 1.13 release, would you be able to check and confirm the fix if I give you an early build? (you may or may not be interested on test builds on the long term, so dont want to force that).