Re the audio issue ... isn't Fairlight not all that different to Vegas Pro's existing audio editor? That is, they are both multi-track audio editors. Neither Vegas Pro's audio editing functions nor Fairlight are similar to SoundForge Pro simply because SFP is a single track (per window) multi-channel editor whereas VP's audio editor and Fairlight are, as mentioned before, multi-track up to 5.1 channel (in the case of Vegas Pro) audio editors. The Fairlight screen dump posted is in no way representative of SoundForge Pro's timeline - it is more like Vegas Pro's existing audio timeline.
There is already a direct link in Vegas Pro to SoundForge Pro via Options/Preferences/Audio - Preferred Audio Editor where SFP can be selected as the preferred audio editor if so desired.
@rock-c ... when asking for SoundForge Pro to be merged into Vegas Pro, how do you envisage this being done from a timeline workflow point-of-view? And from Vegas Pro's audio timeline, what/how do you envisage an integrated SoundForge Pro window being accessed - and for what purpose?
VEGAS Effects already is as "merged" with VEGAS Pro as it needs to be, they both function standalone but also have instant round trips between them, that's all I care for. Ditto is true for Sound Forge. Rather than have them try to shoe-horn all these other amazing apps into one single VEGAS app, I'd prefer they be able to be used standalone with an instant round trip to VEGAS. I do hope to see that integration tightened... it would be awesome if they could eventually figure out a way to live-preview changes made to vegas effects projects in a VEGAS Pro project, so I could animate directly onto projection mapped surfaces when doing my projection mapping... But other than that, I have no need for it to be the same app. If anything, that limits it.
I do like the idea of Vegas doing some more tabs to improve navigation between tasks.
One for editing, one for color grading (color grading panel as a quasi-Fx is awkward) and one for rendering would be wonderful (especially if you could queue renders and then batch execute.) For audio I'm not sure I see the need, but wouldn't be opposed to it.
The downside of integration is cost. If my choice is a $200 video editor or a $600 video, audio and post suite I really can't justify the cost of the latter for what I do.