As far as I know the unified project as proposed does not help your use case. You want to save a WAV file. I did not think we would be exporting a WAV file inside the unitary Audacity project file. Windows and Linux don't have file bundles that are really folders, except for compressed files like ZIP, and compression/decompression has time penalties.arminb wrote:The unified project file idea would be a welcome feature addition to Audacity, I know I would benefit from it. Plus, it would be an opportunity to solve my specific use-case!
And even if we did export inside an AUP compressed file, are we still not stuck with not being able to export inside the Logic bundle?
You don't mean, do you, that if you chop a piece of the audio out in Audacity and switch to Logic, it deletes that same audio (or marks it as deleted) without you having to export the file from Audacity?arminb wrote:I may not understand the question, so I will answer it a couple ways.Gale Andrews wrote:Where it gets complex is - what happens if you import one file from some app, and then another one?
When I launch Audacity from within Logic, it (Logic) keeps track of that and "refreshes" the files that were opened that way every time I command-tab back to Logic.
If users start changing the referenced file that does create a "total mess" for Audacity. I think we would copy in.arminb wrote:if you are asking about one file being imported into Audacity (as a referenced file, not a copy), and then that same file also imported as a referenced file into some other editor or DAW, then I guess that would be either real efficient or a total mess, depending on what one is trying to do.
But what I was thinking was if you import one file into Audacity, then another into the same project window, then choose File > Overwrite original, which file are we overwriting? If there is a complex dialogue to decide which file gets overwritten with selected audio or the whole project, it starts to defeat the object of a quick process.
So what is the import path? If you import a file from Logic, then look in ~/Library/Application Support/audacity/audacity.cfg, what does "DefaultOpenPath" say?arminb wrote:Potentially a different folder, but always in the appropriate project bundle - because I tell Logic to copy all assets into it. In Audacity I can manually import other files from anywhere within the bundle, as long as the last import was from somewhere within that bundle. But as you pointed out, that path is not available in the Export dialog, and there does not appear to be a way to open the bundle from there eitherGale Andrews wrote:Do the files always get imported from the same location, or is it a different folder every time?
Gale