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
Many other live coding languages allow for per-block or per-line execution of code. Maybe this is something to look into to help create different sections in a performances/piece that can executed separately. For example use a part or section keyword:
In the browser version this is in an experimental working state with the shortkey shift-alt-enter and only executes grouped code that has no empty lines between it. e.g.:
// execute the block below by placing the cursor on the line of the kick or snare and hitting shift-alt-enternewsamplekick_909time(1/4)
newsamplehat_909time(1/8)
// the synth is not audible because it is not connected with the top code because of the empty linenewsynthsawnote(01) shape(-1)
An other idea to work with sections could be to include a new function called playbar() (or bar or something alike). This would allow instruments to mute/unmute for specific bars without having to create a new rhythm appended with 0's and without being restricted by the time() function. The bar length would be determined by the signature setting. Or maybe as an argument in the function. For example:
setsignature4/4// these two instruments would alternate playing every barnewsynthsinenote(02) time(1/16) play(euclid(115)) bar([10])
newsamplehat_808time(1/8) bar([01])
// this instrument would play 2 bars and 1 bar silent, but the bar length is set to 7/8 instead of 4/4newsamplesnare_808time(3/16) bar([110] 7/8)
Many other live coding languages allow for per-block or per-line execution of code. Maybe this is something to look into to help create different sections in a performances/piece that can executed separately. For example use a
part
orsection
keyword:Or maybe simplified with parenthesis or curly brackets
The text was updated successfully, but these errors were encountered: