I use pro tools to edit all my SFX recordings and was wondering why some people use Pro Tools and a separate wave editor. I was looking at http://www.audiofile-engineering.com/waveeditor/ and can't seem to find anything special that it does that pro tools can not.
I use izotope RX as a wave editor, and it works wonderfully (though I wish I could crossfade in there).
Really, the reason to use a wave editor is to bypass a couple of things you always have to do in a DAW situation:
1)create a new session 2)export or otherwise output sounds
By using a wave editor you just dive into the sound and start hacking. apple+s when you're done and move on. this means if you just need to cut up chunks of a take, remove slates, do some EQ, or pull out a couple of annoying blips in the sound you can do so without any import or export steps.
Also, destructive batch editing if that's your thing.
I use BIAS Peak Pro (sometimes happily, sometimes not) for the same reasons that Rene outlined: Immediacy. It's simply a question of the right tool for the right context. If I'm editing a single sound for my own library, it's into the stereo wave editor I go. If I'm designing something complex enough to require multiple tracks, I dive into a DAW.
Don't make the assumption that a wave editor will have more functionality than a DAW; it's quite the opposite. These lines are sometimes blurred, too. For example, Pro Tools, iZotope RX, Soundminer v4 Pro, and Adobe Audition have significant functional overlaps, but each is really good at extremely different things (DAW, audio surgery, library/DB, and wave editing, respectively). An analogy would be how any digital painter will of course have Painter, but they'll also have Photoshop, and probably Alias Sketchbook. Different tools for different contexts, even though there's some overlap.
I use AE Waveeditor along with Ardour or Ableton Live depending on the project. Neither of those DAWs have any real wave editing capability, but I can vouch for Waveeditor's smooth workflow, and I'm sure that this is the reason that people use a dedicated wave editor when the task at hand is so specific. Waveeditor is interesting since it more closely resembles photoshop than other wave editors, and I find this allows more flexibility to be creative. In particular the layering workflow (of effects, and of multiple files) is well suited to the task of readying wave files to be dropped into your favourite DAW's sequencer. Although this can be achieved by other methods, including within pro tools. Wave editor's only real con is that it uses a fair amount of the cpu, and updates seem to be slow going, the next of which is said to dramatically reduce cpu usage, but seems to have been in beta forever. If you're at home using pro tools, then there's probably no reason to get a dedicated wave editor.
I use Soundtrack Pro for just about all destructive editing. It provides some features that I don't get elsewhere, can run scripts and batches and gives me access to all of my AU effects, plus the awesome Logic-only stuff like Space Designer, Delay Designer etc. Plus it's built specifically for the waveform editing, so it's efficient and "just works".
It is just speed and taste. Wave editors are brilliant for working on single files without having to import and bounce to disk. It can also be a bit like choosing between different mics or analog gear, the colouration is slightly different depending on the algorithms and I find that I often have to be more drastic with the EQ in Pro Tools compared to wave editors.