Thursday, April 18, 2019

Life in the Adhocscape


Shared Resources and Media Art Production in Manila

L’essentiel est invisible pour les yeux.
                                 Antoine de Saint-Exupery

In a country where institutional support is rudimentary and scarce and where media art is still unfamiliar and very new, the production of media art faces more difficulties than marketable artifacts such as paintings and objects.

For the purposes of this essay we will define ‘media art’ as works involving film, sound, video, and machines and/or made with cameras; sound and video recorders; and computers. There is no deliberate ideological rationale behind this definition, only the brute fact that my own artistic interests and practices revolve around these things, which have in turn determined the circles I move in and the artists I meet, know and talk to. However, it should be noted that the same difficulties surround many minority art genres, particularly any with a large performance element.

In the Philippines, media art is still a relatively minor and unfamiliar tradition, whose products currently face microscopic or nonexistent markets and an absence of friendly exhibition spaces. However, its practice often requires specialized and sometimes expensive equipment and specialized knowledge. Such impediments appear to have engendered three major consequences:

1) a media art scene that is primarily centered around performances and screenings in ad hoc or popup events
2) the sharing of knowledge and resources by its practitioners
3) the creation of informal, ad hoc arrangements that facilitate production


Interviews and discussions with fellow media artists clarified three characteristics of the solutions/adaptations that have emerged in response to the factors of outlined above. The first is:

·      Almost all “shared resources”, whether in the form of space, material, service, or equipment, are owned by a single person who shares the resource out to a selected number of people.

As a result, all those who make use of the resource always have the status of either friend, guest, or some nested variation such as friend of a guest of a friend and so on. There currently are no arrangements of the type that underly the so-called ‘hacker spaces’ popular in more prosperous countries, which are owned and maintained communally by a group of peers. In the case of nearly every resource, it is always owned or administered by a patron -- very often an artist himself--- who possesses and administers the resource by virtue of a) being richer/more successful, b) belonging to a prosperous family or c) being attached to a richer person. Thus sculptor and sound artist Lirio Salvador was the sole signatory of the lease of the gallery and event space known as Espasyo Siningdikato, and did not collect contributions towards its expenses. In the same vein, Terminal Garden, a space which hosted residencies, concerts, performances, and workshops, was the family residence of its director Tengal Drilon. The gallery/event space/studio known as Green Papaya is owned and financed solely by the visual artist Norberto “Peewee” Roldan. The furniture fabrication company Bespoke occasionally manufactures objects for artists, but only and solely at the discretion of its director Jeremy Guiab.

It is worth relating that Tsinelas Labs attempted to transplant the communally-run hackerspace structure to Manila. It closed in less than six months as a result of a lack of subscribers. On the other hand, the Philrobotics Philippine Electronics and Robotics Enthusiasts Club was founded in 2010 and is still going strong as a consequence of being able to use a room rent-free in the offices of E-gizmo, an electronics parts store specializing in sensors, microcontrollers, and industrial automation components, whose owner is a founding member of the club.

The second characteristic is:

·      Physical spaces are constantly in flux.

Spaces are constantly being started, ended, opened, closed, initiated and abandoned. As of this writing, the aforementioned Terminal Garden closed in December of 2015, when the house was turned over to new owners. By the same token, the painters/sound artists Pow Martinez and Manny Megrino built/are building home-recording studios in their residences that they plan to open to friends and collaborators. The art collective WALA (Windang Aesthetics Labor Army, whose acronym means “Nothing” and whose practice centers on public interventions with a heavy media art/performance aspect) effectively spent a four-month residency in 2015 at an abandoned horse stable that the UP Diliman made available for their use. This residency that ended when the stables’ electrical supply was cut off. Because the art made at these spaces currently generates next to no income, these spaces are always dependent on the existence of a disposable surplus. As these surpluses are always in danger of drying up or being channeled to more profitable ends, (the more so if they are formally owned collectively, as for instance by the patron’s family) artists’ access to these spaces is often short-lived.

Finally:

·               Cooperation and sharing is based less on physical locations, formal membership and communal ownership than on networks of personal relationships that facilitate arrangements -- ad hoc, temporary, informal, and improvised -- that determine how surpluses are deployed, exceptions made, and fees reduced or even eliminated.

Some detail regarding WALA’s practices may go some way in illuminating this particular notion. It is a difficulty specific to improvised arrangements that they can appear as trivial or inessential, even to those who make and depend on these arrangements. Certainly my own practice, and that of my band/noise collective The Children of  Cathode Ray --riddled as they are with such jerry-rigged transactions, did not prevent me from initially characterizing the current landscape as “experiencing a drought in shared spaces” until the curator Merv Espina suggested to me that in the Philippine context, physical spaces might be a secondary consideration –one among many resources generated by social relationships. I understand that shifting the focus from physical spaces to social arrangements complicates the conversation. However, if art relies primarily on these arrangements in order to exist and function, then these arrangements, however archipelagic, multifarious, changeable, tangled and hard-to-talk-aboutable, -- these arrangements have to be acknowledged as the primary and essential infrastructure. The discourse must adapt to reality.

WALA is a loose collective of some eight core members, who wish not to be named  as they consider the collective to be the primary artistic entity. As has been noted, they focus primarily on public actions/interventions, though this focus generates a variety of media and objects, including videos, zines, musical/noise instruments and sound recordings. In terms of where they operate, they work and meet primarily at 3 locations:

1)   In Green Papaya in Quezon City, where two of the members –a couple-- live as formally employed assistants of the visual artist Norberto Roldan. The two members live in the upper floor, which also serves as their studio.

2)   In a house in Mandaluyong that functions as the offices and storage rooms of Avante Garde Greeting Cards, where another of WALA’s core group  —a friend of the company’s owner—lives. The offices are equipped with a rather gorgeous copier/scanner/color printer, which WALA is suffered to use.

3)   In an abandoned horse stable -- still open to the elements – on the grounds of the University of the Philippines in Quezon City. The stable was given over to the use of artists as part of the Project Bakawan Art Festival in February of 2015. WALA used the space as meeting room and gallery and staged sound/media performances there until electrical power became unavailable in late May of the same year. It is interesting to note that they effectively shared the space with JKS -- a fraternity/gang based in a nearby village that had co-opted the abandoned stables before UP management invited WALA to use the stables during an art festival -- whose members still maintained a proprietary view of the premises.

These details illustrate that the group’s practice relies heavily on resources that they have access to by virtue of personal relationships.  This access often becomes another resource that they in turn share out to their friends, such as to the Cavite-based sound artist Erick Calilan, who stores sound equipment in the living quarters of the Green Papaya contingent of WALA.

These details suggest that in Manila (and possibly in the Philippines) it might be more appropriate to frame the notion of ‘production space’  in terms of a space of production opportunities, rather than in terms of physical real estate. In spite of the word “real” of “real estate” pre-loading the notion of physical space with primary significance, I would argue that a serious investigation of how art is actually produced cannot presuppose that it knows what it is looking for, lest it run the danger of discounting something essential just because it does not accord with one’s prejudices. Sometimes the essential is invisible to the eye; and I believe that the more abstract and dynamic notion of socially-generated “opportunity space” must be considered as the primary and enabling space in which equipment and resources are shared by Manila’s media artists.

-END-


Note: A SLIGHTLY shorter version of this article was previously published in a.m. post, issue 115 

Thursday, March 28, 2019

OSCgroups Tutorial


I wrote this because I couldn't find an OSCgroups for Dummies tutorial.

OSC stands for Open Sound Control, a communication protocol that functions like MIDI. It's a protocol that allows computers to communicate with one another. It is much more powerful than MIDI, but at the same time it can be a bit clumsy to use, as it operates over computer networks (rather than dedicated hardware, as MIDI does) and so requires that that the the IP address and port number of the receiver be specified in order for an OSC message to be successfully transmitted. As you can imagined, this can easily become be a fiddly and tedious requirement.

OSCgroups is a data distribution program that simplifies matters by enabling group members to send OSC messages to every other member without knowing or specifying each member's IP address. Group members simply register with a central server, which handles the task of forwarding all OSC messages received to all registered computers. OSCgroups consists of two independent files: a server executable, and a client executable. They are tiny programs that are run from the command line in a Terminal window. This is a very economical form of programming, but not a very intuitive one, which is why beginners can use some tips when getting started. Unfortunately, the files do not come bundled with instructions, which is why something like this tutorial may come in handy to newbies. Interested parties may download the files from here: 


and here:


I should mention here that I am not going to go into detail about OSC. OSCgroups is basically a program for people who are already familiar with and use OSC, and who are looking for ways to streamline their communication routines.

The way this all works is that the OSCgroups client program is run on each of the participating computers. OSC capable software (such as Pure Data, MAX/MSP, and Resolume, to name only a few) running on such a member computer sends its OSC messages to this client program, which passes the messages to a third computer, a central server. It is this server which ensures that all member computers receive copies of every message it receives. (See graphic below)

So basically in order to join a group, a computer needs little more than the group name and the group password. It is not clear to me why a member needs a personal password, but OSCgroups requires each member to make one.




ALL PARTICIPATING COMPUTERS:

1)    Put the two files OscGroupServer and OscGroupClient in a convenient folder (e.g. on the Desktop, in Documents, etc.)  A convenient folder is one that  can be reached without too many cd operations from the Terminal.

2)    Log all computers onto a common network. This network can be a LAN or a wifi network. The network needn’t be connected to the Internet. On the other hand, the network can be the internet itself. People have used OSCgroups to perform and collaborate while physically being in different countries.

SERVER:
One can use dedicated OSCgroups servers on the internet (see below), but I favor running my own server over a small, private network isolated from the internet.

Paranoia says it would be best to run the server on a separate and dedicated computer, but it IS possible (and, my friend and resource person Chris B assures me, "normal") to run it together with a client on a single computer.

Computers communicate with each other through things called ports. Ports are essentially numbered data addresses in the computer where data is exchanged. When doubleclicked, the OscGroupsServer program grabs port number 22242 for its use. This is good enough for me, but if you want to use a different port, you can specify it (along with other items) by running the program from a Terminal window. Type ./OscGroupServer -h to learn about the other items/specifications.

NOTE: When clients log onto the server, it is possible that the server computer will have to manually be told to accept the connections.

CLIENT:

The Client program is the file named OscGroupsClient. To run it, you will have to know the IP address of the server. On a Mac, this is done by clicking on the Wifi icon and then clicking Open Network Preferences on the menu. On Windows, it's easiest to type

ipconfig /all

in a Terminal Window. Terminal is a programming window usually found in the Accessories folder of the Start Menu.

NOTE: the IP address 127.0.0.1 is a special address that basically means "this computer". The word "localhost" means the same thing and can sometimes be used in place of "127.0.0.1"  Both terms are used when passing OSC messages within a single computer. 

OscGroupClient cannot be run by being double-clicked, as it requires several arguments to be specified in order to run properly.
OscGroupClient must be run, and the arguments specified, from a terminal window.

Mac: Open a Terminal window, cd to the folder where the OscGroupClient file is located. run the OscGroupClient file by typing
a command like the following:

./oscgroupclient 192.168.1.101 22242 22243 22244 22245 john abcd beatles wxyz

The ./ identifies the sentence as an executable command.
The arguments following oscgroupclient refer to the following values. 

oscgroupclient serveraddress serverport localtoremoteport localtxport localrxport username password groupname grouppassword

If the Mac insists the file is damaged, Go to System Preferences>Security & Privacy>General, and unlock the lock icon in the lower left corner. Give the Mac permission to run files from “Anywhere”, and lock the icon again.

Windows: Open a Terminal window, cd to the folder where the files are located. Run the OscGroupClient file by typing a command like the following:

oscgroupclient 192.168.1.101 22242 22243 22244 22245 john abcd beatles wxyz

The arguments following “oscgroupclient" refer to the following items: 

oscgroupclient serveraddress serverport localtoremoteport localtxport localrxport username password groupname grouppassword

When clients log onto servers, it is possible that the server computer will have to manually be told to accept the connections.

You can test that the client file is working by logging onto a server on the internet, e.g. oscgroups.kiben.net or oscgroups.iua.upf.edu

Sample command: 
oscgroupclient oscgroups.kiben.net 22242 22243 22244 22245 john abcd beatles wxyz



PURE DATA, PROCESSING, RESOLUME, ETC

Configure the software to route messages to and from the local txport and local rxport allocated to the client.
See below for an example in puredata.

click to see full image


If multiple users are behind the same NAT and you experience difficulties. you
might like to try all using a different value for localtoremoteport
for each user, although this shouldn't usually be necessary.