Export/Save to location where file is located.

Anything you think is missing, or needs enhancement, goes here.
Forum rules
If you require help using Audacity, please post on the forum board relevant to your operating system:
Windows
Mac OS X
GNU/Linux and Unix-like
steve
Site Admin
Posts: 81336
Joined: Sat Dec 01, 2007 11:43 am
Operating System: Linux *buntu

Re: Export/Save to location where file is located.

Post by steve » Wed Mar 31, 2021 11:39 am

dna598 wrote:
Wed Mar 31, 2021 11:31 am
For starters i said i am opening the file from the DAW.
How? :?
9/10 questions are answered in the FREQUENTLY ASKED QUESTIONS (FAQ)

steve
Site Admin
Posts: 81336
Joined: Sat Dec 01, 2007 11:43 am
Operating System: Linux *buntu

Re: Export/Save to location where file is located.

Post by steve » Wed Mar 31, 2021 11:40 am

dna598 wrote:
Wed Mar 31, 2021 11:31 am
Stop coddling the user, and let us use the program.
You want us to pamper the expert users instead? ;)
9/10 questions are answered in the FREQUENTLY ASKED QUESTIONS (FAQ)

dna598
Posts: 11
Joined: Sun Apr 14, 2019 3:57 pm
Operating System: Windows 10

Re: Export/Save to location where file is located.

Post by dna598 » Wed Mar 31, 2021 11:44 am

I don't think it's likely that the developers will go for that as a mainstream option because of the risk to less sophisticated users of permanently overwriting their source files without warning.
add the warning if it bothers everyone so much.

dna598
Posts: 11
Joined: Sun Apr 14, 2019 3:57 pm
Operating System: Windows 10

Re: Export/Save to location where file is located.

Post by dna598 » Wed Mar 31, 2021 11:52 am

steve wrote:
Wed Mar 31, 2021 11:39 am
dna598 wrote:
Wed Mar 31, 2021 11:31 am
For starters i said i am opening the file from the DAW.
How? :?
Audacity is assigned as an external editor in my DAW.

right click on an audio item to "open in audacity.exe".

dna598
Posts: 11
Joined: Sun Apr 14, 2019 3:57 pm
Operating System: Windows 10

Re: Export/Save to location where file is located.

Post by dna598 » Wed Mar 31, 2021 12:06 pm

You want us to pamper the expert users instead?
No, i (and many others) just want Audacity to work properly in the MAINSTREAM use case i have highlighted. Please consider telling that to the developers before making your own mind up about it. I am sure they will appreciate it.

dna598 wrote: The solution is getting the computer to store the file path of the imported files, and providing "export (overwrite source "D:Audio files\something.wav")" for the selected track.

steve
Site Admin
Posts: 81336
Joined: Sat Dec 01, 2007 11:43 am
Operating System: Linux *buntu

Re: Export/Save to location where file is located.

Post by steve » Wed Mar 31, 2021 12:38 pm

The way that I see it is that your feature request is essentially a matter of convenience. It would be a jolly nice convenience for anyone using Audacity as an external editor for a DAW, as it avoids the need to navigate to the DAW's data folder on export, but still only a matter of convenience.

On the other hand, we want to avoid the accidental overwriting of source files, which could be devastating and irreversible.

Satisfying both cases is not simply a matter of "let the user decide", because that assumes that the user already understands the implications of their choice, which is clearly not the case for inexperienced users (the majority of Audacity users).

As a DAW user myself, I do see the benefit of your suggestion, and hope that it will be implemented in one way or another. On the other hand, from a "user support" viewpoint, I do not want to be in the situation of having hundreds of users that have accidentally destroyed irreplaceable recordings. The final point is that any solution has to be implemented by a developer, and there are very few Audacity developers.

This feature request is already logged on the Audacity wiki.
I have logged 3 more votes for the feature for the contributors to this thread.
9/10 questions are answered in the FREQUENTLY ASKED QUESTIONS (FAQ)

dna598
Posts: 11
Joined: Sun Apr 14, 2019 3:57 pm
Operating System: Windows 10

Re: Export/Save to location where file is located.

Post by dna598 » Wed Mar 31, 2021 1:04 pm

Yeah the convenience factor that's preventing the everyday use of Audacity in tandem with a DAW like every other editor. So potentially every DAW user.
And for the fear that some users may complain IF they choose the wrong field, even after it could be hidden and turned off by default and a warning could be implemented.
For fear of a deluge of customer support queries that are not even your problem. really. :lol:
I bet a dev could code this up immediately and implement it without anyone noticing.

Edgar
Forum Crew
Posts: 2043
Joined: Thu Sep 03, 2009 9:13 pm
Operating System: Windows 10

Re: Export/Save to location where file is located.

Post by Edgar » Wed Mar 31, 2021 3:03 pm

Back in the days of Audacity 2.0.6 a commercial user of Audacity paid me to add this ability to Audacity. Part of the deal was that the solution was open source. Part of the description for the change was "we will never need to open more than one file at a time". In the description there was no mention of destructive over-writing. It was quite a bit more complicated than I expected and only worked on Windows.

For about six weeks the user (actually, almost 1000 radio stations across Europe and northern Africa) was quite happy, then… A few of the stations were unhappy with the "never open more than one file at a time" restriction. It was a fairly simple matter to reinstate this ability. Again, they were briefly happy until they realize that the save folder was always the folder of the first opened file. We took a poll of the users and determined that it was about about 50/50 for defaulting to the first opened file's location. I ended up adding a preference switch for "first opened location/last open location"
first or last.png
first or last.png (69.08 KiB) Viewed 302 times
All went well until users started complaining about over-writing file "a" with a playlist composed of files "a" and "b". I addressed this by NEVER doing a destructive over-write. If a save is going to result in overwriting an existing file the existing file is renamed. It might be as simple as renaming "a.wav" which becomes "a.bac.wav". If "a.bac.wav" already exists an integer is added: "a_1.bac.wav"; if this would result in a collision the integer is incremented and the result tried again, and again, and again…

Just saying… It can be done, it's not pretty, there are gotchas, it was a LOT of work AND the source (2.0.6, Windows only) is available for the asking.
-Edgar
running Audacity personally customized 2.0.6 daily in a professional audio studio
occasionally using current Audacity alpha for testing and support situations
64-bit Windows Pro 10

dna598
Posts: 11
Joined: Sun Apr 14, 2019 3:57 pm
Operating System: Windows 10

Re: Export/Save to location where file is located.

Post by dna598 » Wed Mar 31, 2021 4:04 pm

On one hand we have the mod (who today learned about launching audacity as an external editor) saying we can't have the feature implemented for fear of inexperienced users messing up their files, and on the other hand we have "trained professionals" in radio stations that can't handle the settings.
No winning.

Edgar
Forum Crew
Posts: 2043
Joined: Thu Sep 03, 2009 9:13 pm
Operating System: Windows 10

Re: Export/Save to location where file is located.

Post by Edgar » Wed Mar 31, 2021 7:17 pm

dna598 wrote:
Wed Mar 31, 2021 4:04 pm
No winning.
I would not say that it is quite that bad. I have modified Audacity on quite a few occasions for professional users - law enforcement, medical community, audio professionals. For one thing, they almost always have a very clear understanding on what is exactly that they want. On only one occasion have I had to write a new users’ manual - but that was the result of wanting many specific small changes, and one large change. All of the small changes already existed in my personal version and the large change required quite a bit of documentation.

Another thing, I cannot expect the incredibly helpful folks on this forum to do tech support on my modified versions. I have to do all my own tech support but, surprisingly, there has been very little of it. Probably the worst tech support issue is that if I make a change to Audacity for a user that user is forever frozen as far as the Audacity version is concerned. Until Audacity 3.0 came out I would carry originally cherry pick bug fixes and add them to my personal version and for a couple of my professional users. Sadly, the change to unified file format is so major that it will mean that all of my modifications are now frozen in time.

So, probably a slight win in the long run.
-Edgar
running Audacity personally customized 2.0.6 daily in a professional audio studio
occasionally using current Audacity alpha for testing and support situations
64-bit Windows Pro 10

Post Reply