For questions, answers and opinions
https://forum.audacityteam.org/
No that's not reliable. It seems to show the location from which it was launched rather than where the executable is.Robert J. H. wrote:How aboutCode: Select all
(print *default-sf-dir*)
This is pretty easy for a built-in effect but without patching Nyquist code it's probably not available to an external plug-in. But in reality you don't need all of that from a built-in effect because there's a wxWidgets function which returns the configuration directory no matter where it is.steve wrote:I don't know of any reliable way to find the directory from which Audacity is running (which I think would be required to find a Portable Settings folder). Let me know if you find one
Thanks Edgar. That's going on the Nyquist wish listEdgar wrote:But in reality you don't need all of that from a built-in effect because there's a wxWidgets function which returns the configuration directory no matter where it is.
What do you mean by launched? I launch it via link on the desktop, but it returns the right directory.steve wrote:No that's not reliable. It seems to show the location from which it was launched rather than where the executable is.Robert J. H. wrote:How aboutCode: Select all
(print *default-sf-dir*)
Code: Select all
(print (setdir ""))As an example, if you open the Windows Command Prompt, the prompt will indicate the current directory. If you then launch Audacity from the Command Prompt, *default-sf-dir* will indicate the same directory as was shown in the Command Prompt. If you then close Audacity, navigate to a new directory and relaunch Audacity, *default-sf-dir* will indicate the new location.Robert J. H. wrote:What do you mean by launched?
I guess that's the Linux way of doing things...steve wrote:As an example, if you open the Windows Command Prompt, the prompt will indicate the current directory. If you then launch Audacity from the Command Prompt, *default-sf-dir* will indicate the same directory as was shown in the Command Prompt. If you then close Audacity, navigate to a new directory and relaunch Audacity, *default-sf-dir* will indicate the new location.Robert J. H. wrote:What do you mean by launched?
That was on Windows XPRobert J. H. wrote:I guess that's the Linux way of doing things...
Not essential, but easier for the user.Robert J. H. wrote:After all, reading the current Latency Correction isn't that important.
The PortAudio library we use does of course have a simplistic feature that tries to do that. It works fairly well with MME host in Device Toolbar but not with Windows DirectSound, which was the reason the automatic adjustment was turned off.steve wrote:The next best thing would be if Audacity automatically knew how much round trip latency there would be, then Audacity could automatically adjust for it.