Plugin scanning

Author
Post
Essentials Only Full Version
TabSel
Max Output Level: -85 dBFS
  • Total Posts : 284
  • Joined: 2011/02/15 04:32:33
  • Status: offline
2011/05/10 18:21:09 (permalink)

Plugin scanning

Sonar x1 x64, using x64 & x32 vst plugs, jbridge, automap... I have a folder ".../vst2 x32/..." for native x32 plugs and a ".../vst2 x64/..." for x64 plugs. Some plugs are available as both x32 and x64 plugs, mainly under the same name, but not all, for example "boost_11.dll" (x32) and "boost_11_64.dll" (x64), both having the same unique vst-id. I jbridge all x32 plugs to x64, so "boost_11.dll" gets "boost_11.64.dll" in folder "...jbridge/vst2 x64/..." I include both folders "...jbridge/vst2 x64/..." and ".../vst2 x64/..." in Sonars vst search path. Now, when I instantiate "boost_11_64", sonar loads the jbridged "boost_11.64.dll" , because it is the first scanned plugin with the same unique vst-id of "boost_11_64"... How can I have sonar instantiate the Plugin I choose, instead of the First Plugin in the Search path with the Same vst-id?
#1

2 Replies Related Threads
    Jim Roseberry
    Max Output Level: 0 dBFS
    • Total Posts : 9871
    • Joined: 2004/03/23 11:34:51
    • Location: Ohio
    • Status: offline
    Re:Plugin scanning 2011/05/10 18:44:27 (permalink)
    There's no need to bridge all 32Bit plugins via jBridge.
    Don't bridge the plugins that have native 64Bit dlls.
     
    FWIW...
    When refering to 32Bit code, you'd say x86 (not x32)  

    Best Regards,

    Jim Roseberry
    jim@studiocat.com
    www.studiocat.com
    #2
    bluzdog
    Max Output Level: -56 dBFS
    • Total Posts : 1928
    • Joined: 2007/10/06 17:15:14
    • Location: Lakewood, Colorado
    • Status: offline
    Re:Plugin scanning 2011/05/10 20:31:24 (permalink)
    Use the plug in manager and make folders to organize your plugs any way you like.
    #3
    Jump to:
    © 2024 APG vNext Commercial Version 5.1