Bug 959 – VST, LADSPA and AU effects incorrectly handled by More...

••• Introduction •••
••• Keywords •••

Audacity 3.0.3 development began 19th April 2021

Audacity Bugzilla

Bug 959 - VST, LADSPA and AU effects incorrectly handled by More...


Summary:	VST, LADSPA and AU effects incorrectly handled by More...

Status:	RESOLVED FIXED

Product:	Audacity
Classification:	Unclassified
Component:	Application Core
Version:	2.1.1
Hardware:	Per OS All

Importance:	P5 RepeatableAll
Assigned To:	Default Assignee for New Bugs

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2015-05-19 17:57 UTC by James Crook
Modified:	2019-05-27 09:25 UTC (History)
CC List:	3 users (show)

See Also:
Steps To Reproduce:	- Delete the audacity.cfg, pluginregistry.cfg and pluginsettings.cfg - Start Audacity - Go into effects->More... and add a VST effect. - Click OK. Notice that the effect appears in the menu. - Go into effects->More... again. Notice that the VST effect is not ticked, and there is no way to remove it.
Release Note:
First Git SHA:
Group:	VST
Workaround:
Closed:	2019-05-27 00:00:00

Flags:	petersampsonaudacity: Test‑OK‑Win+ petersampsonaudacity: Test‑OK‑Mac+

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description James Crook 2015-05-19 17:57:20 UTC

[Seen with VST, presumed to affect the others too] Once loaded successfully the effect does not appear ticked in the 'More...' list, and cannot be removed.

Comment 1 James Crook 2015-05-20 04:19:49 UTC

This is a near duplicate of bug 945.  The two bugs need to be combined and one P1 bug emerge.

Comment 2 James Crook 2015-05-21 09:43:54 UTC

Reduced to P5 as this is only a problem if EXPERIMENTAL_EFFECT_MANAGEMENT is enabled.

Comment 3 Peter Sampson 2019-05-27 09:25:06 UTC

This mow works properly for VST on Win and AU on Mac with the newer Plug-in Manager