After integration of the program in the PortableApps.com Platform it`s impossible to change the language permanently. Only in the case of installation NOT in the Platform can performed a durable change of language.
New: NAPS2 (Feb 24, 2025), Platform 29.5.3 (Jun 27, 2024)
1,100+ portable packages, 1.1 billion downloads
No Ads!, Please donate today
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on BlueSky
Follow us on Facebook
Follow us on LinkedIn
Follow us on Mastodon
Follow us on Twitter
The language of Audacity will automatically change to match that of the platform. This is by design and the same as GIMP, Pidgin and other apps. If you want Audacity in German, set the platform to German. Is it not working that way at the moment? I can't recall offhand, but Audacity's launcher may have a bug with specific languages.
UPDATE: It looks like it is a bug. Open the file AudacityPortable.ini in the AudacityPortable\App\AppInfo\Launcher directory. Delete the tenth line (Default=en) and then save it. Does it auto-switch for you properly now?
Sometimes, the impossible can become possible, if you're awesome!
At my own research I also find out the way to delete the 10. line of the file AudacityPortable.ini. But with this action the instructions in the Support for Audacity respective "Change Audacity Portable to Another Language" are needless.
The instructions are for standalone users. Not everyone uses the menu, though we'd like them to.
Sometimes, the impossible can become possible, if you're awesome!
It´s true, that thess instructions affect only the standalone installation. In the last weeks I have now begin to read the instructions at your website respective the creation of portable apps. But these tutorials are more a reference. Is there a arrangement for the next time, that you announce a step by step tutorial?
Thanks for that advice, I didn't find that bug as I didn't use Audacity portably for some time.
Further testing revealed some inconsistencies. I don't know when or why that happens, but from time to time, Audacity starts with the same settings as my local install, that means hijacking its settings.
My local install not set to portable settings but stores its settings in the AppData folder. I did some investigation and found another hint. I use audacity for some years and so have some old registry entries form a version prior to 1.3 left which Audacity seems to use, too (see wiki on their page).
I'll do some cleanup this evening and report if this strange behavior still occurs.
Another point: Audacity has no function to manually enter the path for VST-plugins but scans the system and stores found locations in the plugnins.cfg.
I manually edited that file, but it is not taken care of by the launcher (drive letter etc.).
I can only give better information when I have stripped my registry from old entries, because I don't know if the VST locations are stored there, too.
Now time now, but later...
I know the article at the wiki for audacity respective some troubleshooting with older versions prior 1.3 of audacity. The question is if audacity with version 1.3 or above trying to detect the path to an older LAME encoder "lame_enc.dll". This path is created by an older version of audacity ( 1.2 or below). If you want to solve this problem with your local installation of audacity, it`s NOT necessary to delete some registry keys respective your older version 1.2 of audacity. Here you have 2 possibilities to solve this problem:
1.) If you have installed the portable version of Audacity from this website, you can put the LAME encoder "lame_enc.dll" directly in your AudacityPortable\App\LAME directory.
2.) If you use now a local installation of Audacity version 1.3 or higher simultaneously with a local installation of Audacity version 1.2 or deeper, then you must ensure there are no older versions of lame_enc.dll in any locations where Audacity detects it. In your case (you come from germany) you must delete older versions of the file lame_enc.dll in the following paths: C:\Programme\Lame für Audacity, C:\Programme\Audacity 1.3 Beta (Unicode) or in the Plug-Ins folder inside that. Then you exit Audacity. After this you navigate to the 1.3 preferences .cfg file at: C:\Dokumente und Einstellungen\Benutzername\Anwendungsdaten\Audacity\audacity.cfg. Open audacity.cfg in a text editor such as Notepad, and delete the two lines starting with:
[MP3]
MP3LibPath=
Then save the changes to audacity.cfg and restart Audacity.
With respect to your problems with VST-Plugins I can`t help you, because I don´t have any experience with this subject.
@tapsklaps: Thanks, but I don't have any problems with lame. All installations have their own lame_enc.dll wich are defined via settings (and use these as they should normally).
@John, Chris... (or someone with more insight to the launcher than me)
The issue I found seems to be a timing problem.
I cleaned up my registry - I don't have any version 1.2 in use, the regs seem to have been left over by updating with 1.3 a year ago. It didn't contain any suspicious settings anyway.
I suspect there being a lag when the launcher moves the "Portable Settings" folder to the Audacity folder. As Audacity checks for the existence of that folder to decide not to use settings in %AppData% maybe the transfer sometimes just is not fast enough. Then it doesn't start in "portable" mode but uses %AppData% instead.
I don't know if the launcher waits for the DirectoriesMove to be completed or starts the app parallel to that. Audacity apparently has no time defined to wait for that folder to materialize as it normally is just there (or not and then %AppData% is to be used).
I eleminated the problem by moving "portablizing" my local settings e.g. creating a Portable Settings folder in my local install.
The Problem didn't occur for the last few retries, but I don't know if it's just because now the file transfer of the launcher is cached or if it just was a performance problem this afternoon though there was no workload on my computer that time...
) but until now it didn't happen.
I watched out for a new Audacity folder to turn up in %AppData% (that would somewhat confirm my crude thesis
Some key data: I use WinXPSP3 admin and the respective drive was a 1.8" HD (fast transfer, slow seek times).
-edit-
A possible solution: include the folder "Portable Settings" by default (even if empty) then it is there and the launcher just replaces it with the one in Data. So Audacity would never be in the situation not to find it and therefor start in non-portable mode.
No matter what I've tried, I can't reproduce this issue and no one else has reported it.
Sometimes, the impossible can become possible, if you're awesome!
It didn't occur again the few times I used Audacity portable the last week. Maybe it was a one time issue caused by some strange condition at that time or the leftovers of an old local installation or all combined...
I could not repuduce it either, so maybe it was just my setup here (and at that time). It seemed strange enough that day.
Is it practicable to add an empty folder "Portable Settings" by default just in case or can that cause problems? I tried it and it is backed up as expected during runtime. The only issue I can think of might be that two sets of portable settings may be created if the bug should incredibly occur (and my suspicions were correct;) ).
As the existence of a folder with that name is the only switch to make Audacity behave portable, it would at least be a safety line (if needed).