Can “.aup”-files contain default audio export settings? So when I open the file and click on “Export Audio…”, these settings (file type, path etc.) are suggested as default values? If not, is the information about those default values stored elsewhere and can one edit them safely?
PS: The question results my attempt to program a Blender Addon which allows me to open a sound file from Blender in Audacity via an “Open in Audacity”-Button. After pressing that button, an .aup file is created and opened which contains a link (via ) to the sound file and text markers that also exist in the Blender project (via ). After editing in Audacity is done, one shall click on “Export Audio…” and save the audio to the path in which the .aup file is (therefore the question; I try to automate that process as much as I can). My Blender Addon then reads the saved audio and replaces the old audio with the new one. This project is the simplified version of a project I wrote about earlier ( https://forum.audacityteam.org/t/aup-file-reference-and-wav-instead-of-au/44422/1 ).
No. An AUP file is by definition a per project file.
Yes in audacity.cfg.
are stored, and encoding qualities for particular formats (when used) are also stored. However you can only edit that file when Audacity is closed. Audacity won’t pay attention to edits you make to the file while Audacity is running, and will overwrite those edits when it exits.
Another question that is not different enough to start a new thread:
Can one open an Audacity project via command line with a custom settings path? Like
audacity myProject.aup /c ..\settings\
? Or are only the “hard coded” paths (“Portable Settings”/OS-specific AppData) possible? If so, do you plan adding such a feature in (near) future? (I know that that would make having multiple instances of Audacity very easy and I don’t know if that is wanted or not)
And all that just for a simple “Edit in Audacity”-Button. Btw. the part of the script that generates the Audacity project is done and works as it should, including text markers. I only struggle at the reimport of the edited audio file in Blender because my script can’t know where the user saves the file and the user can’t intuitively find the directory where the script expects the audio file to be saved in. Therefore this question so that user intuitively exports the audio to a path the script knows of.
Yes, that would be perfect. Then my script could generate the project file, open it in Audacity and it would be clear what the export path is. And that would make my personal workflow beside the script better because I store Audacity projects mostly near the location where I want to export the audio and I always had to navigate through the whole directory tree to find it. So that sounds as a really good solution if that feature is added. It would even be okay for me if one had to activate it manually in the settings, because one could suggest users to do so while using my script and it would only mean a single required user action.