Index: lines resources

a collection of learning resources, curated by lines members. please edit. this is a wiki.

for monome specific information, read the monome docs and also please contribute using github.




Programming tools and environment


A Github Glossary

Pull request

in projects hosted on GitHub, often only a select few people are allowed to make changes to the online version of the repository, which serves as the “one true” version of the repository. When others have made changes to the project that they would like to contribute to the whole project, they open a “pull request,” requesting that the repository owner “pull in” the changes that they have made.

Pull up resistor

entirely unrelated to software version control, a “pull-up” or “pull-down” resistor sets the “resting state” of an electrical line by providing a weak (high-impedance) connection to a positive voltage (pull-up) or ground (pull-down.) this is typically needed when multiple circuits are “reading” and “setting” the same line by means of transistors or switches (components which physically connect or disconnect the line from ground or +V.) without the pullup/pulldown resistors, the line would be left in a “floating” and indeterminate state whenever no “clients” are actively setting it.

most relevant to modular synthesizer usage, pullup resistors are required in systems which use an i2c bus. (which is active-low.) the amount of pullup resistance required can depend on the number and characteristics of components attached to the bus - the pullup resistance must be large enough to be “defeated” when a switch is closed, but small enough that it still “reads” as a connection to +V when all switches are open. This Sparkfun article explains more about pull-ups from an electronics perspective.


acronym for “read evaluate print loop.” This is a sort of “command line interface” that allows users to try short commands and gain quick feedback about their effect. Maiden’s REPL (at the bottom of the screen) is perhaps the most commonly referenced one here.


short for “repository.” In git, a repository is a folder containing everything to do with a project. Git tracks the contents of these folders to allow for version control and collaboration over the web.


Mozaic Mozaic - Scriptable iOS midi plugin

  • edit this wiki and add something here


Making Music

Resources & Inspiration


Music Tools & Technologies

By module



Discourse is the forum software used by The following information may be useful for editing this post!

You can also access a built-in tutorial by sending a private message to @discobot as described here.



ok! please feel free to add categories to the above post. discussion about content can happen in this thread.


There are some hopefully useful ideas in the below linked thread… I have to go get into Boston commuter hell now so I will let this speak for me until I can get back for more later… thanks again for the support on this!!!

1 Like

Would a glossary be helpful ?

Some terms I would have liked to understand, and more to come:

Pull request
Pull up


Is this meant to be for purely technical threads or would it be okay to include generally useful threads like for example recipe threads or ADHD/cognitive functioning threads?

1 Like

My 2c, I’m inclined to think we should be linking to specific posts and not threads. Also, am I right in thinking that the general user, or even regulars cannot create wiki posts?

1 Like

I’m not sure why the distinction is being made of having " on " in front of the lines posts but if people seem to like that I tried to clean it up a little so it was more readable

I made a couple changes

added SOS secrets
“fixed”? (maybe just to me haha) “on lines:” formatting. if this wasn’t there I don’t think the bolding would be necessary

tried to unify the posting method

if it is on lines then it says so, also that seems to come first in each heading
bolding the important links

formatting on the github heading in tools and environment

added shbobo to language specific

added making music heading
added resources & inspiration (under making music) subheading
added pocket operations
executing the modular album
learning music ableton
modular ahha moments

@GoneCaving I see what you are saying about linking to specific posts I think I’d like a blend of the two potentially (see the shbobo shnth link for how I’d handle it)

EDIT: I thought it would indent nicer than that hmmm maybe that isn’t the solution I’ll leave it up for now and think some more because I do like having the link back to the original start of the thread while also having specific posts mentioned


I believe that by default Regulars can make their own posts wiki.

@oot this is only my opinion, but I like the current focus on the technical.


My inspiration for proposing an index was born from my challenges with navigating a vast sea of technical information…

That is not to say that other topics are not valid but perhaps they could be grouped under a heading at the bottom such as “other topics”?


i’m mostly aligned with the technical/music-making focus, despite the benefits of some of the more general tips/tricks threads. easter eggs aren’t quite as fun if there’s a map to all of them.

@GoneCaving: echoing @alanza, regulars can make their own wiki posts. i’m wondering if your question is about editing wiki posts? i’m pretty sure that’s possible for members & upward.


No, it was about making wiki posts. I’ve gone hunting and now see how to do it (its not so obvious!).

1 Like

Please share that info, on the index would be great.

One thing I totally overlooked for inclusion on the index is Discourse!

Also it would be great to have links to the official monome docs at the top :sunglasses:

1 Like

should live-coding stuff be a separate category in the programming section? planning to add some ORCA IDE & SonicPi stuff later.

@wednesdayayay thanks for the formatting/edits. i think they help a lot. and i’m with you re: a mix of threads & individual posts. some of the threads are focused & content-rich enough to merit full inclusion.

also, i’ll be better able to add to the wiki when i’m not just accessing via phone. i’ll set aside some time with my laptop this weekend & dig in.


any recommendations how to format this better?

I imagine some threads that get posted could have a lot of individual posts linked that would be nice to access quickly in this way

however it sticks out like a sore thumb in the flow of things
it also doesn’t need to always be open which is why this drop down menu is nice
but it can’t be indented at all (at least I can’t figure it out)

1 Like

Figured it out I think, you have to put a bullet and then indent everything under the [details] block the same amount:

* [details="Shnth"]

I originally conceived that there could be separate pages (or a continuation further below) with further details so that the top-level topical lists wouldn’t get jammed up with a lot of details…

Kind of a table of contents at the top…

Regarding posts and threads, it’s great to have specific links, but in a perfect world it would be great to have teams distilling the gems into more accessible chunks… that would be most user friendly, while also recognizing the value of actually reading threads…


probably want to put the glossary in the top post, at the bottom.

i think it’s best if all the information is in the top post rather than anyone feel the need to dig into the meta-discussion of this thread.


this is wonderful thank you!
@tehn glossary has been added to top post


i might suggest a different format for the headings “here on lllllllll” and “elsewhere” as they are repeated too often and break the flow.

perhaps just group the “here at llll” links first, then give a little divider, then the elsewhere list


  • here
  • here
  • here
  • elsewhere
  • elsewhere
- here
- here
- here
- elsewhere
- elsewhere

yeah that was what I was getting at earlier
I don’t know that we need to make that distinction