Difference between revisions of "Completed Proposal Import/Export Eq Curves"

From Audacity Wiki
Jump to: navigation, search
(In response to previous discussion on the forum and recent suggestions on audacity-devel)
 
(add my support for this - suggest we should plan for multiple curve import/export)
Line 1: Line 1:
{{Proposal_Header|This page is a proposal for automatically removing DC bias.  }}
+
{{Proposal_Header|This page is a proposal for importable and exportable preset curves for the Equalization effect.  }}
  
 
__NOTOC__
 
__NOTOC__
Line 5: Line 5:
 
== Proposed Feature ==
 
== Proposed Feature ==
  
To provide a simple method to import/export curves for the Equalizer effect.
+
To provide a simple method to import/export curves for the Equalization effect.
 
This would allow a "library" of curves to be made available for simple download and installation by any user.
 
This would allow a "library" of curves to be made available for simple download and installation by any user.
  
  
== Developer Backing ==
+
== Developer/QA Backing ==
  
 
* Martyn Shaw?
 
* Martyn Shaw?
 
+
* GA
  
 
== Use Cases ==
 
== Use Cases ==
  
* The Equalizer effect is a versatile multi-purpose tool used by most users:
+
* The Equalization effect is a versatile multi-purpose tool used by most users:
 
:* The current Preset list is dominated by "vinyl equalization" curves.   
 
:* The current Preset list is dominated by "vinyl equalization" curves.   
 
:* Many other curves that would be useful to many users are excluded.
 
:* Many other curves that would be useful to many users are excluded.
 
:* What may be a useful set of curves for some users will be irrelevant to other users. A simple method to import "preset" curves will allow users to load the Equalizer effect with the curves that are most useful for them.
 
:* What may be a useful set of curves for some users will be irrelevant to other users. A simple method to import "preset" curves will allow users to load the Equalizer effect with the curves that are most useful for them.
:* A simple method to export curves will allow users to easily share their custom curves with others and quickly build a library of Equalizer settings.
+
:* A simple method to export curves will allow users to easily share their custom curves with others and quickly build a library of Equalization settings.
  
  
 
== Background ==
 
== Background ==
It has occurred many times on the forum that a user has asked how to achieve a result using the Equalizer, for example how to simulate the sound of a walkie-talkie, or remove the harshness from a vocal recording. While it is simple to produce suitable Eq settings, passing that information on to the user either requires that they try to copy a screen-capture or manually edit the EQCurves.xml file. Neither of these solutions are convenient or user friendly.
+
It has occurred many times on the forum that a user has asked how to achieve a result using Equalization, for example how to simulate the sound of a walkie-talkie, or remove the harshness from a vocal recording. While it is simple to produce suitable Eq settings, passing that information on to the user either requires that they try to copy a screen-capture or manually edit the EQCurves.xml file. Neither of these solutions are convenient or user friendly.
  
There has recently been a revised RIAA curve produced. The facility for easily importing curves would allow users to immediately make use of this and similar resources.
+
There has recently been a revised RIAA curve produced. The facility to easily import curves would allow users to immediately make use of this and similar resources.
  
 
A selection of "general purpose" settings such as "bass boost/bass cut/treble boost/treble cut/telephone/loudness/rumble filter" would not only be useful to a wide
 
A selection of "general purpose" settings such as "bass boost/bass cut/treble boost/treble cut/telephone/loudness/rumble filter" would not only be useful to a wide
Line 35: Line 35:
 
From a user perspective, a simple way to implement import/export of Eq curves would be the addition of 2 buttons on the Equalizer interface.
 
From a user perspective, a simple way to implement import/export of Eq curves would be the addition of 2 buttons on the Equalizer interface.
 
Clicking the "Export" button would bring up a browser window allowing the '''current curve settings''' to be exported as an XML file.
 
Clicking the "Export" button would bring up a browser window allowing the '''current curve settings''' to be exported as an XML file.
Clicking the "Import" button would bring up a browser window allowing a correctly formatted XML file to be imported and becoming the current '''Custom curve'''.
+
Clicking the "Import" button would bring up a browser window allowing a correctly formatted XML file to be imported and become the current '''Custom curve'''.
  
 
The name of the curve ''could'' be included in the XML file but this poses potential issues of duplicate curve names. Alternatively the curve could unnamed and simply become the "Custom" curve that the user can Save into their preset list in the normal way.
 
The name of the curve ''could'' be included in the XML file but this poses potential issues of duplicate curve names. Alternatively the curve could unnamed and simply become the "Custom" curve that the user can Save into their preset list in the normal way.
Line 44: Line 44:
  
 
== Discussion ==
 
== Discussion ==
 +
 +
* '''Gale:''' I think curves would have to be named - the average user will have little idea from a row of figures what the curve is. There should be a dialogue to ask user to choose a new name if an imported curve bears the same name as an existing one. <p>Although we don't want to get too advanced to begin with, clearly the most useful way this feature will develop will be that packages of curves will be available such as "Robots and automatons"; "Radios"; "Genres" etc. So I think we should at least be planning for that at this stage e.g. selecting multiple/all items in the curve list or in the browser window exports/imports a batch of curves as one named xml file.</p>

Revision as of 11:08, 16 March 2010

Proposal pages help us get from feature requests into actual plans. This page is a proposal for importable and exportable preset curves for the Equalization effect.
Proposal pages are used on an ongoing basis by the Audacity development team and are open to edits from visitors to the wiki. They are a good way to get community feedback on a proposal.


  • Note: Proposals for Google Summer of Code projects are significantly different in structure, are submitted via Google's web app and may or may not have a corresponding proposal page.


Proposed Feature

To provide a simple method to import/export curves for the Equalization effect. This would allow a "library" of curves to be made available for simple download and installation by any user.


Developer/QA Backing

  • Martyn Shaw?
  • GA

Use Cases

  • The Equalization effect is a versatile multi-purpose tool used by most users:
  • The current Preset list is dominated by "vinyl equalization" curves.
  • Many other curves that would be useful to many users are excluded.
  • What may be a useful set of curves for some users will be irrelevant to other users. A simple method to import "preset" curves will allow users to load the Equalizer effect with the curves that are most useful for them.
  • A simple method to export curves will allow users to easily share their custom curves with others and quickly build a library of Equalization settings.


Background

It has occurred many times on the forum that a user has asked how to achieve a result using Equalization, for example how to simulate the sound of a walkie-talkie, or remove the harshness from a vocal recording. While it is simple to produce suitable Eq settings, passing that information on to the user either requires that they try to copy a screen-capture or manually edit the EQCurves.xml file. Neither of these solutions are convenient or user friendly.

There has recently been a revised RIAA curve produced. The facility to easily import curves would allow users to immediately make use of this and similar resources.

A selection of "general purpose" settings such as "bass boost/bass cut/treble boost/treble cut/telephone/loudness/rumble filter" would not only be useful to a wide audience but could have "educational value" for people that are new to audio processing.


Proposal

From a user perspective, a simple way to implement import/export of Eq curves would be the addition of 2 buttons on the Equalizer interface. Clicking the "Export" button would bring up a browser window allowing the current curve settings to be exported as an XML file. Clicking the "Import" button would bring up a browser window allowing a correctly formatted XML file to be imported and become the current Custom curve.

The name of the curve could be included in the XML file but this poses potential issues of duplicate curve names. Alternatively the curve could unnamed and simply become the "Custom" curve that the user can Save into their preset list in the normal way.

Position of the buttons:

There are various options but at present I would favour placing the Import/Export buttons after the Save/Delete buttons. The "Grid" checkbox could be moved lower down to the same line as "Preview" button.


Discussion

  • Gale: I think curves would have to be named - the average user will have little idea from a row of figures what the curve is. There should be a dialogue to ask user to choose a new name if an imported curve bears the same name as an existing one.

    Although we don't want to get too advanced to begin with, clearly the most useful way this feature will develop will be that packages of curves will be available such as "Robots and automatons"; "Radios"; "Genres" etc. So I think we should at least be planning for that at this stage e.g. selecting multiple/all items in the curve list or in the browser window exports/imports a batch of curves as one named xml file.