Compiling a Vortex
Compiling a vortex means, first and foremost, nagging and coercing #listeningclub members to submit. Submit tracks, you weirdo. And second, it means assembling those tracks into a (possibly coherent) single MP3 file for playback on the final Sunday of the month.
It’s performance art. It’s project management. It’s attention to detail.
The starting point for a round of LC vortex is a musical theme for those submitted tracks. You inherit the theme that last month’s compiler prompted the LC masses to invent and agree on. Theme prompting becomes your job, before all’s said and done, in prep for the vortex after yours.
To see some past themes, check out the list.
So, the steps here assume we’ve already settled on a theme for your vortex: submitters will aim (or not) to abide by it.
Roughly speaking, as you act as compiler for this month’s vortex you perform the following steps:
- Determine logistics for submitting tracks
- Pick a submission deadline
- Announce and nag
- Assemble the tracks into a single vortex file
- Create a text file listing tracks and submitters
- (Optional) Write an intro blurb
- Provide the goodies to @Kleptones
- Coordinate picking a compiler for next time.
- Coordinate picking a theme for next time.
Details if you need them:
Determine logistics for submitting tracks
Pick a submission deadline
Announce and nag
Assemble the tracks into a single vortex file
Create a text file listing tracks and submitters
(Optional) Write an intro blurb
Provide the vortex file and track list to @Kleptones
Coordinate picking a compiler for next time
Coordinate picking a theme for next time
To contribute to this chapter, start by forking this project