

Operations applicable only to multiple events:ģ.2 Real-time and Sequential Access Operations

Operations on note events that can and have to happen independently of transport state / playback: Note events can be manipulated in a number ways depending on selection and the mode of access. The existing open-source audio/MIDI sequencers are all no match for Ardour’s audio capabilities and none of them has on-canvas MIDI editing, so there’s a gap to fill. Another is avoidingĪdditional windows the user has to deal with. This is also an argument for on-canvas MIDI editing. Being able to edit one part while seeing how it relates to another is fundamental. In such a case, having 2 time-lines in 2 separate windows and applications that need to be synced It’s common in modern music production to combine audio like drum-loops with MIDI sequenced lines. They are concerned about added complexity, the required development effort and either don’t need MIDI themselves or think it can be Some people stated a preference for Ardour staying audio-only.
#Ardour audio midi how to
The central question is how to make the operations necessary to edit note events available in the most usable way. For now I will address editing of note events, exploring the problem and solutions Regarding interaction and interface design, graphical editing of MIDI is the most interesting and crucial aspect. He prepared the infrastructure in a GSoC 2006
#Ardour audio midi code

Dry stuff I know, but even if no one bothers to read it, it helped me to organize my thoughts 😉
