"Opening" files

[steve]

As there is still frequently confusion about the difference between "Audacity Projects" and "audio files", would it help to:

• Change "File > New" to "File > New Project"
• Change "File > Open..." to "File > Open Project..."
• Move "File > Import >" up the menu between "Open Project..." and "Recent Files >"

The down side is that "importing a file into a new project" would require an extra click (open a new project, then import the file).
The main plus side is that when "importing a file into a new project" it would be clear to new users that that is what they are doing (and not actually "opening" the audio file).

If the extra click is considered to be a deal breaker (I don't personally think that it is), then there could be an additional menu item for:
"File > Import into New Project >"

File-import.png (47.15 KiB) Viewed 1784 times

[kozikowski]

You're just dancing around:

Save Project.
Save Sound File.

Shoot it and get it over with. I have a blindfold here somewhere. Western bandanna style of course.

Just one Open. Let the machine figure it out.

Koz

[steve]

Just one Open. Let the machine figure it out.

We've been doing that for years.
The machine figures it out and then the user messes it up because they don't understand what the machine has done.

[waxcylinder]

Ooh - the hobby-horse is out in the paddock yet again for another run around

[steve]

I accept that it's a 'hobby horse', but if we can reduce the number of common user errors without too much inconvenience to everyone else, then I think it's worth doing.

[Gale Andrews]

You're just dancing around:

Save Project.
Save Sound File.

Shoot it and get it over with.

Of course. The obvious answer.


Gale

[Gale Andrews]

You're just dancing around:

Save Project.
Save Sound File.

Shoot it and get it over with.

Of course. The obvious answer.


Gale

But since we won't do the obvious why not support http://wiki.audacityteam.org/wiki/Propo ... on#Details ? You (Steve) are still written there as supporting it. That proposal clearly distinguishes projects and files which I thought was the object of the exercise.

But Vaughan won't buy it (yet). We already discussed it on -quality.


Gale

[steve]

But since we won't do the obvious why not support http://wiki.audacityteam.org/wiki/Propo ... on#Details

That would do nicely I think, but as you say, Vaughan doesn't buy it. Perhaps he would buy a smaller change?

[waxcylinder]

You're just dancing around:

Save Project.
Save Sound File.

Shoot it and get it over with.

Of course. The obvious answer.


Gale

Looks like you may get what you are wishing for ...

I note from James' recent thoughtpiece: http://wiki.audacityteam.org/wiki/User: ... kPanelDemo that he plans:
Proposal File Menu Reorganization : One detail is that you will be able to open a wav file, and save it back to a wav file, so the confusing distinction between save and export largely goes away.

Peter.

[steve]

http://wiki.audacityteam.org/wiki/User: ... kPanelDemo

Proposal Unitary Project : Intention is to add load/save of Wav files, using additional streams within Wav for things like labels. Eventually will work by extending a file with new data and cached changes being added on the end - i.e. and unitary project format, that also happens to be playable as a Wav file (one that has extra baggage in it at the end, and raw recording at the start).

Proposal File Menu Reorganization : One detail is that you will be able to open a wav file, and save it back to a wav file, so the confusing distinction between save and export largely goes away.

That'll do