> For the complete documentation index, see [llms.txt](https://benjohansen.gitbook.io/eacomp/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://benjohansen.gitbook.io/eacomp/old/course-schedule-spring2021-mus4203/max-qwerty.md).

# Max qwerty (due Feb.11)

Using the samples you recorded (some long and some short) for the last homework, create a Max patch that you can use to perform your samples using nothing but your computer QWERTY keyboard. You can make it function however you please (keys can start and stop samples or transition from samples to other samples, randomness can be at play also).

One very important learning outcome is to understand how to use the line\~ object, so you must include that object in your patch. It is a difficult object to understand completely, so I suggest you check out Darwin Grosse's tutorial = <http://darwingrosse.com/20Objects/lesson15.html>

Here are other objects you may include:

* play\~
* \*\~
* \[button]
* key
* upkey
* dac\~
* gain\~

Remember, the patch from last class (Feb.4) is on Box = <https://baylor.box.com/s/iww2xi7c6fytfigfeq65mu8j8w6ca6ml>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://benjohansen.gitbook.io/eacomp/old/course-schedule-spring2021-mus4203/max-qwerty.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.