Waves Plug-in Freaking Out

[smrp]

I have a session with using S1. When I try to open it it gives me an error. When I go into the plugins folder I don't see S1 so I can't just throw it away. My mix is done but not yet bounced and I dont' want to lose my mix.

How can I get this crappy thing out of the session?

[abbyin3d]

This is an old post from Disco Doctor regarding removing plugins from a session:

Here is how to remove plugins from a session using ResEdit. I decided to
post this after I received about twenty emails asking me how to do this.
As some of you know, the DSP manager is still prone to crashing when
trying to reopen a large Pro Tools session that is maxxing out all of your
available DSP. Until the DSP manager is fixed, this is (as far as I can
dream up) the quickest and easiest way to successfully reopen such a
session. This trick works perfectly. However, you should ALWAYS do this to
a COPY of your session file. Duplicate your session in the Finder (click
on it and press command-D) so you have a safety copy.
(Please note - I have NO knowledge of how the Pro Tools application code
was actually written - I just hacked away at a Pro Tools session with
ResEdit until I figured out how to do this. Keep that disclaimer in mind
when you do this. Having said that - I've done this several times and have
not experienced any kind of subsequent corruption in a session. This is
perfectly safe if you do it right.)
The first part of this post is a detailed explanation of how to do this,
which makes the whole process sound complicated. The second part is the
simple step by step process. It's very easy to do this, but I wanted to
describe it in explicit detail for people just in case they have no
ResEdit experience. Let me know if I did a bad job explaining all of this.

Detailed Lesson: How to remove plugins from a session with ResEdit
----------------------------------------------------------------------
First get acquainted with this process by trying this on a new empty
session. Make a new session in Pro Tools. Add three audio tracks. Then add
one plugin to each audio track. It doesn't matter what plugins you add for
this lesson, but I suggest any plugin other than the stock Digidesign
plugins. You'll see why later on.
Now open the session with ResEdit. To do this, just drag and drop the
session file (you made a safety copy of it, right?!!!) onto ResEdit.
You will now see a window with a list of icons with funny four letter
names. These are "resource types". The three resource types we will be
dealing with are named:
FxNm
FxTD
PISt
Double click the FxNm resource. If you added three plugins to your test
session, you should now see three numbers in a list that say something
like 1000, 1012, 1013. These are the actual FxNm "resources". The numbers
are called "Resource ID's". It doesn't matter if the ID numbers I just
mentioned aren't the exact numbers you see, but all of the numbers should
be 1000 or higher. Double click the first ID number in the list.
Now look at this new window - you should see several rows of hexadecimal
numbers, and over to the right there's some text corresponding to the
hexadecimal numbers. In that block of text you should see the name of the
plugin on the first audio track in your test session. For example, if you
added a 4 band Focusrite d2 to the first audio track, you'll see this text
in the window (minus the quotes):
"ff d2 4-bandp"...and the text will be surrounded by a bunch of other
nonsense characters.
If the plugin you added on the first audio track was a TC Megaverb you
would see:
"TCMegaverb"...in the list with a bunch of other nonsense characters.
The point is that this FxNm resource represents the actual plugins in the
session. When you have a maxxed out session with 50 plugins in it, the
order of the plugins in the session, from left to right, will roughly
correspond to the numbered list of resource ID's in the FxNm resource. In
other words, resource ID# 1000 (or whatever the lowest numbered resource
is) of FxNm will probably be the first plugin in your session. You
determine that for sure by opening the resource as I just described above
and looking for the name of the plugin within the resource ID text. With a
big session, you'll be hunting a little bit - but it's not that hard. For
example, if you keep your reverbs, choruses, and delays to the left of the
mixer along with the master fader the way I do, then it'll be easy to find
a TC Megaverb that you want to delete. Just double click the first few
resource ID's in FxNm until you see TC Megaverb. When you find it, write
down the resource ID number.
The FxTD and PISt resources contain the exact same list of resource ID
numbers that FxNm has. They contain other information about the same
plugin (as far as I can tell). So in this test session, if the first
plugin in your test session has resource ID# 1000 in the FxNm resource
list, there will also be a resource ID# 1000 in the FxTD and in the PISt
resource lists.
I've probably made this sound complicated. But don't worry. It's not! Keep
reading!
So now, using your test session which you already have open in ResEdit -
do the steps below starting with Step #2. Once you do this, you'll
understand all of this.
----------------------------------------------------------------------
10 Really Easy Steps for Removing a Plugin with ResEdit
----------------------------------------------------------------------
1) Open the Pro Tools session file within ResEdit by dragging and dropping
the session file onto the ResEdit application
2) Double click the resource type FxNm
3) Double click the resource ID numbers one at a time and examine the text
in the resource until you find the plugin you want to delete (identified
by the plugin name in the resource text). If the resource you opened is
not the one you want to delete, just close the resource window (command-W)
and double click the next resource ID number in the list.
4) You found the plugin that you want to delete? Good. Now WRITE DOWN the
resource ID number (i.e. - 1012) and close the resource window.
5) Now highlight that resource number in the FxNm resource ID list by
clicking on it once and then press DELETE. Close the FxNm resource window.
6) Now find the FxTD resource in the main resource types window (again -
that's the main ResEdit window with all the icons). Double click it.
Again, you will see a bunch of resource ID numbers starting at 1000 or
higher.
7) Find and highlight the SAME resource ID number in this window that you
just wrote down and press DELETE. Close the FxTD resource window.
8) Open the PISt resource in the main resource types window
9) Again, highlight the SAME resource number in this window that you just
wrote down and press DELETE. Close the PISt resource window.
(NOTE: Did you screw up and delete the wrong resources? Did you forget to
make a safety copy of the session?? No big deal! BEFORE you save your
changes, you can select "Revert file" from the File menu in ResEdit and
everything you changed will be reverted to its original condition. And
next time make a safety copy!!)
10) Now save the changes you made and quit ResEdit.
-----------------------------------------------------------
That's it! Now try opening the session you just modified in Pro Tools. If
you did everything correctly, and the plugin you removed was a "whole
chip" plugin, then your session should open sans one plugin. This is of
course assuming that nothing else is wrong with your system. I've done
this a dozen times - so I know it works!
I want to stress that it is important to delete the right type of plugin
to make this work. If you have fifty d2's in your session, thirty d3's,
twenty Waves plugins, three Megaverbs, three Amp Farms, and two Lexiverbs,
and the session was maxxing out your DSP, and you delete one of the d2's,
the session probably isn't going to reopen. You need to remove a "whole
chip" plugin. At the beginning of this post I suggested that you don't use
stock Digidesign plugins while experimenting with removing them in
ResEdit. The reason is because some of them don't have an easily
identifiable text description within the FxNm resource. The other reason
is that deleting a stock Digidesign plugin from a session probably won't
help you reopen the session.
THREE IMPORTANT THINGS you really need to keep track of until Digidesign
fixes the DSP Manager:
1) Always SAVE your plugin settings before closing your session. This way
you can pull plugins out of the session with this ResEdit trick, get it
opened up again, and then put the plugins back the way they were once you
get the session open again.
2) Try to keep track of what the last few plugins you added to your
session were prior to closing it. For example, if you opened your session
and worked on it for four hours, and in that time you added two Lexiverbs,
and now it won't reopen, you can safely bet that removing one of those
Lexiverbs will allow you to get the session open again.
3) BE AWARE that if you delete a plugin using this ResEdit technique and
there was automation on that plugin - IT IS GONE FOREVER. Hopefully you
remember which plugins were automated and which were not, and you can try
deleting one of the unautomated plugins. Also be aware of the fact that if
you remove a "mono to stereo" plugin that was on an audio track or aux
channel (i.e. - TC Megaverb mono/stereo) then any automation on other
plugins on that channel may be lost because the channel will revert back
to mono. The actual rule here is: Plugin automation on a plugin that is
inserted before (above) the "mono to stereo" plugin will NOT be lost, and
plugin automation on a plugin inserted after (below) the "mono to stereo"
plugin WILL be lost.
That's it! I know I made all of this sound a bit complicated, but when you
open up a session in ResEdit and do it a few times, you'll see that it
takes about 15 seconds once you get the hang of it. Unlike the
Tracktransfer tricks that exist for "fixing" sessions that won't reopen,
you will be able to retain all of your playlists, groups, I/O labels, and
unused regions by using this technique. That's why I bothered to figure
all of this out! I couldn't reopen a very large and complex session - and
the playlists were absolutely essential to completing the mix.
Wouldn't it be nice if it all just worked?
Good luck.
-Disco Doctor

PS - If you use this tip and it helps you out, then you are morally
obligated to start making some noise on the user conference about the
problems that exist with the DSP Manager!! I wasn't even going to bother
posting this tip on the user conference until about twenty people emailed
me tonight saying they are having the same problems and could I please
tell them how to remove plugins with ResEdit. Tell Digidesign damnit!! And
tell them LOUDLY - or it's going to be a looong time before the DSP
manager works reliably.

[This message has been edited by abbyin3d (edited July 03, 2000).]

[DigiTechSupt]

smrp
Remember that Waves plug-ins are stored
in the Waves plug-ins folder and not in the DAE plug-ins folder. Also a easy way to
pull the waves plug-ins from a session is
to simply pull the waves-shell DAE plug-in
from the DAE plug-ins folder, then launch the
session and save a session copy. That way you have a session you can open and the original
session intact. Also trash the waves prefs in the system folder/preferences. Also waves has made improvements to there waveshell and it is a good idea to update the waves bundle and
wave shell DAE to ver. 2.8.1
MJ