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
Currently, the way time argument is interpreted is not consistent across functions that use time as an argument, for example:
time(4) -> 4 measures worth of time
length(4) -> 4 milliseconds
I would suggest to make an integer or fraction represent a multiple/subdivision of a measure and add a time unit specificier if other measures of time are desired, for example:
length(4) -> 4 measures worth of time
length(4ms) -> 4 milliseconds
length(4s) -> 4 seconds
this could be extended to other values, for which there is a default unit, but different units could be specified, for example:
fx(filter low 4) -> filter cutoff at 4 Hz
fx(filter low 4kHz) -> filter cutoff at 4000 Hz or fx(filter low 4k) to save typing