Difference between revisions of "GSoC Ideas 2008"

From Audacity Wiki
Jump to: navigation, search
(dunno how to link to make a category a link yet.)
(Category link as requested ; one typo ; isn't letting crawlers see the email address a bad idea- you can always right click and copy to clipboard?)
Line 1: Line 1:
 
The Audacity Developer Team weren't part of Google Summer of Code 2007 but we want to be in 2008.  We were watching what happened in 2007 closely.
 
The Audacity Developer Team weren't part of Google Summer of Code 2007 but we want to be in 2008.  We were watching what happened in 2007 closely.
  
http://code.google.com/summerofcode.html
+
{{external|http://code.google.com/summerofcode.html}}
  
Please help us to get ready for the next round.  It is never too early.  Your ideas and enthusiasm will help us make it happen next year.  You can contact us at this email address: [mailto:[email protected] [email protected]].   
+
Please help us to get ready for the next round.  It is never too early.  Your ideas and enthusiasm will help us make it happen next year.  You can contact us at {{external|[mailto:[email protected] this email address]}}.   
  
 
We're also keen to [[Connected Open Source|promote links between projects]] that can benefit Audacity.  In 2007 wxWidgets participated in GSoC 2007 and so did Xiph.org.  We use code from both.  Indirectly work on those projects may benefit Audacity.  If you have ideas for a project of that kind that you would like to do, we'd be keen to hear from you and discuss it with you, at the address above.
 
We're also keen to [[Connected Open Source|promote links between projects]] that can benefit Audacity.  In 2007 wxWidgets participated in GSoC 2007 and so did Xiph.org.  We use code from both.  Indirectly work on those projects may benefit Audacity.  If you have ideas for a project of that kind that you would like to do, we'd be keen to hear from you and discuss it with you, at the address above.
Line 12: Line 12:
 
Other pages related to GSoC 2008 are:
 
Other pages related to GSoC 2008 are:
  
* All pages in [ [Category:GSoC] ].  (link at bottom of page).
+
* All pages in [[:Category:GSoC]].  
 
* [[Potential GSoC Students]].  If you are a student who would be interested in participating in GSoC 2008 with Audacity, please put your name and the institution you are at on this page.  This is so that we can show Google the level of interest that we already have, to encourage Google to give us mentor status in 2008.
 
* [[Potential GSoC Students]].  If you are a student who would be interested in participating in GSoC 2008 with Audacity, please put your name and the institution you are at on this page.  This is so that we can show Google the level of interest that we already have, to encourage Google to give us mentor status in 2008.
  
Line 64: Line 64:
  
 
'''Description:'''
 
'''Description:'''
Postifsh is a p-threads based Linux audio application with uncompromising quality and some unique effects such as 'deverb' which removes unwanted reverb from a track.  Currently it can't be used from within Audacity.
+
Postfish is a p-threads based Linux audio application with uncompromising quality and some unique effects such as 'deverb' which removes unwanted reverb from a track.  Currently it can't be used from within Audacity.
  
 
Integrating it into Audacity will be a challenge indeed, particularly on the windows side where we anticipate problems with a simple translation to wxThreads.  The student will need to be prepared to dive into such code.
 
Integrating it into Audacity will be a challenge indeed, particularly on the windows side where we anticipate problems with a simple translation to wxThreads.  The student will need to be prepared to dive into such code.
Line 88: Line 88:
 
One of the most common operations people want to do when mixing audio is to smoothly transition between two sound clips.  This is commonly called a cross-fade.  This operation is technically possible in Audacity now, but it is very clunky, requiring multiple steps and no editability short of undoing the actions and starting again.  We are looking for someone to implement a clean, intuitive, nondestructive cross-fade for Audacity.  Audacity already has all of the infrastructure necessary to support implementing this operation nondestructively and we already have a clear plan for how it should work.  The following webpage has a mockup of what we think the GUI might look like:
 
One of the most common operations people want to do when mixing audio is to smoothly transition between two sound clips.  This is commonly called a cross-fade.  This operation is technically possible in Audacity now, but it is very clunky, requiring multiple steps and no editability short of undoing the actions and starting again.  We are looking for someone to implement a clean, intuitive, nondestructive cross-fade for Audacity.  Audacity already has all of the infrastructure necessary to support implementing this operation nondestructively and we already have a clear plan for how it should work.  The following webpage has a mockup of what we think the GUI might look like:
  
http://limpet.net/mbrubeck/temp/cross-fade/
+
{{external|http://limpet.net/mbrubeck/temp/cross-fade/}}
  
 
This feature, while seemingly small, would represent a huge boost in usability for Audacity.  This feature is intimately related to several other UI enhancements that we have proposed: for example, one element of this proposed GUI is that clips "stick" to each other or "snap" into place when you push them together.  Such a snap-to behavior would be great in several other circumstances, for example having a track stick to t=0, or to a point that lines up with another track.
 
This feature, while seemingly small, would represent a huge boost in usability for Audacity.  This feature is intimately related to several other UI enhancements that we have proposed: for example, one element of this proposed GUI is that clips "stick" to each other or "snap" into place when you push them together.  Such a snap-to behavior would be great in several other circumstances, for example having a track stick to t=0, or to a point that lines up with another track.

Revision as of 06:14, 4 October 2007

The Audacity Developer Team weren't part of Google Summer of Code 2007 but we want to be in 2008. We were watching what happened in 2007 closely.

http://code.google.com/summerofcode.html 

Please help us to get ready for the next round. It is never too early. Your ideas and enthusiasm will help us make it happen next year. You can contact us at this email address .

We're also keen to promote links between projects that can benefit Audacity. In 2007 wxWidgets participated in GSoC 2007 and so did Xiph.org. We use code from both. Indirectly work on those projects may benefit Audacity. If you have ideas for a project of that kind that you would like to do, we'd be keen to hear from you and discuss it with you, at the address above.

This page is mainly for Ideas for projects.


Other pages related to GSoC 2008 are:

  • All pages in Category:GSoC.
  • Potential GSoC Students. If you are a student who would be interested in participating in GSoC 2008 with Audacity, please put your name and the institution you are at on this page. This is so that we can show Google the level of interest that we already have, to encourage Google to give us mentor status in 2008.


Ideas

Below is a list of potential projects, but feel free to suggest your own ideas as well. It would be best to write the first version on More GSoC Ideas. When the idea is well defined and mentors have been found, it may get moved to this page.

A there are literally hundreds of user-contributed feature suggestions on the Feature Requests page. A good project proposal could combine a number of these suggestions into one proposal.


Possible Mentors These are, in order, the most likely or best mentors for this project idea.
Skills For nearly all project ideas, wxWidgets and C++ programming are essential. Some projects need additional skills too.
Early Spinoffs We regard it as vital that projects have early spin-offs that can be completed well within the time. These early spin offs help to ensure that even when a projects runs into difficulties that the Audacity project still gets a useful result.

Label Track Enhancements

Possible Mentors:

  • James Crook, Federico Grau

Description: Audacity has flexible Label tracks for annotating sections of the audio. The method for positioning and dragging the labels allows the same kind of labels to easily be used to label points, ranges, and also maintain boundaries between regions by dragging two end points at the same time.

We're looking for proposals for the next stage of enhancements, that integrate them more into the audio editing process. Possibilities to consider include:

  • More operations on labels, such as 'apply effect at labels'.
  • Visual enhancements, such as different icons and colours associated with different kinds of labels.
  • Handling of very large numbers of labels. This requires both optimisations and new visual options.
  • Snapping of labels, so that they position at specified time intervals.
  • New ways to automatically compute labels.

A detailed proposal should make clear the use cases for the enhanced labels that are motivating the changes.

Skills:

  • wxWidgets and C++

Early spinoff from this work:

  • Label tracks to stick to the track above, so that they edit together.


Postfish Integration

Possible Mentors:

Description: Postfish is a p-threads based Linux audio application with uncompromising quality and some unique effects such as 'deverb' which removes unwanted reverb from a track. Currently it can't be used from within Audacity.

Integrating it into Audacity will be a challenge indeed, particularly on the windows side where we anticipate problems with a simple translation to wxThreads. The student will need to be prepared to dive into such code.

We also have to be mindful that Audacity will usually be run on machines with far less processing power than the ideal for Postfish. Postfish does heavy number crunching. Its 'deverb' effect was designed for Dual Xeon 3GHz systems. For its integration in Audacity we want to fall-back gracefully to non-real time mode when necessary.

This is part of the Connected Open Source initiative, aiming to build more bridges between Open Source projects.

Skills:

  • wxWidgets and C++
  • pThreads
  • Experience with both Linux and Windows would help.

Early spinoffs from this work:

  • Demonstration of a simple real-time echo effect using same thread structure as planned for Postfish integration.


Intuitive cross-fading

Possible Mentors:

  • Matt Brubeck

Description: One of the most common operations people want to do when mixing audio is to smoothly transition between two sound clips. This is commonly called a cross-fade. This operation is technically possible in Audacity now, but it is very clunky, requiring multiple steps and no editability short of undoing the actions and starting again. We are looking for someone to implement a clean, intuitive, nondestructive cross-fade for Audacity. Audacity already has all of the infrastructure necessary to support implementing this operation nondestructively and we already have a clear plan for how it should work. The following webpage has a mockup of what we think the GUI might look like:

http://limpet.net/mbrubeck/temp/cross-fade/ 

This feature, while seemingly small, would represent a huge boost in usability for Audacity. This feature is intimately related to several other UI enhancements that we have proposed: for example, one element of this proposed GUI is that clips "stick" to each other or "snap" into place when you push them together. Such a snap-to behavior would be great in several other circumstances, for example having a track stick to t=0, or to a point that lines up with another track.

Skills:

  • wxWidgets and C++

Early spinoffs from this work:

  • Ability for all effects to be faded in/out automatically. This can avoid clicks in some circumstances.


Play-Back Enhancements

Possible Mentors:

  • Dominic Mazzoni, Vaughan Johnson, James Crook

Description: Audacity lags behind commercial audio software in a number of details of its play back behaviour. Specific enhancements we would like a summer student to provide are:

  • No 'click' on start/stop/loop; At the moment there usually is an audible click when Audacity starts or stops playing a sound, or in iterations of playing a loop. A very short fade-in and fade-out applied only to playback should fix this.
  • Loop play adjusts dynamically to boundaries being moved; Finding the precise boundaries of a sound, for example an unwanted sound to be fixed, can be difficult with Audacity as it currently is. The location of the sound isn't obvious from the waveform. The new option would allow playing the sound in a loop, adjusting the boundaries to find out exactly where it starts and stops.
  • Vari-speed playback; Fast playback of sound allows sections of audio to be located more rapidly. Slow playback allows precise location (on timeline) of sound to be determined more accurately. There is a crude version of this on the 'Transcription Toolbar' - refining it would include allowing the speed to vary during playback without starting and stopping.
  • Drag-playback-cursor whilst playing; This requires changes to both playback and GUI. It is an extension of vari-speed playback and would make locating sound more rapid.
  • Play all 'labels' on the selected label tracks; Labels can be placed on the Audio both manually and automatically. This has many uses, one being the possibility of previewing a recording whilst skipping over periods of silence.

Skills:

  • wxWidgets and C++

Early spinoffs from this work:

  • The schedule should plan to have some features complete to the 'release candidate' phase by the half way point. This is more useful than progressing all of the features in tandem, and perhaps completing none of them if time runs out.

FFmpeg integration

Possible Mentors:

  • Richard Ash, Dominic Mazzoni, Vaughan Johnson

Description: A patch has been produced in the past to use FFmpeg libraries for importing and exporting audio files in a wide variety of audio formats. This however was against 1.2.x and will require considerable changes to integrate it with current audacity code. There will also be issues surrounding the build system and ensuring license requirements are met when distributing the resulting program.

  • Import needs to decode the imported files into audacity, handling varying channel counts sensibly.
  • metadata in imported files should be fed into the audacity meta-data handling so it can be stored, edited and used for exported files.
  • A decision is needed on what to do if video files (with and without sound tracks) are presented.
  • Export will need to work out how to provide a user interface to handle choice of codec and container formats.
  • Export should cater for multi-channel output where applicable with more than 2 output channels, using the export routing code already in place.
  • Export needs to write relevant metadata to the exported file from the available audacity metadata and user interface.

Skills:

  • wxWidgets and C++
  • Must be prepared to work on both Windows and Linux and ideally Mac OSX too.

Early spinoffs from this work:

  • Importer is probably easier to do and independent of export. Adding an importer should not be terribly hard to do, at least for mono and stereo files which covers most use cases. No interface modifications needed to do this, and enabling / disabling it at build time is clean and follows other importers.
  • Metadata support can be implemented after other parts are complete / working.

More ideas at More GSoC Ideas; also the feature Feature Requests page may suggest ideas for a project proposal.