Regarding the question about Audacity:
Audacity works with "projects". An "Audacity Project" is a format specific to Audacity that allows Audacity to perform simple or complex audio editing and processing on one or more audio tracks. Audio may be "recorded" into an Audacity project or may be "imported" into an Audacity project. Please note that an Audacity project is not
an audio file. To create a normal audio file from an Audacity Project you must "export" the audio. For more information about this, please see here in the manual: http://manual.audacityteam.org/o/man/au ... jects.html
Returning to the original question from: viewtopic.php?p=215547#p215547
pstein wrote:After having dragged a MP3 onto Audacity I want to close the whole prgm.
Much to my surprise I got a prompt "Save changes before closing?"
The misconception here is that "Audacity has opened the MP3 file", but that is not
what has happened. There are two actions that have occurred:
1) A new (empty) Audacity Project has been opened.
2) An MP3 file has been imported (copied) into the Audacity project.
Note that the Audacity Project is no longer a new empty project as it now contains imported audio data from the MP3 file.
On closing, Audacity (rightly in my opinion) asks the user whether they want to save the changes.This behaviour is entirely in keeping with how the vast majority of other computer programs behave after importing data.
As an example:
1) Open Libre Office
Writer (or Open Office
Writer) [free open source word processors].
2) Drag a text file into the open document. The text file is imported into the document.
3) Close Libre Office. You are asked if you want to save the changes.Regarding feature votes:
Please note that Audacity is a free open source program and is primarily created, maintained and supported by unpaid volunteers in their "spare time". Developing new features can be a difficult and time consuming task, so not surprisingly the reality of the situation is that developers will generally prefer to spend their time working on things that they are interested in. Nevertheless, we feel that it is worthwhile to keep a record of feature requests from users as it serves to provide insight and overview of those things that users are interested in.
As an example, it was previously thought to be near impossible to implement any form of "real time processing" in Audacity due to the fundamental architecture of the program. However, we continued to keep a record of "votes" for this feature, which proved to be the most popular requested feature of all (by a large margin). In Audacity 2.1.0 we are very pleased to announce the first ever implementation of "real time preview". Currently this feature is limited to VST and LADSPA effects only, but future versions of Audacity should see it refined and gradually rolled out to other types of effect.
In short, "voting" for a feature does not mean that the feature will be implemented any time soon. For a feature to be implemented it needs to be technically feasible, it may need consideration regarding conflicts with other features, and very importantly it requires someone with the necessary technical skills to have the time and interest to implement it.
As an open source program we welcome contributions from new developers.Regarding belligerent ranting:
The final two posts from Brian P Barnes have been disapproved. Please note that referring to the forum staff as terrorists with personal vendettas does not strengthen your point, it only wastes our time which would otherwise be better spent helping other Audacity users.