Google Summer of Code 2007

We've applied to be accepted been accepted into the Google Summer of Code for 2007. Last year we had several great projects, a great time and both got some work done and brought some new developers onto the team. Let's repeat that this year! So, my own personal ideas for projects are:
  • Scripting & Batch command support
  • Extend current OSC command set
  • Graph-based connection UI
  • MIDI interface (perhaps on top of the midi support from last year's GSoC?? perhaps!)
  • Beat detection (using aubio and/or VAMP plugins)
  • use Bias2OMF source code on to support OMF data handling
  • work out how to support AudioUnit plugin GUIs on OS X
  • Polish up SeX (Session Exchange) python app
  • MIDI interface/port selection dialog & infrastructure
  • Multichannel 3d Panning: algorithm(s) and GUI
  • Video tracks
Suggest more ideas in the comments. If you're a site editor, feel free to edit my list. If you're a student, start thinking about possible projects and your own application.

This is off-topic and I

This is off-topic and I apologise, but I want to reply to the note about Rosegarden.

I don't know whether you've tried RG 1.5.0/1.5.1, but the matrix editor has seen some improvement since earlier releases.

You can move, quick-copy and adjust durations of one or more notes at once by dragging on the body of the note, the body of the note with Ctrl pressed, or the right edge of the note, respectively, with the select tool. e.g. drag-select a bunch of notes then Ctrl-click-drag to copy them to a new location.

You can add new notes even when using the select tool, by dragging with the middle button pressed (admittedly not as handy as it used to be, now most middle mouse buttons are wheels), and you can switch between the draw and select tools using F2 and F3 keys. (The last two features were always there, but perhaps not everyone knows about them.)

The matrix also now has a better memory for the last grid and zoom settings you used for a segment, and has context help for mouse operations.

FWIW I'm one of those who thinks better interoperation with existing sequencers would be more effective than having complete MIDI editing in Ardour itself. That's not just for the obvious reason that I work on one of those existing sequencers, but because, having worked on one of them for a while, I'm all too aware that doing note-based editing well is a bottomless pit for developer time, just as audio recording is.


The content of this message

The content of this message was deleted because it failed to display even a minimum level of politeness. This forum is not a venue for rants about any software, least of all software that isn't Ardour. If anyone has anything they would like to say regarding Rosegarden, please do so on their mailing lists and other support venues.

Let’s keep this friendly,

Let's keep this friendly, okay? Rosegarden is valuable software and the Ardour developers appreciate its developer's contributions to the community.

Yes, I do understand what

Yes, I do understand what you're saying about Rosegarden. There should definitely be better interoperation between Ardour and sequencers.
But I think built-in would also be good. It gives
people a choice and some people like to do everything in one program.

For example, looks at how you could do everything in Ableton Live if you wanted to or ,if you felt like it, you could do all the editing and mixing in ProTools.

I think it's a given that they should work on a built-in editor. In fact, I'd say it's the number one requested feature now.

What I would like to see, in

What I would like to see, in conjunction with MIDI recording and editing, and maybe 'instrument' support using DSSI and/or LV2, is a patch choosing dialog with a searchable patch list generalizing over all patches for all MIDI instruments known to the system. I don't know if this is too early given that MIDI in ardour is still in an early phase, but here it goes anyway.

Basically, what it would do, if possible, is to collect patch information from softsynths (if possible) and use instrument definition files (there are already plenty of those in rosegarden and MusE syntax), to create a list of patch names, abstract from the type of device it applies to. When a patch is selected, the corresponding synth settings are applied to the MIDI track in question, and then that track would talk to the device that 'owns' the patch. The list would be searchable (thus searching for "piano" will bring up _all_ piano sounds), and would instantly update the patch information to the track, so that the sound of the currently selected patch in the list can be tested without needing to close the dialog.

It would also be possible to use other panes in the dialog to choose patches by device.

I think this would be very user friendly, by abstracting away the underlying technologies. Is this something that people would like to see? Is it even possible?

My idea for several years

My idea for several years now is a Playalong utility, something like band in a box, but capable of own ideas (variations), like communication and interaction with the a.i. There'd be an interface which let's you select style, chords, tune, rhythm, bass line or even arangements and so on. It'd be pretty midi based. And the final version should be capable of imitating a whole jazz trio or something like that. A future version should be able of interacting with the user via midi instruments. Can anybody tell me if a project like this is appreciated in ardour, for I'd like to do it this summer and GSoC would just be the best way to get it done.

Midi Editing /

Midi Editing / interoperation with something like rosegarden is exactly what I need, too, in Ardour.

I often work with midi-tracks (midi-guitars, bass etc.) to record audio upon that. Rosegarden has no big audio editing functions, Ardour no midi (at the moment).

A interoperation between them, e.g. synchronized start and tempo-tracks would be cool, a complete new midi interface in ArdourX even cooler!


If you’re serious about

If you're serious about it, write an application and submit it.

I would, but I have no

I would, but I have no progamming skills. (Well, once I tried Delphi, haha...)


A tempo track would be nice

A tempo track would be nice too. like when you press ctrl+t (or alt+t, i forgot) in cubase, you get a 2 dimensional board (tempo vs time) where you can "draw" the tempo, using straight lines, fade-in/out's,...

Dieterbe: Yeah, that’s

Dieterbe: Yeah, that's pretty much what I had in mind. Just three different areas that each have a function. Each part does get smaller as the note shrinks, but I figured it wouldn't be a problem as long as the view of the notes can be stretched horizontally to one's liking. It's weird seeing midi programs without this, but I guess I was just spoiled by Sonar.

Also, in NO way was I trying to dis Rosegarden, I use their product and it's definitely solid (and the product of an amazing amount of work). I know that they have mouse controls of the sort that cannam reported, but I much prefer only needing to use the mouse to put things down, over ctrl-clicking. Just personal preference.

one thing that i think

one thing that i think people overlook (or maybe this does exist and i'm oblivious to it) is that xjadeo can not show a 'filmstrip' type view of the video along with the audio tracks. yes, you can use it to playback and see how things sync up, but you can't get the big picture: "see that scene starting there with the explosions? look at the changes in sound there."

I really appreciate the

I really appreciate the possibility of seeing OMF implemented. It is crucial for doing audio-to-picture editing.

My chosen tool for video editing is made by Avid. And I happened to stumble across the Ardour pages while doing some research.

OMF import done right will make Ardour stand out from the croud and attract people from the video business.

AAF will be the next logical step as well as MXF. AAF builds on the foundation done by OMF, but has a much wider support. MXF is a subset of AAF. For anyone not familiar with these three letter words, AAF is designed to move whole projects ( "timelines" ) from one application to another, with or without the actual mediafiles embedded. MXF is a subset meant for aquisition or playout - e.g. no "timeline" information. This is just a simplified explanation. There are possibilities to mix these standards in such a way it it becomes a real mess to explain :-) Both AAF and MXF have their own websites with a lot of explanation.

I have not been able to find out what video formats Ardour support for playalong. The videoformat should support wievable picture during scrubbing and frame by frame advancing without becoming pixelated.

Another idea to look at would be to get Ardour into the Ubuntu repository so installation can be done with no hassle at all. That is probably easier than making a special distro with Ardour included.

I am going to try to install Ardour on Ubuntu Desktop running under WMWare. Hope I can make it work for poking around in the system.



-latency compensation for

-latency compensation for send-returns.
At the moment latency is compensated for by sliding the track, but that doesn't work correctly when you have a send originating after plugins or external inserts.

-"ping" feature to measure and compensate the latency of external units or plugins that don't report it.

-A more intelligent solo function that looks at the routing.

-A combination of FFT view and object based editing would allow you to use a lasso tool to select any sound and apply effects, cut/copy/paste etc, just to that area.
(as discussed elseware VAMP could be used to implement the FFT and visualisation, but Clam also looks promising, see


-folder tracks

-ability to set pan law per channel.

Nyquist Support Speaking of

Nyquist Support

Speaking of Audacity and VST Enabler, how about support for Nyquist(the LISP-like audio processing language that works with Audacity).

For a description, go here:

for the “ping” feature,

for the "ping" feature, jdelay already exists.

this is linux - we don't reimplement cool tools just to make user's lives easier. or do we? :)

parts of the automation need

parts of the automation need an overhaul.
editing is not so nice.

a midi editor is a nice thing.
we need to take a look at how different an
audio stream and a midi stream are.

an osc data stream is also missing.


can velocity be expressed

can velocity be expressed with alpha color ?.

then a stream splitter could split midi-streams into

CC (control automation) -> (view/editable with AutomationTimeAxisView)

NOTES (contain velocity) -> (view has to be coded)


I’d like to see a

I'd like to see a cup-holder and a rear-view mirror, but that's just me.

I know this is late for this

I know this is late for this summer, but I'd love to see a way of categorizing plugins. It's a huge PITA to scroll through a bunch of plugins I'll never use to get to the 20 or so I use regularly.

Some sort of folder view would be nice. The ability to the same plugin in multiple folders would help as well. You could have a "guitar" folder, "bass", "drums", etc, as well as having separate folders for the plugin authors.

try autotalent for pitch

try autotalent for pitch correction.
I made a ubuntu package for it too. See: