You'll need to do some fairly heavy hacking to get into those areas, so why not access the audio data directly from the project rather than via its external files?fmiyara wrote:I hope in a future to have all processing done inside Audacity, but for the time being, some processing must be done using specific software such as Matlab, Scilab or Octave. I find it cumbersome having to export and import audio in whatever format (wav, pcm) to have it available outside the Audacity environment, when a script out there could read and process an Audacity project and return a valid Audacity project.I'm aware of that. However, importing a WAV file with, for instance, cues or notes, doesn't result in the inclusion of cues as labels in the .AUP; and, conversely, .AUP labels are not exported to .WAV. Cues or whatever time-related marks are most interesting for measurement documentation purposes, musical analysis, phonetic analysis, bioacoustics, and so on.Audacity handles metadata in the .AUP file, not the .AU files.
Audacity handles labels in the .AUP file, not in the .AU files.
There are various ways that you could do that, for example you could add a "dummy" effect that simply pipes audio data to/from the selected track(s) to your external code, or you could create a Nyquist plug-in to read/write audio data to/from a specified location, or you could use mod-script-pipe. Hacking into the external project files just seems to be a rather cumbersome and error prone approach if you don't mind me saying.