Scholarly discussion of the music of John Cage.

[Eric Theise <>]

Hi David, Andrew, (here comes) everyone,

Inspired by Andrew's quite clear explication of the algorithm in Monday's email I coded up a Python 3 module to do the work at the command line: PyMesomake

Code and instructions are at https://github.com/erictheise/pymesomake . I'm a rare and reluctant user of Windows so I tested the distribution and wrote the installation instructions for that platform. Instructions for MacOS and Linux have not been fleshed out yet but there's likely enough in the Windows instructions for users of those platforms to get going.

Here's a list of what doesn't work:

  * printing line breaks between mesowords in the final output

  * alerts when letters from the mesostring are not found in the sourcefile

  * the 100% rule

  * no right wing words for the final letter in the mesostring; I am thinking the right thing to do is to cycle back to the first letter (a commodius vicus of recirculation).

I'll be addressing those issues and embedding the module in a publicly available website as time permits.

I've had a run of good fortune recently – a new grant to have digital scans of old & in-progress 16mm films scanned next week, plus today I picked up a hard drive containing old videotape-based work that's been recovered through an earlier Bay Area Video Coalition Preservation Access Program grant – so I'm sliding PyMesomake onto the back burner to bubble on low flame for a bit.

Apologies if I'm slow to answer questions. Feel free to lodge issues at the GitHub site. Thanks for the learning opportunity and hope some of you have fun taking it for a spin.

Cheers, Eric

On Mon, Jan 14, 2019 at 5:29 PM David Bellows <> wrote:

Hello Andrew,

Thank you very, very much for setting the record straight on this!
There is so much speculation online about mesostics that it became
impossible for me to make any choices with confidence so I ended up
basically including everything everyone said.

Your line:

> It’s worth mentioning that there are no chance operations involved. This is process, not chance. (Think about what that means.)

Really brings it all home and makes everything clear. Process, not
chance. Perfect!

Thank you again,
Dave Bellows


On Mon, Jan 14, 2019 at 4:40 PM AHF <> wrote:
>
> Hi All,
>
> This has to come from my leaky memory — no source code available to me at this time.
>
> The “writing through' method of mesostic making.
>
> Input a source text, possibly quite long. For example: The Book of Genesis. (I remember typing that into the computer round about 84 or 85, before there were online versions believe it or not. It’s a hell of a book.)
>
> Input a mesostring, quite short, for example “Messe des Pauvres”.
>
> Using software, scan the source text for the first word having the first letter of the mesostring but not followed by the 2nd letter of the mesostring. This is the 50% rule — which John and I certainly started out with. Most likely I did a 100% version later on, but I can’t recall if and where it was used.
>
> Proceed on to the 2nd letter, as for the first. Continue to the end of the mesostring. Result is one found mesoword per line of the output poem.
>
> Find all the wing words that fit the 50% rule on either side of the mesowords. Go backwards, to the left of the mesoword in the source text, stopping when the rule rejects a word. Do the same forwards, to the right. Fill in all the words on both sides up to but not including the breaking words.
>
> Print it out on paper, then using a pencil, cross out words on the tips of the wings, left and right, that by taste you decide you can do without. The remaining words are always contiguous: you prune in from the ends, not by jumping around. (Memory alert — maybe at some point John did jump around, but I doubt it.)
>
> Accept stanza breaks based on the word breaks in the mesostring, or not, perhaps instead breaking stanza’s for breathing when reading, or some other performative constraint, or just based on how the reading flows.
>
> That’s it.
>
> It’s worth mentioning that there are no chance operations involved. This is process, not chance. (Think about what that means.)
>
> Writing-through is not the only way John made mesostics. He often just fit words around some text, often someone’s name, as they came to him, typically the 50% to 100% rule.
>
> It looks from my notes here that mesomake is a writing-through tool, while mesolist produces a catalogue of all the words matching each letter of the mesostring in the source text, and mlfind get’s one word for each mesoletter from a mesolist list. In any case, very different results.
>
> The point is: “mesostic" and "writing-through" are not synonyms.
>
> I hope this clarifies things a bit.
>
> Andrew Culver
>