SF Plugins startup necessary at system boot? -Sound Forge - PC

Subject:SF Plugins startup necessary at system boot? Posted by: NarratorsAudio Date:5/1/2013 1:47:47 PM I've just started using Autoruns to try to trim down unnecessary startup applications, and I find a load (all?) of my Sound Forge plugins in the registry at HKLM\Software\Classes\Filter. My knowledge of startup requirements is minimal at best, but it seems odd that plugins would need to be launched upon computer startup, rather than just SF application startup. Can anyone advise me on this? Thanks in advance. -- Judith
Subject:RE: SF Plugins startup necessary at system boot? Reply by: rraud Date:5/1/2013 2:46:27 PM Can you elaborate? Plugins, VSTs in particular, are not normally queried until SF starts and then that only takes about a second. If SF set to launch at system start, that would be normal, though it should not slow things down significantly. Perhaps a media player application is 'loading' the plugs at system start-up.
Subject:RE: SF Plugins startup necessary at system boot? Reply by: SonySQAPete Date:5/1/2013 3:37:56 PM You don't load those at boot. They're in the codecs tab for a reason - they're registered directx plugins. (DirectX plugins share some lineage with Directshow filters, hence their location.) Autoruns can display quite a bit more than just startup information. It'd seem that autoruns lists our plugins as a result of them being globally-registered components that could, in theory, be loaded by another application. http://forum.sysinternals.com/search_results_posts.asp?SearchID=20130501215320&KW=DirectShow Modifying those entries could cause issues with those plugins. Please don't modify registry entries unless you're certain that you know what you're doing. Message last edited on5/1/2013 4:02:06 PM bySonySQAPete.
Subject:RE: SF Plugins startup necessary at system boot? Reply by: J. Date:5/1/2013 4:03:32 PM Plugins, VST or DirectShow, do not load themselves. They are just libraries. In this case, as in the codec case, they are globally discoverable objects that could be loaded by any app that looks for such things. Not sure why sysinternals chose to list them, but they aren't doing anything by themselves. J. Message last edited on5/1/2013 4:07:12 PM byJ..
Subject:RE: SF Plugins startup necessary at system boot? Reply by: Geoff_Wood Date:5/5/2013 6:16:18 AM A little knowledge can be a dangerous thing. Your plugins are not being loaded. They are being scanned so that SF knows that they exist. Don't change anything there ! geoff

Subject:SF Plugins startup necessary at system boot?

Date:5/1/2013 1:47:47 PM

I've just started using Autoruns to try to trim down unnecessary startup applications, and I find a load (all?) of my Sound Forge plugins in the registry at HKLM\Software\Classes\Filter.

My knowledge of startup requirements is minimal at best, but it seems odd that plugins would need to be launched upon computer startup, rather than just SF application startup.

Can anyone advise me on this?

Thanks in advance.

-- Judith

Subject:RE: SF Plugins startup necessary at system boot?

Reply by: rraud

Date:5/1/2013 2:46:27 PM

Can you elaborate? Plugins, VSTs in particular, are not normally queried until SF starts and then that only takes about a second. If SF set to launch at system start, that would be normal, though it should not slow things down significantly. Perhaps a media player application is 'loading' the plugs at system start-up.

Subject:RE: SF Plugins startup necessary at system boot?

Reply by: SonySQAPete

Date:5/1/2013 3:37:56 PM

You don't load those at boot.

They're in the codecs tab for a reason - they're registered directx plugins. (DirectX plugins share some lineage with Directshow filters, hence their location.) Autoruns can display quite a bit more than just startup information.

It'd seem that autoruns lists our plugins as a result of them being globally-registered components that could, in theory, be loaded by another application.

http://forum.sysinternals.com/search_results_posts.asp?SearchID=20130501215320&KW=DirectShow

Modifying those entries could cause issues with those plugins.

Please don't modify registry entries unless you're certain that you know what you're doing.

Message last edited on5/1/2013 4:02:06 PM bySonySQAPete.

Subject:RE: SF Plugins startup necessary at system boot?

Reply by: J.

Date:5/1/2013 4:03:32 PM

Plugins, VST or DirectShow, do not load themselves. They are just libraries. In this case, as in the codec case, they are globally discoverable objects that could be loaded by any app that looks for such things.

Not sure why sysinternals chose to list them, but they aren't doing anything by themselves.

J.

Message last edited on5/1/2013 4:07:12 PM byJ..

Subject:RE: SF Plugins startup necessary at system boot?

Reply by: Geoff_Wood

Date:5/5/2013 6:16:18 AM

A little knowledge can be a dangerous thing. Your plugins are not being loaded. They are being scanned so that SF knows that they exist. Don't change anything there !

geoff