User:Vitrinekast/Proposal: Difference between revisions

From XPUB & Lens-Based wiki
No edit summary
No edit summary
Line 25: Line 25:
=== Collaboration with Riviera Taylor ===
=== Collaboration with Riviera Taylor ===


Part of this project is a collaboration with Riviera. Me and Riviera will divide the responsibility of hosting, where (in a nutshell) Riviera will focus more on the server side of things and my focus will be around hardware. Together, we will document the hangouts thoroughly in Markdown. We will set up a documentation system, that (due to markdowns fantastic nesting abilities) can have the various outlets we would like. For instance, in the format of a newsletter to be sent out to the community of Klankschool, their archive, parts of my thesis, and Riviera’s thesis.
Part of this project is a collaboration with [[User:Riviera|Riviera]]. Me and Riviera will divide the responsibility of hosting, where (in a nutshell) Riviera will focus more on the server side of things and my focus will be around hardware. Together, we will document the hangouts thoroughly in Markdown. We will set up a documentation system, that (due to markdowns fantastic nesting abilities) can have the various outlets we would like. For instance, in the format of a newsletter to be sent out to the community of Klankschool, their archive, parts of my thesis, and Riviera’s thesis.


Our collaboration will be one with a lowercase c, where we will work together and alongside one another, but are not dependent on each other.
Our collaboration will be one with a lowercase c, where we will work together and alongside one another, but are not dependent on each other.

Revision as of 23:31, 22 November 2024

Make: synthesizers after the apocalypse

In this project, I will research the various ways in which abandoned media can be repurposed into sound devices. I consider "abandoned media" to be discarded devices that no longer serve their original intended purpose yet could still function as something else. For instance, a printer that has an “Internal Communication Problem” being repurposed into a percussive instrument, as happened in Printer Jam [1]. I’ll explore the ideas of speculative sound circuits, where playful and absurdist methodologies are applied to create sound using various unlikely technological devices (Richards, 2018) [2] , and Salvage Computing[3]. This will happen in a series of DIY/DIWO workshops/hangouts. The workshops will be hosted at Klankschool[4], together with Riviera Taylor.

Salvaging sound devices

The real long-term future of computing consists of figuring out how to make the best possible use we can out of the literal millions of devices which already exist Solderpunk, 2020, Cited in de Valk, 2022)[5]

Buying new (electronic) parts and components is usually cheaper than repairing or salvaging. Even more conveniently, in the online community of DIY synthesizers, it is common practice to share an Mouser Project Cart[6] alongside the schematics, when publishing your project. This allows you to buy all the needed parts within just a few clicks. To me, this introduces the idea that you need to buy these super specific components in order to succeed, instead of making the inconveniences that come with salvaging part of the creative process. I’ve found that the DIY/DIWO moments where these notions are less prominent, way more empowering and educational.

Here are some samples I’ve collected during workshops:





DIWO Hangouts

During the hangouts, we will explore various methods around salvaging components and dismantling devices, making our own instruments using these materials, live coding hardware through MQTT/OSC[7] servers & applications, and everything in between. Ultimately, they could lead up to a BYOP (Bring Your Own Printer) Orchestra. The hangouts will be held at the Klankschool and involve the Klankschool community. The hangouts are hosted in collaboration with Riviera Taylor, who’s writing a thesis about System Administration and Server Maintenance, and creating her project around Klankschool too.

Collaboration with Riviera Taylor

Part of this project is a collaboration with Riviera. Me and Riviera will divide the responsibility of hosting, where (in a nutshell) Riviera will focus more on the server side of things and my focus will be around hardware. Together, we will document the hangouts thoroughly in Markdown. We will set up a documentation system, that (due to markdowns fantastic nesting abilities) can have the various outlets we would like. For instance, in the format of a newsletter to be sent out to the community of Klankschool, their archive, parts of my thesis, and Riviera’s thesis.

Our collaboration will be one with a lowercase c, where we will work together and alongside one another, but are not dependent on each other.

Who

  • The klankschool community
  • Trashure expert Joak
  • Operator Radio to talk about post apocalyptic electronic music, but also to create the workshop in a different environment
  • Roodkapje to host events such as the BYOP orchestra
  • XPUB community
  • Creative Coding Utrecht - space to host events

Why

When reading about Salvage Computing I got very excited, as it could give me a different vocabulary when working with salvaged electronic components as a material. The last year I’ve been a part of various workshops around DIY/Electronics/Circuit Bending, etc., and I’ve been increasingly surprised by the way some people spoke about the materials being used. Especially around material that is “broken” (what is broken anyway, who decides when something is broken), it was sometimes seen as valueless and waste, to be discarded and not thought about again.

Instead of turning this project into a consumer-blaming, finger-pointing project, I want to take the opportunity to explore if it is actually possible to go in full-salvage mode. What workflows do I need to come up with to salvage these components? Which are the most salvageable? How to recognize them? What can they be used for? And how to deal with the carcass of the printer? Is the approach a viable way of working, or only for those privileged enough where they can actually spend this much time?

When

Keeping track of time with Jeremy Bearimy

November

!No read november!

  • Start salvaging an inventory & investigate recipes
  • Continuation of the repair club at klankschool
  • Investigate static site generators for Markdown2HTML2print documentation
  • write this proposal

December

  • Contact some from the “who” list for possible workshops/DIWO events
  • Continue salvaging & documenting
  • Prepare DIWO hangouts
  • Define DIWO topics
  • Build a documentation system
  • Continuation of the repair club at klankschool

Januari

  • Contact some from the “who” list for possible workshops/DIWO events
  • Reflect on salvaged inventory and build the “Components” chapter
  • Document 2 recipes for the thesis
  • Continuation of the repair club at klankschool
  • 1st DIWO hangout at klankschool

Februari

  • Continue salvaging
  • Document 2 recipes for the thesis
  • Reflect on recipes and build the “recipes chapter”
  • Continuation of the repair club at klankschool
  • 2nd DIWO hangouts at klankschool

March

  • Continue salvaging
  • Document 2 recipes for the thesis
  • Continuation of the repair club at klankschool
  • 3rd DIWO hangouts at klankschool
  • Complete first draft thesis 14th March 2025 Deadline First Draft Thesis

April

  • Continue salvaging
  • Finalise thesis
  • Continuation of the repair club at klankschool
  • 4th DIWO hangouts at klankschool AND/OR BYOP Orchestra 18th April 2025 Deadline Thesis

May

  • Continue salvaging
  • Prepare printed version of the thesis
  • Prepare graduation show
  • Continuation of the repair club at klankschool
  • 5th DIWO hangouts at klankschool

June

What came before

During my previous studies, my graduation project was about collaborative synthesizers using web technologies. This background in web development means I am very excited about using web2print FLOSS to create a snapshot in time of a living document. In the last couple of years, I’ve shifted my focus a bit from the web as a material to (re)making with hardware. At XPUB, this resulted in turning printers into performative devices, hosting a Colloquium about making music with (salvaged) motors, and an earlier attempt to turn a printer into a battery-powered pen plotter.

File:Vitrinekast proposal project 3.mp4

Vitrinekast proposal project 1.jpeg File:Vitrinekast proposal project 2.mp4

In the first year of XPUB, I’ve become more interested in using workshops as a method of sharing and exchanging research. I’ve been part of many workshops around DIY/Circuit Bending/Synthesizer Building/Permacomputing, and found this a very enjoyable, non-hierarchical way of sharing knowledge and uncovering unknown concepts. ## Which context I want to position the research in the middle of the ideas of salvage computing[8] and DIY culture [9]. Within the DIY synth community specifically, DIY/DIWO is a common practice[10] [11], where people explore circuits together during workshops. However, these circuits often come in kits[12], featuring brand-new components and rigid instructions. To me, knowing that e-waste is such a big environmental issue, this goes against my (probably romanticized) ideas of punk in DIY culture, where you create with what is available around you[13].

But maybe (probably) my perspective on DIY culture is outdated and in need of a proper refresh.

Key texts

Dear reader! As I’ll spend a lot of time de-soldering components the coming months, I’m looking for audio references! So if you have any podcasts/radio shows/interviews/audio books/etc, please let me know!

  1. Printer Jam: Get a grip on everyday life with OSC (Gulaschprogrammiernacht 2024). See https://media.ccc.de/v/gpn22-457-printer-jam-get-a-grip-on-everyday-life-with-osc.
  2. John Richards. Speculative Sound Circuits. 2018. DOI: 10.14236/ewic/EVAC18.33
  3. ‘Salvage computing’ (no date) Salvage computing. https://damaged.bleu255.com/Salvage_Computing/ (Accessed: November 22, 2024).
  4. Klankschool is a community operating a space (and a server) in the south of Rotterdam. Its members share a common interest in performances, sound art, improvisation, noise, … Each member is a teacher, student, musician, janitor and more. The motivation to have a community-run space is to share sounds, work on projects, organise events, hang out, exhibit works, learn, teach and listen. See https://klank.school/
  5. ‘Salvage computing’ (no date) Salvage computing. https://damaged.bleu255.com/Salvage_Computing/ (Accessed: November 22, 2024).
  6. A digital shopping cart provided by Mouser Electronics, a large distributor of electronic components. See https://eu.mouser.com/Tools/ProjectCartSharing
  7. MQTT and OSC are messaging protocols. MQTT is used for small IoT devices, OSC usually for sound software/hardware. See https://en.wikipedia.org/wiki/MQTT and https://en.wikipedia.org/wiki/Open_Sound_Control
  8. ‘Salvage computing’ (no date) Salvage computing. https://damaged.bleu255.com/Salvage_Computing/ (Accessed: November 22, 2024).
  9. Critical Making (2012). California, United States of America: Telharmonium Press, Hollywood. https://conceptlab.com/criticalmaking.
  10. Richards, J. (2013) ‘Beyond DIY in electronic music,’ Organised Sound, 18(3), pp. 274–281. https://doi.org/10.1017/s1355771813000241.
  11. Collins, N. (2006) Handmade Electronic Music: the art of hardware hacking. https://openlibrary.org/books/OL29487230M/Handmade_Electronic_Music.
  12. Clacktronics – BUILD YOUR OWN MODULAR – Thonk – DIY Synthesizer Kits & Components
  13. Spencer, A. (2005) DIY: The Rise of Lo-fi Culture. Marion Boyars Publishers.