plug-in scanning -ACID Product Family - MAGIX Community Forums Archive

Subject:plug-in scanning Posted by: edgar_farbosa Date:4/13/2004 9:04:41 PM okay this has been bothering me for a minute where exactly is acid scanning plugins from? I have Reaktor 4 and i want to use the DX plug capabilities but Acid refuses to scan in the plug. Why is it selective? Can I add in Reaktor DX manually? I used to be able to in acid 2 any help would be appreciated
Subject:RE: plug-in scanning Reply by: pwppch Date:4/14/2004 6:29:19 AM DX plugins are FX and are scanned using the Windows Registry, as defined by the DX specification for filters/plugins. Reaktor is a instrument, and ACID supports VSTi, not DXi. You cannot use the DX version of Reaktor in ACID. You must have either install Reaktor to the default VST install path or tell ACID to look at an additional directory for your VSTi plugins. Reaktor is installed to the default location normally, unless you told it otherwise. If this location changed, the you can tell ACID to for it preference pages for VSTi synths. Peter
Subject:RE: plug-in scanning Reply by: edgar_farbosa Date:4/14/2004 12:00:56 PM reaktor has dx plugin effects they actually work in an old sound forge i have (4.5) but not 7. Im not referring to the Vsti... those are easy to setup you can acutally manually browse them so i gotta know... why does sound forge 4.5 pick up the DX plugs from the registry but not Acid or Sound Forge 7.0. They are in there. Something else is wrong.
Subject:RE: plug-in scanning Reply by: pwppch Date:4/15/2004 9:22:04 AM Ok, now I know what you want. Forge 4.5 was released before DXi's were available. Some DXi's will crash and burn if they don't get all the DXi required calls/interfaces from the host. Others that are correctly designed an impelement as both DXi and DX filters behave and play nicely. Because of serious problems with MANY DXi's that were brain dead, we had to filter out DXi's from the available DX filter list in later versions of our hosts. There is no way to know which DXis will cause the problems, but enough of them did that we had to just prevent all DXi's from being exposed as DX filters. There is no work around for our latest versions. I will make sure that we take a second look at this now that DXis have been around for awhile. Perhaps the stability issue has improved. Peter
Subject:RE: plug-in scanning Reply by: edgar_farbosa Date:4/16/2004 1:18:05 AM ah yes i was noticing that sound forge 4.5 was picking up synths also, which would not really be useful as an effect! but i seem to distinctly remember running reaktor effects in real time in acid at some point. so theres no possibility of like faking acid into just scanning in the dxi's? thanks for you responses, btw

Subject:plug-in scanning

Date:4/13/2004 9:04:41 PM

okay this has been bothering me for a minute

where exactly is acid scanning plugins from? I have Reaktor 4 and i want to use the DX plug capabilities but Acid refuses to scan in the plug. Why is it selective? Can I add in Reaktor DX manually? I used to be able to in acid 2

any help would be appreciated

Subject:RE: plug-in scanning

Reply by: pwppch

Date:4/14/2004 6:29:19 AM

DX plugins are FX and are scanned using the Windows Registry, as defined by the DX specification for filters/plugins.

Reaktor is a instrument, and ACID supports VSTi, not DXi. You cannot use the DX version of Reaktor in ACID.

You must have either install Reaktor to the default VST install path or tell ACID to look at an additional directory for your VSTi plugins. Reaktor is installed to the default location normally, unless you told it otherwise. If this location changed, the you can tell ACID to for it preference pages for VSTi synths.

Peter

Subject:RE: plug-in scanning

Reply by: edgar_farbosa

Date:4/14/2004 12:00:56 PM

reaktor has dx plugin effects they actually work in an old sound forge i have (4.5) but not 7. Im not referring to the Vsti... those are easy to setup you can acutally manually browse them

so i gotta know... why does sound forge 4.5 pick up the DX plugs from the registry but not Acid or Sound Forge 7.0. They are in there. Something else is wrong.

Subject:RE: plug-in scanning

Reply by: pwppch

Date:4/15/2004 9:22:04 AM

Ok, now I know what you want.

Forge 4.5 was released before DXi's were available. Some DXi's will crash and burn if they don't get all the DXi required calls/interfaces from the host. Others that are correctly designed an impelement as both DXi and DX filters behave and play nicely.

Because of serious problems with MANY DXi's that were brain dead, we had to filter out DXi's from the available DX filter list in later versions of our hosts.

There is no way to know which DXis will cause the problems, but enough of them did that we had to just prevent all DXi's from being exposed as DX filters.

There is no work around for our latest versions.

I will make sure that we take a second look at this now that DXis have been around for awhile. Perhaps the stability issue has improved.

Peter

Subject:RE: plug-in scanning

Reply by: edgar_farbosa

Date:4/16/2004 1:18:05 AM

ah yes i was noticing that sound forge 4.5 was picking up synths also, which would not really be useful as an effect!

but i seem to distinctly remember running reaktor effects in real time in acid at some point. so theres no possibility of like faking acid into just scanning in the dxi's?

thanks for you responses, btw