In order for this to work, you will need to take screenshots of each of the buttons in a highlighted state and a nonhighlighted state, and put them in a folder so that the path is right.
The script as-is mutes/unmutes when you hit ctrl-alt-(1-4)
Never messed with Auto-IT3; AutoHotkey can compare your screen against existing image files and then use that comparison to build a target for a mouseclick (which is what is done in this script).
So it’s not under the hood at all, it’s just working off the way the app looks. But that’s maintainable enough for Renoise because it’s usually possible to get it into a known state re: what’s onscreen, at least for this purpose.
Well, AutoIT3 has a function which can scan a certain area for pixel value and if something changes in that area, it can trigger an event… i have not really investigated if it can do more in that regard. I’ve used the function to detect tray-icon popup dialog that does not have any window handles or whatsoever to recognize its appearance.
with the backslash key, but this only works for the current selected track.
So if you want to mute more tracks you have to use the tab as well to shift the cursor.
No. Defaults are Ctrl + NumPad for tracks 0-9 for a total of 32 tracks that can be assigned. Of course you can always change these. I did have them on the F-Keys as a secondary set-up at one point, for example.
Nopes, not even the writer of the manual is all integrated. I should only feel ashamed for not investigating this more thoroughly (Bantai is a lot sharper on these terms fortunately). My sincere apologies. But yes: i don’t use these keys since i have a workflow that does not require this feature.