refreshing the browser window appears to fix the problem.
given the behavior it is likely that the rename operation was completed on the device (via the http backend) and the return response is either:
an error which would cause maiden to not update its local state with the renamed file/url
the rename logic for the buffer file tree state in the maiden isn't finding the matching node to update.
refreshing the browser window is effectively forcing the on device file tree to be re-read which seem to be further evidence that the change is made on device but the browser based data is not being brought in sync.
it appears that occasionally after renaming a file in
maiden
it is no longer possible to play the file. https://llllllll.co/t/norns-help/14016/268 https://llllllll.co/t/norns-help/14016/269refreshing the browser window appears to fix the problem.
given the behavior it is likely that the rename operation was completed on the device (via the http backend) and the return response is either:
maiden
to not update its local state with the renamed file/urlmaiden
isn't finding the matching node to update.refreshing the browser window is effectively forcing the on device file tree to be re-read which seem to be further evidence that the change is made on device but the browser based data is not being brought in sync.