Bug 488 – VST scan interferes with opening a .aup file from the Finder

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

Audacity 3.0.3 development began 19th April 2021

Audacity Bugzilla

Bug 488 - VST scan interferes with opening a .aup file from the Finder


Summary:	VST scan interferes with opening a .aup file from the Finder

Status:	RESOLVED NOT-A-BUG

Product:	Audacity
Classification:	Unclassified
Component:	Application Core
Version:	2.0.0
Hardware:	Mac macOS

Importance:	P4 Repeatable
Assigned To:	Default Assignee for New Bugs

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2012-03-21 15:31 UTC by Bill Wharrie
Modified:	2018-08-20 11:51 UTC (History)
CC List:	4 users (show)

See Also:
Steps To Reproduce:	- default installation of Audacity 2.0.0 -- using Portable Settings folder (for convenience) -- no audacity.cfg file, no plugins.cfg file - start Audacity then quit -- plugins.cfg is created and is empty - double-click .aup file - opens fine - quit Audacity - add many VST effects to the plug-ins folder -- just so that the VST scanning process is visible - start Audacity -- scanning for VST effects takes place --- conclusion: the existence of VST effects in the plug-ins folder, combined with an empty plugins.cfg file triggers VST scanning. - quit Audacity - edit plugins.cfg to be empty - double-click a .aup file -- VST scanning takes place -- an empty project window opens --- conclusion: VST scanning on Mac interferes with opening a .aup file
Release Note:
First Git SHA:
Group:	---
Workaround:
Closed:	2018-08-20 00:00:00

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 Bill Wharrie 2012-03-21 15:31:06 UTC

When starting Audacity by double-clicking a .aup file, if a VST scan occurs then an empty project window is opened.

Comment 1 Bill Wharrie 2012-03-21 15:32:54 UTC

The VST scanning does not need to be long enough to trigger display of the "Scanning VST effects" window for the bug to occur.

Adding one and only one PPC-only VST effect to the Audacity plugins folder on an Intel machine will cause VST scanning on every launch. The existence of the VST effect combined with an empty plugins.cfg triggers the scanning, but because the VST effect is PPC-only nothing is written to plugins.cfg. The existence of at least one valid VST effect in any of the three locations Audacity looks in will cause something to be written to the plugins.cfg file, so VST scanning will not subsequently occur unless the user explicitly asks for it through the Effects Preferences.

Comment 2 Gale Andrews 2013-10-05 01:13:22 UTC

Bug description should apply to dragging files to the icon as well, and steps are no longer fully correct for 2.0.4 onwards so RESOLVED - INVALID. Replaced by bug 658.