Questions about last update #73
-
Hi, I've also found that web manager write with wrong owner and permission when I try to copy a bank, permission is 0664 instead 0775 and owner is www-data:www-data. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
I too am having problems scrolling through the patches after updating. I've been using this on and off for about a year and a half. And on my LaunchKey37 and RPi3 it seemed to work well enough for me, but when I started to try and really set it up in a better way it all stopped working. I've tried using the pots to select patches which used to work well. But now just shuts off the RPi. And I've tried to use pad buttons in an incremental way, (like how it's intended to be used), but nothing I do will make the patches or banks change. I've been rackin my brains for the last few days on how to troubleshoot it, & how to see what my midi controller is sending to the RPi. I'm not sure which files store the settings for what change controls change the patches or banks. |
Beta Was this translation helpful? Give feedback.
-
Oops, there were two issues here. TL;DR you can re-run the install script ( First, in a recent update I changed these lines to these - I thought the SELECT_PATCH option was confusing to some people, and created surprising and odd behavior if they already had a control assigned to CC#24, so I set it to @tizfra the permissions and ownership are correct. The installer adds you to the www-data group, and permissions 664 means user+group can read/write, so you should be able to edit and move the banks. 775 would be user+group can read/write/execute. Thanks for pointing out these issues - let me know if there are still problems! |
Beta Was this translation helpful? Give feedback.
Oops, there were two issues here. TL;DR you can re-run the install script (
curl -L git.io/squishbox | bash
) and it will work, except you'll need to edit this line afterward if you want to use a knob/slider/pot to scroll through patches.First, in a recent update I changed these lines to these - I thought the SELECT_PATCH option was confusing to some people, and created surprising and odd behavior if they already had a control assigned to CC#24, so I set it to
None
by default. Second, I tried to add a universalpatch
router rule keyword to give people more control over using MIDI messages to select patches, but I messed up the syntax in headlesspi.py.@tizfra the permissions and ownership …