User:Kim/reading/Problems of Notation: Difference between revisions

From XPUB & Lens-Based wiki
No edit summary
Line 57: Line 57:
=== Schooltime Compositions ===
=== Schooltime Compositions ===
* '''Logo Lab''' Student program at MIT
* '''Logo Lab''' Student program at MIT
** '''LOGO''' simple programming language directing 'turtle'
** '''LOGO''' simple programming language directing 'turtle' [https://www.are.na/block/28634508 Tortoises?]
* overlaps [[#Scratch History|Scratch Orchestra]]:  
* overlaps [[#Scratch History|Scratch Orchestra]]:  
** Interest in developing collective, self-directed practical research
** Interest in developing collective, self-directed practical research
Line 73: Line 73:
** with absorbing this, notation records historical development of practices (versioning)  
** with absorbing this, notation records historical development of practices (versioning)  


=== The virtues of Practice ===
* practice over product
* '''practice''' is not solely determined by performance of the skills it comprises. Rather: activities of practice exist within a set of relations (social and historical)
** '''internal goods''' qualities that enable practice to flourish
** '''external goods''' what it produces (might become property to non-practitioners)
** '''virtues''' internal goods, in contrast to ethics are not defined and realised by law, but by action and are not static but evolving with situation
** '''vices'''


 
* free software (4 principles or virtues)
[https://dspace.mit.edu/bitstream/handle/1721.1/6086/AIM-239.pdf HAKMEM]
** 4. freedom connects internal good of hacking to external good of distribution
[https://www.are.na/block/28634508 Tortoises?]
* open source (19 rules - not ethics but management model)
* Open Source vs Free Software:
** both: models of collaborate production
** free software is distributive model
** open source: acquisitive model of collaboration

Revision as of 20:18, 15 September 2024

All Problems of Notation Will be Solved by the Masses: Free Open Form Performance, Free/Libre Open Source Software, and Distributive Practice

Simon Yuill

  • recent valorization of 'collaboration' omits basic condition of collaboration - that all forms of production ultimately rely on various degrees and arrangements
  • 'collaboration' becomes commodified (art, consumer as worker)
  • can FLOSS (Free/Libre Open Source Software) counteract?
  • problems with FLOSS:
    • issue of collaboration and legislation (and how these relate to medium code)
    • FLOSS emerging cultural practices fail to relate to outside (non-FLOSS art/ culture)
      • these practices are not collaborative but distributive
  • article outlines relation between notational production and distributive practice

Livecoding

  • embodies FLOSS key principles (code - algorithms - music)
  1. continual re-writing of code as primary mode of artistic production
  2. presentation of the work as open ended, mutable rather than static artefact

Livecoding Aesthetics

  • production is 'live' and living
  • workshops / pedagogic aspect important

Hacklabs + Hackmeets

  • First Hacklabs developed in Europe - emerging from squatting movements
  • FLOSS + Hacklabs share principle of 'enabling the possibility of production by others'

collaborative practice brings together production of many under single goal (directing disposition of every individuals labour)
distributive practice enables disposition of labour by others (under their own direction)

  • is facilitated in the output of production as notation/ code
  • not only creating product but letting it become an active being beyond initial implementation

Notational production

  • is not unique to software
  • in lifecoding: specificity of code is opened towards indeterminism of improvisation
  • echoes music period of 'free playing' Jazz + avant-garde compositional systems
    • 'free play' instead of improvisation (see Black Notational Production)

Scratch History

  • emerged from public classes (workers education centre) in experimental music in UK, late 1960s
  • Scratch music pieces were active experimentation with different notational forms (graphic, musical, collage...)
  • all notations from Scratch Orchestra were freely distributable
  • encouraged to not only copy but use, add and modify scores

Noise Interrupts

  • Scratch Orchestra Nature Study Notes set up small scale operating systems
    • organizational structures enabling other works to be produced within them
    • performance as an operating system
  • In conventional computers interrupt mechanism enables signals from peripheral devices (keyboard, mouse) to enter operating system
    • when interrupt signal is received - computer selects response action
    • response chosen by matching identifier code for each signal (pre programmed routines aka 'interrupt handlers')
  • interrupt creates vector between internal operation, notational operation and contingency of outside (physical) world
  • interrupts break linear, internally operating Turing Machine
  • in Linux release 'interrupts aren't hidden'
  • with this possibility of errors occurs
    • treating error as positive, productive opportunity
  • noise as any material that is not recognized by an existing system and is therefore opposed to information

Schooltime Compositions

  • Logo Lab Student program at MIT
    • LOGO simple programming language directing 'turtle' Tortoises?
  • overlaps Scratch Orchestra:
    • Interest in developing collective, self-directed practical research
      • through self developed notational systems, 'improvisational' activities
    • criticism of institutionalized conservatism (although more or less dependent on)
      • breaking student - tutor hierarchies, learning as self-directed production
    • attitude to (encourage) error

Training in Contingency

  • LOGO students 'improvise' with their code, responding and adjusting to turtles performance (similar to coding-performing feedback loop of livecoding)
  • Computer and programming languages are more constrained in their interpretation of notation than humans (= danger and opportunity)
  • feedback loops
    • unexpected errors of the past become future possibilities
    • with absorbing this, notation records historical development of practices (versioning)

The virtues of Practice

  • practice over product
  • practice is not solely determined by performance of the skills it comprises. Rather: activities of practice exist within a set of relations (social and historical)
    • internal goods qualities that enable practice to flourish
    • external goods what it produces (might become property to non-practitioners)
    • virtues internal goods, in contrast to ethics are not defined and realised by law, but by action and are not static but evolving with situation
    • vices
  • free software (4 principles or virtues)
    • 4. freedom connects internal good of hacking to external good of distribution
  • open source (19 rules - not ethics but management model)
  • Open Source vs Free Software:
    • both: models of collaborate production
    • free software is distributive model
    • open source: acquisitive model of collaboration