When the pedalboard is changed via pi-Stomp hardware or rest, the pedalboard name in the Mod UI does not track. The name shown in the web UI will be the name of the previous pedalboard. The correct name can be restored by refreshing the page in the browser. Although, it's easy to refresh, it's likely to one to forget, and if a pedalboard save operation is evoked, the save will overwrite the previous pedalboard with the current content. That's bad.
The issue is not specific to pi-Stomp. Executing the pedalboard change rest api command yields the same behavior:
curl localhost/reset; curl -F 'bundlepath=/var/modep/pedalboards/AmpSim.pedalboard' localhost/pedalboard/load_bundle/
It's possible that this bug has been fixed in new releases of mod-ui. pi-Stomp is relying on the modep-mod-ui patchbox module for that code, so a fix maybe slow to come. We'll have to see if an issue exists against mod-ui and track when a fix might become available.
When the pedalboard is changed via pi-Stomp hardware or rest, the pedalboard name in the Mod UI does not track. The name shown in the web UI will be the name of the previous pedalboard. The correct name can be restored by refreshing the page in the browser. Although, it's easy to refresh, it's likely to one to forget, and if a pedalboard save operation is evoked, the save will overwrite the previous pedalboard with the current content. That's bad.
The issue is not specific to pi-Stomp. Executing the pedalboard change rest api command yields the same behavior: curl localhost/reset; curl -F 'bundlepath=/var/modep/pedalboards/AmpSim.pedalboard' localhost/pedalboard/load_bundle/
It's possible that this bug has been fixed in new releases of mod-ui. pi-Stomp is relying on the modep-mod-ui patchbox module for that code, so a fix maybe slow to come. We'll have to see if an issue exists against mod-ui and track when a fix might become available.