Jump to content
Sign in to follow this  
razor7music

Removing Sonar Lingering Remnants

Recommended Posts

Hello All

I tried for the last time to get V-Vocal and Pentagon I to work in CW. I'd like to keep them in the tool belt if I could, but I don't need them enough to spend any more time trying to get them to work.

So, how do I remove V-Vocal from appearing in my region FX list and how do I remove Pentagon I from my soft synth/sampler list? I think I get rid of Pentagon I from my vst plug in manager, but not sure.

Any help is appreciated! 

Share this post


Link to post
Share on other sites

I don't really think there is much reason to remove them. I still have them too as I always install bare bones 8.5, X3 then Splat. I have never used V vocal ( or Melodyne) and I don't even think about them. I have used Drum Replacer a few times. But I could never get V Vocal or Melodyne to work so I just leave them be. 

And I must have a dozen VST instruments I never use. They too cause no issues. I just looked and I don't see Pentagon. I guess I don't check the box during my custom installs of the old versions. 

Share this post


Link to post
Share on other sites

Both may be unregistered using regsvr32

I am curious though, what is the problem with Pentagon I?

 

Share this post


Link to post
Share on other sites
5 hours ago, scook said:

Both may be unregistered using regsvr32

I am curious though, what is the problem with Pentagon I?

 

I get a cryptic error message that it's corrupted or not installed correctly. I'll post a screenshot when I'm back in studio.

Thanks for the unregister tip. That's how I've been trying to register the dll's. I didn't realize that's how you get rid of them appearing in CW.

Share this post


Link to post
Share on other sites
11 hours ago, John Vere said:

I don't really think there is much reason to remove them. I still have them too as I always install bare bones 8.5, X3 then Splat. I have never used V vocal ( or Melodyne) and I don't even think about them. I have used Drum Replacer a few times. But I could never get V Vocal or Melodyne to work so I just leave them be. 

And I must have a dozen VST instruments I never use. They too cause no issues. I just looked and I don't see Pentagon. I guess I don't check the box during my custom installs of the old versions. 

Just to unclutter my UI.

Melodyne has been sketchy ever since a couple of CW updates ago, but if I re-analyze the audio I can get it to work well. Haven't needed V-Vocal since I use Melodyne.

Share this post


Link to post
Share on other sites
13 minutes ago, razor7music said:

I get a cryptic error message that it's corrupted or not installed correctly.

There is an easy fix for this.

It is a permissions issue.

Right-click on

HKEY_LOCAL_MACHINE\SOFTWARE\rgc:audio Software\Dxi\Pentagon I

and give Users "Full Control" like this -

FfDNVeu.png

Share this post


Link to post
Share on other sites

Thanks @scook

I gave the Shared DXi folder and all the subfolders and files Users full control. When I try to register the dlls, I get these errors (first two)

When I try to unregister, I get the 3rd error.

 

Register 1.png

Register 2.png

Unregister.png

Share this post


Link to post
Share on other sites

If Pentagon is visible to CbB there is no need to mess with regsvr32. The plug-in is registered. This happens with all bundled DX plug-ins at install time.

 

The typical problem with Pentagon occurs when trying to add it to a project

5cFTsGi.png

The fix is to give Users "Full Control" in  HKEY_LOCAL_MACHINE\SOFTWARE\rgc:audio Software\Dxi\Pentagon I  as shown in image above

There is no need to mess with anything else.

Alternately running CbB as administrator works too but changing the one entry in the registry is all that is really needed.

 

The last regsvr32 error seems to indicate the command may have been issued with no quotes around a path containing spaces. Like

regsvr32 /u c:\program files\somepath\somefile.dll

instead of

regsvr32 /u "c:\program files\somepath\somefile.dll"

Command line tools use spaces to parse input. To minimize these types of errors, I like to use regsvr32 in the folder containing the dll.

 

But again. the usual solution to getting Pentagon working has nothing to do with regsvr32. That part is done properly at install time unless one receives the DLL/OCX error during install mentioned in the thread below.

 

Share this post


Link to post
Share on other sites
Posted (edited)
11 hours ago, scook said:

If Pentagon is visible to CbB there is no need to mess with regsvr32. The plug-in is registered. This happens with all bundled DX plug-ins at install time.

 

The typical problem with Pentagon occurs when trying to add it to a project

5cFTsGi.png

The fix is to give Users "Full Control" in  HKEY_LOCAL_MACHINE\SOFTWARE\rgc:audio Software\Dxi\Pentagon I  as shown in image above

There is no need to mess with anything else.

Alternately running CbB as administrator works too but changing the one entry in the registry is all that is really needed.

 

The last regsvr32 error seems to indicate the command may have been issued with no quotes around a path containing spaces. Like

regsvr32 /u c:\program files\somepath\somefile.dll

instead of

regsvr32 /u "c:\program files\somepath\somefile.dll"

Command line tools use spaces to parse input. To minimize these types of errors, I like to use regsvr32 in the folder containing the dll.

 

But again. the usual solution to getting Pentagon working has nothing to do with regsvr32. That part is done properly at install time unless one receives the DLL/OCX error during install mentioned in the thread below.

I checked the permissions in the folder security settings. I'll check it in the registry.

Thanks!

Edited by razor7music

Share this post


Link to post
Share on other sites

The Pentagon problem is strictly a registry issue.

The program was never modified to allow for security changes made in Vista.

 

  • Thanks 1

Share this post


Link to post
Share on other sites
8 hours ago, scook said:

The Pentagon problem is strictly a registry issue.

The program was never modified to allow for security changes made in Vista.

 

That totally worked!! Thanks!

Somewhere in the troubleshooting process V-Vocal was fixed too. I did so many things I don't know which one worked, but thanks again!!

Share this post


Link to post
Share on other sites
Posted (edited)
On 5/29/2020 at 8:39 AM, scook said:

The Pentagon problem is strictly a registry issue.

The program was never modified to allow for security changes made in Vista.

 

BTW @scook -- Any idea if this might also be why z3ta won't load? Do you know where the default location of those reg keys are?

Edited by razor7music

Share this post


Link to post
Share on other sites

Z3ta+ is a VST plug-in and does not have the same permissions problem Pentagon I has.

Not familiar with a loading issue with the plug-in.

  • Thanks 1

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
Sign in to follow this  

×
×
  • Create New...