athenaCL Tutorial Manual: Second Edition, Version 1.4.8 | ||
---|---|---|
Prev | Chapter 5. Tutorial 5: Creating and Editing Textures | Next |
Textures can be muted to disable the inclusion of their events in all EventOutputs. Textures and their Clones (see Chapter 7) can be muted independently. The command TImute, if no arguments are given, toggles the current Texture's mute status. The following example demonstrates muting Texture a1, listing all Textures with with TIls, and then displaying the collection of Textures with the TEmap command. Notice that in the TIls display, the "status" of Texture a1 is set to "o", meaning that it is muted.
Example 5-18. Muting a Texture with TImute
[PI(auto-muteHiConga)TI(a1)] :: timute TI a1 is now muted. [PI(auto-muteHiConga)TI(a1)] :: tils TextureInstances available: {name,status,TM,PI,instrument,time,TC} + a1 o LineGroove auto-lowConga 64 05.0--20.0 0 b1 + LineGroove auto-muteHiConga 62 00.0--20.0 0 [PI(auto-muteHiConga)TI(a1)] :: temap TextureEnsemble Map: 20.16s | . | . | . | . | a1 ____________________________________________ b1 ____________________________________________________________
By providing the name of one or more Textures as command-line arguments, numerous Texture's mute status can be toggled. In the following example, Texture a1 is given as an argument to the TImute command. The TIls command shows that the Texture is no longer muted.
Example 5-19. Removing mute status with TImute
[PI(auto-muteHiConga)TI(a1)] :: timute a1 TI a1 is no longer muted. [PI(auto-muteHiConga)TI(a1)] :: tils TextureInstances available: {name,status,TM,PI,instrument,time,TC} + a1 + LineGroove auto-lowConga 64 05.0--20.0 0 b1 + LineGroove auto-muteHiConga 62 00.0--20.0 0