sonic-pi
sonic-pi copied to clipboard
[bug-report] - samaaron/sonic-pi - malfunctions within the scope of HCI and Preferences (MacOS)
[bug-report] - samaaron/sonic-pi - malfunctions within the scope of HCI and Preferences
Greetings
I was broadcasting live to to twitch and youtube via restream and:
- sonic pi stopped receiving user input
My first was:
- there is a corruption within the sonic pi input
what could be the cause for that?
- too much preferences tweaking within UI/UX
- too much code allocated in buffering
what did I decided to do:
- to erase preferences;
how did i achieve this? on terminal, i typed:
sudo cd Preferences/ && ls -alRSA && rm -rf net.sonic-pi.gui-keys-bindings.plist net.sonic-pi.gui-settings.plist net.sonic-pi.gui-settings.plist
what did happen?
- i started sonic pi
- the preferences i previously had before were restored, somehow
shall we consider this a bug? how can we fix this

Hey @tmm2018. Similarly to https://github.com/samaaron/sonic-pi/issues/1944, a little more detail here would be very helpful. For example, what previous UI preferences did you think had been cleared, that seemed to be 'restored'?
It may be related to some of those:
- tweaking UI
- changing background to black
- changing to modern icons
- changing modules and re-arranging layout
- adding large portions of code to buffers
usually the way as i fix this is by:
- remove the preferences files
- remove the ~/.sonic-pi folder
- rebooting system
somtimes it works, sometimes it doesn't work
i would love to be able to have a stable version of sonic pi, once this would allow me to:
- sequencing *.scsyndefs very easily, to make more experimental and more extreme music
- sequencing beat using my own sample libraries, in order to have an algorithmic composition tool, that can work as a cool and easy to use replacement tool for ableton live
on the basis of this acessment is:
- the fact that easy, intuitive, and simple to use tools are basically the best for doing stuff with tinkering with music
- the fact that opensource alternatives to commercial software are basically better because you can modify the source legally, and coming up with your own tools
that doesn't mean:
- don't spend some time reverse engineer commercial software, and trying to bring some of its principles towards opensource, while improving those, and vice versa