Erratic behaviour with instrument menu #24
Labels
No Label
bug
feature-request
sounds
UI
UX/QoL
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: kieran-mcauliffe/healing-soundscapes#24
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hi.
I'm not able to choose an instrument and save it in a preset.
Here is a video that demonstrates the issue.
Transform in having general issue selecting an instrument in the browser... But not for player 1, only for 2 3 and 4
OK especially the 2nd player. List in the browser does not correponsd to index of the sampler.
@computermusik could you have a look at it, please ?
Here is a richer description of the problem for you @computermusik. Hope this helps solving this weird bug.
As you can imagine this bug is more like a fluke as I can't reproduce it and it didn't occur on anyone else's machine. Otherwise, they wouldn't have been able to save their presets.
Nonetheless, I have introduced a feature that might help in scenarios such as this one. Can you please change Output Mode to 5 and report whether the issue still persists? I so please click on the Init button to refresh the interface.
Well, it looks way better, but when I store a preset and recall it, then it is the wrong instrument coming back in the sampler only (not in the browser)...
Please init the browser and try again. Also please post or send me the bank file so I can have a look.
It seems that for some reason the browser interface freezes on your computer. I had worked on and fixed this issue, but it might well be that you still have an older copy of the js file. In order to find out I would like to have a Zoom session comparing the js versions. I also hope that no one by accident uploaded the old version the repo.
The freezing manifest itself when you’re changing the values manually in the interface and then send an Drawsocket html message to the element. You wouldn’t see a change unless you created a JavaScript function to update the value. This I fixed over the summer. I wonder wether that’s in the file that you’re using.