Pure Data

I came across a presentation at the University of Oxford on the ‘Show Series‘ that was called “Pure Data – a musical programming show and tell”. I went expecting more about ‘data’, ‘big data’ and ‘stuff’, with a few related notes (pun intended) about music…

But was pleasantly surprised.

What is Pure Data?

“Pure Data (or Pd) is a real-time graphical programming environment for audio, video, and graphical processing. Pure Data is commonly used for live music performance, VeeJaying, sound effects, composition, audio analysis, interfacing with sensors, using cameras, controlling robots or even interacting with websites.” (from flossmanuals)

“Pure Data is a flexible and accessible programming language widely used by musicians because of its friendly “patching” interface.” (from the ‘Show Series’ description)

The talk demo-ed some entry level projects and gave an overview of how the program is used to control and make sounds. He gave an introduction of some of the objects used to create a sequence of sounds, and controllers such as oscillator, volume and digital to analogue objects. I really liked the references given and the speaker pointed us to these:

A few observations for the future (and once you learn the basics you might remember this):

  • VERY IMPORTANT: one of the first things to do is to add a volume control and set it to 0.3 (30%) otherwise you can ruin your speakers, headphones and/or ears!
  • If there are two input connections, use the right first, then the left. Left is usually dominant, and if you connect to left then right, the right might never be played/listened.
  • Best practice is to tidy the “patch”, allowing others to best understand your own drawing/code.
  • Number entries can be changed to sliders, click/right-click and select Properties to edit.
  • Sinesum allows complex sounds (any right combination of sounds with sine), so it is good to know.


Ambient Pure Data Composition:

Algorithmic Composition In Pure Data:

This last one has different ‘skins‘ and a tidy control panel, the two videos already exemplify some of the power of PD and also how complex a composition can become. I think if you understand music theory in some level you can benefit greatly, but if not, have fun just playing with the various controllers.

Another great and fun thing to do is to turn your music creations into apps, here are two references on how this can be done:

On the ‘make an app’ note, there are two versions of Pure Data to download, the “vanilla” and the “extended”. The vanilla apparently is easier to export your patch to an android app, however the extended version comes with loads of useful libraries.

You can check the screencast of the Pure Data ‘Show Series’ and maybe learn a bit more than what I listed here.

Speaking at FOWA

I work at the Bodleian Libraries on the BDLSS department for a few years now. And inquiring about the Future of Web Design (FOWD) conference in January this year, I was pleasantly surprised to be invited to speak on the Future of Web Apps (FOWA) in October. The FOWA conference has a “Rising Stars” track for people who are new to speaking but have great skills and passion to share.

It is worth saying that the FOWA team, specially Sarah Robinson, had a great impact on my speaking adventure. They made the whole experience simple to follow, always showing support and being available for any questions. On arrival, they guided me to a “speaker room” in case I need some quiet area to prepare anything before the presentation. I received a greeting card, and the simple gesture was truly appreciated.

It is quite cool to see my name on it… thank you @BathCityGirl and F.I. team for the lovely card! #fowa

A photo posted by Monica Messaggi Kaya (@monicakaya) on

There was always reassurance available in case “the nerves” kicked in. During the presentation one of the organisers also let herself to be a “point of eye-contact” in case I needed a familiar face in the audience. I found it really helpful and if I forgot a detail or two I could focus and get back on track. Another follow up was given at the end of the talk, and I felt part of a team, instead of an outsider trying to get in. I really enjoyed the experience, especially being the very first time speaking in a conference.

Since I was working on the Digital Manuscripts Toolkit (DMT) project, I thought would be great to talk about the journey and the challenges of putting this toolkit together considering the amazingly rich examples of manuscripts the Bodleian Libraries have.

I’ve spoke about the International Image Interoperability Framework (IIIF); with the aim to use, develop and repurpose digital manuscripts in interesting and innovative ways. Highlighted the steps to work with IIIF, introducing the Image API with the demo at http://iiif.io/#try-it, and Presentation API explaining about the primary resources (Manifest > Sequence > Canvas > Content) and their properties.

I carried on talking about the DMT Journey so far as the toolkit itself is a large combination of tools, and the one I was working on was the online editor. I’ve mentioned the possibility of having Docker images to create the Image server needed to satisfy one of the steps to work with IIIF. Then the IIIF metadata compliance that we’re achieving using Manifest Factory (Python); exemplified the discovery step with the Digital Mushaf project – that reunites Qur’anic manuscripts held by four institutions, and showed that we’re using a Mirador viewer instance to display and combine all these manuscripts into one sequence.

During the presentation I spoke about the research of existent tools and libraries that was done, to name a few of them: Grunt, Node.js, jQuery, Karma, underscore.js, pubsub.js, handlebars.js, URI.js, mousetrap.js, ZeroClipboard.js, d3.js, state-machine.js, tinymce.js, qTip2, sinon.js, Jasmine, Istanbul, Travis. Also demonstrated some viewers available to display and zoom images (OpenSeadragon, Mirador, UniversalViewer).

I was able to show the mockup of the online editor and a few tests that I made trying to build our first Manifest editor online.

Finishing up the presentation, I was able to talk about our funded projects that represent a direct challenge and great examples on how the scholars could use our Manifest editor online:

It was a great experience, and considering a highly technical audience, this talk was received well, and had plenty of examples and JavaScript libraries for them to discuss and possibly use. Some of the feedback received was in the lines of:

“you made some already amazing manuscripts even look more interesting”.

Slides https://slides.com/monica/digital-manuscripts-toolkit/

Code https://github.com/bodleian/dmt

Oxford Research Software Developers Network (Oxford RSDN)

On 05 May 2015 an email was circulated within the Digital Humanities at Oxford (University) calling colleagues that were working as research software (including data) developers. The idea was to keep in touch, share experiences and learn from each other; as well finding similar roles when contracts end (as University of Oxford works a lot with fixed-term contracts).

Part of the email from :

The Oxford e-Research Centre, Computer Science and the Digital Humanities are working to set up a University-wide network of “Research Software Developers” (RSDs): those who combine expertise in programming with an intricate understanding of research, and support the work of researchers in developing the (usually bespoke) software that is fundamental to so much of modern research. Many such people are employed across the University, but are not always well supported by cross-university structures. As a result they are often isolated and difficult to retain within the University. We are thus looking to connect these individuals in order to share expertise, provide appropriate advanced training, and facilitate re-employment with the University, hence optimising the use of their skills to enhance the University’s research.

A central support for the network will be a register of RSDs and their expertise, combined with a community forum and virtual employment exchange. Otherwise what the network does will be largely up to the members, but our ideas include regular meetings with talks from members or external speakers on new technologies, techniques they’ve found useful, case studies of how particular projects were tackled, and the like. We could run training sessions and hackathons to learn new tools/languages, or address common problems. There could also be research talks on relevant topics that have the potential to be transferred into RSE work.

After a short survey and a mail-list formed the first kick-off meeting happened on 8th June 2015. I’ve participate on this meeting (as a team member of the BDLSS) and below are some of my notes of the event… The people that had their names down (possibly starting it all) were:

  • Jonathan Cooper, Computer Science
  • David Robey, Oxford e-Research Centre & Digital Humanities
  • Wes Armour, Oxford e-Research Centre
  • Charles Crowther, Classics
  • Michael Davis, Bodleian Libraries

Jonathan Cooper started the discussion and presented a few ideas, based on the survey… Main focus was to get:

  • Frequency, location and time of day for regular meetings.
  • Content of the meetings, particularly for Michaelmas Term.
    • Summarise all the suggestions made through our survey.
  • Our proposal is to have short monthly meetings focused on lightning talks from members, as well as occasional longer events such as training courses or hackathons.

Create a representative body to:

  • facilitate find people and posts
  • lobby for recognition (role, pay, career)

Survey appointed these main interests:

  • sharing
  • networking
  • training
  • career development

Types of meetings we (RSDN) can do:

  • lightening talks
  • discussions
  • training courses
  • longer talks/presentations
  • hackathons
  • facilitating

In terms of content, we can focus on:

  • groups
  • services
  • material
  • courses

After a few discussions, the steps forward seemed to settle on:

  • monthly meetings (about 1-2hs)
  • lightening talks
  • discussion
  • and occasionally longer events.

A few points were made about the importance of having a profile within the network, to allow discoverability (even if you don’t have a whole CV there), but have basic information about the person and other links to your other profiles online (LinkedIn, Github accounts, etc.)

“As a group, it is easier to make a case for supporting this group in higher levels and allow hiring, collaboration, etc.”

An interest for a meeting on the summer time was raised, we’ll await more information via the mail list.

On 25/06/2015 a Slack account was created, which you can join at https://rsdn.slack.com/signup, and as long as you have a domain email listed you can participate.

The initial website for the Research Software Developers Network (Oxford RSDN) is at: http://rsdn.oerc.ox.ac.uk/