You're welcomed.
Have a nice evening as well as Audacity team.
Search found 8 matches
- Mon Mar 29, 2021 5:43 pm
- Forum: Windows
- Topic: VST_PATH Audacity 2.1.3
- Replies: 11
- Views: 603
- Mon Mar 29, 2021 4:56 pm
- Forum: Windows
- Topic: VST_PATH Audacity 2.1.3
- Replies: 11
- Views: 603
Re: VST_PATH Audacity 2.1.3
Hi, I sent a PM. However here are possible steps for a test : - Install a vanilla version of Audacity (and/or delete or move pluginregistry.cfg) - Make sure there is no VST reg keys : HKCU\\Software\\VST\\VSTPluginsPath and HKLM\\Software\\VST\\VSTPluginsPath - Make sure plugins dir has no VST plugi...
- Sun Mar 28, 2021 8:09 pm
- Forum: Windows
- Topic: VST_PATH Audacity 2.1.3
- Replies: 11
- Views: 603
Re: VST_PATH Audacity 2.1.3
Hi Steve,
I just begin to prepare the PR and so I sync the master.
I guess a fix has just been included as I see the following code in VSTEffect.cpp (line 405):
The history confirms this.
Regards.
I just begin to prepare the PR and so I sync the master.
I guess a fix has just been included as I see the following code in VSTEffect.cpp (line 405):
Code: Select all
wxStringTokenizer tok(vstpath, wxPATH_SEP); Regards.
- Sun Mar 28, 2021 6:36 pm
- Forum: Windows
- Topic: VST_PATH Audacity 2.1.3
- Replies: 11
- Views: 603
Re: VST_PATH Audacity 2.1.3
Hi,
No problem
Here is a little code variant that I use for recent Audacity version:
It is inserted in VSTEfect.cpp after these lines, around line 400:
No problem
Here is a little code variant that I use for recent Audacity version:
Code: Select all
#if defined(__WXMSW__)
wxStringTokenizer tok(vstpath,";");
#else
wxStringTokenizer tok(vstpath);
#endifCode: Select all
if (!vstpath.empty())
{
- Tue Mar 27, 2018 7:41 pm
- Forum: macOS
- Topic: +6dB gain in Audio Units
- Replies: 8
- Views: 708
Re: +6dB gain in Audio Units (and VST)
Hello,
Using Audacity 2.2.2, I see the same behaviour with VST on Windows (maybe the topic should be moved or copied ?)
For example, using HOFA 4U Meter/Fader/MS-Pan, or ReaJS w/psycho_dither shows +6dB at input meters...
Obviously the test track has been normalized to -0.1dB
Regards.
Using Audacity 2.2.2, I see the same behaviour with VST on Windows (maybe the topic should be moved or copied ?)
For example, using HOFA 4U Meter/Fader/MS-Pan, or ReaJS w/psycho_dither shows +6dB at input meters...
Obviously the test track has been normalized to -0.1dB
Regards.
- Sun Feb 25, 2018 11:09 am
- Forum: Windows
- Topic: VST_PATH Audacity 2.1.3
- Replies: 11
- Views: 603
Re: VST_PATH Audacity 2.1.3
Hello,
Any chance to include this fix in master ?
Alternatively how can I submit a patch ?
Any chance to include this fix in master ?
Alternatively how can I submit a patch ?
- Thu Mar 23, 2017 12:34 am
- Forum: Windows
- Topic: VST_PATH Audacity 2.1.3
- Replies: 11
- Views: 603
Re: VST_PATH Audacity 2.1.3
Hi,
I think I found the issue.
In the code of VSTEffect.cpp
The tokenizer at line 354 should be turned into:
I think I found the issue.
In the code of VSTEffect.cpp
The tokenizer at line 354 should be turned into:
Code: Select all
wxStringTokenizer tok(vstpath, ";");
//with the ";" delimiter
- Wed Mar 22, 2017 8:47 pm
- Forum: Windows
- Topic: VST_PATH Audacity 2.1.3
- Replies: 11
- Views: 603
VST_PATH Audacity 2.1.3
Hi, I use Audacity 2.1.3 with VSTs on Windows 10 and I wonder if the behaviour stated in wiki for VST lookup is correct. ( http://manual.audacityteam.org/man/installing_effect_generator_and_analyzer_plug_ins_on_windows.html#vst_install ) Indeed, I prefer to use a VST_PATH system environment variable...