This is a short video taken by one of the artists involved in the Aftershock Project in Manchester earlier this year. In it, some musicians are composing a song together. A week earlier, most of them had never met. A week later, they had performed that song together on stage in front of a packed audience, and returned to their homes in England, France and Italy.
By itself, the video is fairly unremarkable, though it does give a brief insight into the creative process, which normally would be hidden from an audience. Musicians traditionally tend to like presenting finished things.
But what it represents in terms of a methodology, a process and a way of ‘making internet’ with respect to music (and musicking) is something that really interests me – and has formed the basis for much of my academic work over the past year or so.
Because what’s interesting is not the video itself, but the way in which that video potentially links to other, related videos from within the same context – and makes connections from which narrative meaning can be constructed.
Call it associative vernacular mediation.
In other words, just as you can build something unique with a set of Lego bricks, you can create a multi-perspective story using these rough-and-ready vernacular video clips.
If you missed it, I’ve spent the last 10 days in Manchester as part of Nitin Sawhney’s Aftershock Project.
Aftershock has been going for about 10 years now, and I’ve been involved in the last three events, which were supported by the European Cultural Foundation. The first was in Genoa, Italy in June last year. The second was in Marseille, France in September – and this one brought together some of the musicians from the first two for a final event in Manchester.
My own involvement in the project is a little bit weird and complicated, so I thought I should explain that a little.
Day 8 of 10 in Manchester for the Aftershock Project. It’s pretty full on and everyone’s pretty tired – but we have a final set list, and the musicians pretty much know what they’re doing across the board now. Best of all, the gig is sold out.
So now it’s just a matter of them rehearsing until it’s really tight, and for me to start to make a note of some of the things I’ve learned along the way in doing this project and putting it all online.
The stats are interesting, if you like that sort of thing. A slow growth curve but really starting to pick up. The interpersonal dynamics have been really interesting, as well as the different responses to the technology.
I’ve got a few more interviews up on the site now. Tomorrow I want to try a couple of different approaches. Perhaps even film and upload a whole runthrough. We’ll see.
I’m also going to try and get out of the venue a bit tomorrow and take photos of something other than musicians.
Today the Aftershock musicians were given a task that involved them going out into the city and collecting sounds to inspire and incorporate into a new song.
Above (L-R) are Marika the percussionist, Roberto the singer, Eoghan (pronounced ‘Owen’) the drummer, Denis the guitarist, singer and electronic noisemaker, and Nick the bass player.
I went with them and documented some of that. Here’s a video:
Relaxing on the couch while David finishes the album
Sitting in an apartment in Manchester, while my roommate David puts the finishing touches on his band’s album before it gets sent off to New York to be mastered tomorrow. Really lovely way to spend an evening (for me at least – David’s stressing a bit…).
I'm an author of books about technology, culture, music and radio. I'm also an award-winning broadcaster and filmmaker, a public speaker and lecturer, record producer and festival director. I am closely following developments in emerging technologies and the cultures and ethics surrounding them, and my projects typically focus on issues of justice, inclusion, and sustainability.
Most of my work involves surrounding myself with incredibly smart and talented people who would have no other reason to ever be in the same room as each other. That's when amazing things happen.
I tend to talk a lot about music (often jazz-adjacent and particularly on vinyl, but also playlists and mixtapes). I'm enthusiastic about food and cooking, the intersection of art and science, new technologies, vintage technologies, education, social progress, silence, innovation, narrative, data commons, culture, sound art and the spoken word. This blog will continue to reflect those diverse and shifting enthusiasms. I may also digress.
I'm from Tāmaki Makaurau / Auckland in Aotearoa New Zealand, I have Scottish ancestry, I've spent a decade in the south of Birmingham UK, and another in a forest in the north of Sweden.
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
__utma
ID used to identify users and sessions
2 years after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_ga
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked
30 seconds
_ga_
ID used to identify users
2 years
_gid
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager