You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An undocumented feature: If the synth supports detailed parameters (like the Rev2), you can actually type a python expression into the name search advanced filter. If you prefix the name search with an exclamation mark, the current patch will be a dictionary called p.
The syntax matches the pytschirp syntax.
Example:
!p["LPF Audio Mod"].get()!=0
Will search for patches that use the Rev2's audio mod feature for the low pass filter.
The names of the parameters currently can be seen best in the Patch Diff dialog. If there are no parameters shown in the patch diff, the synth does not support detailed parameters yet.
To productize: currently, the search is run in memory, so I would need to load all patches first, not just a single page, and then run the search. Exploding that information into the SQL database probably is overkill for a desktop application, that would make most sense in a client/server scenario.
Also, the parameters would need to be documented, e.g. an autocomplete of parameter name.
The syntax is ugly with the p["..."].get(), these characteres could go away and be added automatically. Or I improve pytschirp to allow better syntax.
The text was updated successfully, but these errors were encountered:
An undocumented feature: If the synth supports detailed parameters (like the Rev2), you can actually type a python expression into the name search advanced filter. If you prefix the name search with an exclamation mark, the current patch will be a dictionary called
p
.The syntax matches the pytschirp syntax.
Example:
Will search for patches that use the Rev2's audio mod feature for the low pass filter.
The names of the parameters currently can be seen best in the Patch Diff dialog. If there are no parameters shown in the patch diff, the synth does not support detailed parameters yet.
To productize: currently, the search is run in memory, so I would need to load all patches first, not just a single page, and then run the search. Exploding that information into the SQL database probably is overkill for a desktop application, that would make most sense in a client/server scenario.
Also, the parameters would need to be documented, e.g. an autocomplete of parameter name.
The syntax is ugly with the p["..."].get(), these characteres could go away and be added automatically. Or I improve pytschirp to allow better syntax.
The text was updated successfully, but these errors were encountered: