I have updated this page with the two new "... to mono" options - I think what I have written is accurate, but I am no expert.

I also updated the image as the default action has changed - but need to wait for Cloudfare to flush its cache before I can check (I have set a P2 reminder in the Manual).

I don't know if James will pull this page into the Manual for the released 2.3.3 - but I'm seriously doubting that he will want anther RC and another week's delay for this.  But until that happens, this bug must remain open.

And I'm struggling to understand why this warrants P1 release-blocking status.  I would have thought that P3 with a release note would have been more appropriate - or even P4.

I think P1 because we have pulled the (legacy) Vocal Remover effect from Audacity 2.3.3. As a consequence, users that have previously relied on the legacy effect are now forced to use the new effect. Due in part to limitations of Nyquist plug-ins interface, how to use the new effect is not obvious, so in my opinion it is essential that our documentation is accurate.

We already have a complaint on the forum due to a user not knowing how to use the new effect:

"I've compared 2 effects - Vocal remover gives the best results. Please return it to the list of effects. Secondly, these 2 effects are different in action and do not replace each other."

(In reply to Steve Daulton from comment #3)
Unfortunately it is worse than I thought. The current version of "Vocal Reduction and Isolation" does not work correctly.

According to the manual:

Remove Center Classic: (Mono): Removes all audio (the whole frequency spectrum) that is common to both left and right channels and returns a (dual) mono track.

However, it actually doesn't do that. It just prints a "help screen" and does not process the audio at all.

(In reply to Steve Daulton from comment #4)
>According to the manual:
>
>Remove Center Classic: (Mono): Removes all audio (the whole frequency spectrum) >that is common to both left and right channels and returns a (dual) mono track.

And that's exactly what it does on W10 for me.

I just tested on 2.3.3 RC02 with my touchstone track for stereo separation, the opening track of Sgt. Pepper's Lonely Hearts Club Band.

(In reply to Steve Daulton from comment #3)
>We already have a complaint on the forum due to a user not knowing how to 
>use the new effect:
>
>"I've compared 2 effects - Vocal remover gives the best results. Please return it >to the list of effects. Secondly, these 2 effects are different in action and do >not replace each other."

This is a separate issue to the bug as titled.

But note that it's only for new users (or possibly those that choose the reset when installing the 2.3.3 upgrade) that we have removed Vocal Remover in 2.3.3.

If you already have Vocal Remover in your earlier Audacity, when upgrading to 2.3.3 Vocal Remover will remain in your effects list.  So users who have got used to using it and prefer it should still have it.

Downgraded to P3 following offlist discussion with Steve

The Manula has been updated by Steve (and Peter)