The CLSID dance

Author
Post
Essentials Only Full Version
ThJ
Max Output Level: -90 dBFS
  • Total Posts : 4
  • Joined: 2004/11/08 05:39:15
  • Status: offline
2004/11/08 05:48:14 (permalink)

The CLSID dance

Here's a problem I've been suffering a lot: I bring my projects to new SONAR installations and the plug-in CLSIDs don't match up anymore. Upon loading one project, SONAR spat the "Missing plug-ins" dialog at me. Clicking the "Online information" button hurled up the following information:

The following plugins were missing from your project.

Plugin: Sonitus:fx Modulator (Track: ''Strings out'')
NO MATCH
CLSID: 5CEE8F1A-1B27-4595-8442-D9FEDA29C0AC

Plugin: Sonitus:fx Delay (Track: ''Vocal'')
NO MATCH
CLSID: D3154A3D-551B-4421-9D45-F12068D35ED2

Plugin: Sonitus:fx Gate (Track: ''Vocal'')
NO MATCH
CLSID: 0CC0D2A0-4F21-40DA-B5BC-AC533346DA0C

Plugin: Sonitus:fx Reverb (Bus: ''Reverb'')
NO MATCH
CLSID: 0F050EB4-EF74-4363-9A56-E7E7B9368510

I will make hunka burnin' love to the person who shows me how to solve this all-time classic. I already made an attempt at editing the registry, changing the CLSIDs for the plug-ins in question to their predecessors' values. This didn't work, so I undid all my changes, and here I am. Help?

SONAR developers: Can you please add:
a) an automatic name-based plug-in search on load?
b) a dialog for matching project plug-ins up against installed plug-ins?
< Message edited by ThJ -- 11/8/2004 6:07:45 AM >
#1

5 Replies Related Threads
    togo59
    Max Output Level: -86 dBFS
    • Total Posts : 218
    • Joined: 2004/07/22 09:05:11
    • Status: offline
    RE: The CLSID dance 2004/11/08 07:31:01 (permalink)
    Hi,

    A complete uninstall/reinstall should matchup the registry entries. I am sure you do know what you're doing but for most people the registry is a no-go area for obvious reasons.

    If you're brave, you could use something like "Registry First Aid" from http://www.rosecitysoftware.com/Reg1Aid/ but be careful, these things are very good at things like deleting broken links, which is good, but they don't join up things that need to be joined up, i.e. they can be destructive without being constructive.

    Nevertheless, I have used the above and in all but one case (a disaster from which I recovered the computer after a lot of hard work) it has been brilliant. But you'll have to buy it (not expensive) 'cus the free demo only fixes about 14 links -- useless!

    So (and don't take me to court if I'm wrong) I would:
    Save all your projects and stuff to a safe area,
    Uninstall Sonar completely
    Optionally, Run Registry First Aid (and say yes to all the backups etc it offers you)
    Re-install Sonar

    Hope it helps.

    ...ping?

    Sonar has charms to soothe the savage breast. 
    #2
    adrian.crossan
    Max Output Level: -78 dBFS
    • Total Posts : 647
    • Joined: 2003/11/05 18:15:04
    • Location: Liverpool, UK
    • Status: offline
    RE: The CLSID dance 2004/11/08 07:42:34 (permalink)
    I'd try this first, open a command prompt and run regsvr32 on the affected plugins. E.g.

    regsvr32 "C:\Program Files\Cakewalk\Shared Plugins\Sonitus FxModulator.dll"


    The file names are obvious so you should be able to match the plugin to the file easily enough.
    #3
    ThJ
    Max Output Level: -90 dBFS
    • Total Posts : 4
    • Joined: 2004/11/08 05:39:15
    • Status: offline
    RE: The CLSID dance 2004/11/08 09:17:55 (permalink)
    I think I'm beginning to figure out a couple of things. Firstly, this happened when I upgraded from SONAR 3 to SONAR 4. It seems that the plug-ins have changed names slighly... For instance, SONAR 4 uses "SonitusFxReverb.dll" whereas SONAR 3 used "Sonitus fxReverb.dll" and "SonitusFxReverbDX.dll" (the names are probably not 100% accurate).

    When I installed SONAR 4, certain Sonitus:fx plugins stopped working. They were in the list, but were displayed as placeholders. Then I removed both versions, and re-installed SONAR 4. All the plug-ins now showed up doubled in the Sonitus:fx menu, with half of them displaying placeholders instead of real plug-ins. I went into the registry and removed the bad ones. Now everything is all right, all plug-ins working, but projects I made with the 'tainted' SONAR 4 now have trouble loading, presumably because the SONAR 3.x plug-ins were used instead of the 4.x ones.

    What I suspect has happened is that Cakewalk haven't provided me with a 100% smooth upgrade path. While the plug-ins were still branded with Sonitus:fx graphics in 3.x, they've changed it to say "Cakewalk" now. The company who made the effects have ceased to exist, I believe. I'm guessing Cakewalk or someone else bought the suite (wise decision) and changed minor things, resulting in the plug-ins having other CLSIDs in SONAR 4 than SONAR 3.

    The registry settings, down to how the presets are stored, seem identical. It should be trivial to make the newly branded plug-ins work with projects made with the previous plug-ins. I just don't know quite what to tweak...
    < Message edited by ThJ -- 11/8/2004 9:26:36 AM >
    #4
    JohnIsa
    Max Output Level: -90 dBFS
    • Total Posts : 15
    • Joined: 2004/11/28 12:42:43
    • Status: offline
    RE: The CLSID dance 2004/11/28 14:41:38 (permalink)
    ThJ
    did you ever solve your problem? experiencing the exact same issue.
    #5
    ThJ
    Max Output Level: -90 dBFS
    • Total Posts : 4
    • Joined: 2004/11/08 05:39:15
    • Status: offline
    RE: The CLSID dance 2004/11/28 14:49:20 (permalink)
    No, I'm afraid not. I just clenched my teeth together and used the new plugins instead. This is an issue the Cakewalk developers need to solve.
    #6
    Jump to:
    © 2025 APG vNext Commercial Version 5.1