Kinetic Nodal Sequencer – KiNoSeq
I’ve been following Hans Kuder’s flexible, nodal music sequencer Tiction for a while – and while there’s not been much development recently – I think it has plenty of unrealised potential. So much so that I’ve been thinking about how to develop an original application – one inspired by Tiction – but that realises the multi-touch capabilities of the iPad.
There are other emerging nodal sequencing applications – most notably:
- Noteworks – “a piece of music composition software that re-imagines the way music is created, played, and shared… a computer software platform that reduces the learning curve for algorithmic music composition. Users create musical compositions by building networks and interacting with them in real time. The element of chance allows playback to continue for hours without looping, this material can be exported as MIDI. The noteworks team consists of Robert Alexander, Patrick Turley, and John Umbaugh.”
It’s free, beta but well developed and documented and definitely worth checking out;
- and Nodal – “a generative software application for composing music. It uses a novel method for the notation and playing of MIDI based music… based around the concept of a user-defined graph. The graph consists of nodes (musical events) and edges (connections between events). You interactively define the graph, which is then traversed by any number of voices. Nodal is developed at the Centre for Electronic Media Art (CEMA) at Monash University, Australia. Original concept: Jon McCormack. Project team: Alan Dorin, Aidan Lane, Jon McCormack and Peter McIlwain. Developed by: Aidan Lane.”
It’s up to v1.6 and available for “an introductory price of just $US30”.
It’s interesting to see these alternative approaches to nodal based music making – and there’s plenty to learn from them – but I still think that Tiction is conceptually the most intuitive, flexible and ripe for development to extend its functionality and refine its usability.
So I’ve started by listing what Tiction currently does… and asking the questions: What of this is essential? What of this is desirable? What of this would be redundant on a multi-touch interface? What of this does it do well? What of this could it do better?
Following on from this I’ve started to compile a thorough list of possible KiNoSeq functionality… and ask the questions: What of this is essential? What of this is desirable? How might this be outlined through a phased development plan?
I did actually start to work on this with a C++ programmer I met via Madlab… though sadly it hasn’t progressed and I’m still looking for other development opportunities.