I’ve been testing on Vista (SP2). Today after reading your post I tried to test one of the failing versions on Windows 7, but ran into a problem. I put the Audacity folder on the desktop as I normally do for testing, and since Channel Mixer doesn’t come with the zip I put it in Portable Settings\Plug-Ins, as I’ve been doing all along with Vista. After restarting, Audacity finds the .ny file, and I can enable it in “add/remove plug-ins”, but after clicking OK and re-opening the Effects list, it’s not there. When I go back to “add/remove plug-ins”, it’s disabled again.
I tried putting it in Audacity…\Plug-Ins, and Audacity didn’t find it. It finds the one in another installation of Audacity on the same computer, but not the one in its own folder. Also tried renaming the one in Portable Settings\Plug-Ins to *.yn. Audacity still shows a “channel-mixer.ny” in that folder, but there is none! If I enable the one it found in another Audacity folder, it’s disabled again when I reopen “add/remove plug-ins”.
I’m glad you spotted this problem DickN. Yes I can reproduce it on Windows (it does not occur on Linux). The problem is in Audacity rather than the plug-in.
A fix is on the way, but as a workaround you can use the Debug button instead of the OK button.
I have not followed the logic of why some externally issued plugins out in the wild like Channel Mixer still use a Debug button (and so now write to the Log). Is the intention to remove the Debug button from Channel Mixer?
I see no crashes in the fix in the Nightly Build. But I don’t like that now (part of the fix or very recent change?), once I have used the Debug button in Channel Mixer in a session, every time I then Press “Preview” I have to look at the Debug output first before I can hear the preview.
Debug should not persist beyond running the effect with the OK button.
Select an effect
Apply the effect using the Debug button. The effect is now in Debug mode
Select the effect again.
Press the Preview button. The effect is still in Debug mode and the Debug window appears before the preview plays.
Apply the effect with the “OK” button. The effect is no longer in debug mode, so the effect is applied without showing the Debug window.
Select the effect again.
Press the Preview button. The effect is not in Debug mode, so the preview is played without showing the Debug window.
The intention is that the Debug button should be used for debugging. “Release” plug-ins should be bug free, so there is no purpose for debugging, then, consistent with other types of effect, they will be released as “Release versions” without a debug button. The Debug button should be enabled in experimental, proof of concept and other plug-ins that are not yet release ready, so as to help reveal and locate bugs.
The logic has not changed, but improvements to the logging now reveals a behaviour that previously existed but was hidden. There are pros and cons to the behaviour now being revealed. The “pro” is that it is now possible to debug preview, whereas that was not previously possible. The “con” is that after using Debug, the debug window is enforced until cancelled by running the effect with the OK button, and users may not realise why that is happening - however, debugging is not intended for “users”, it is intended to be a tool for “developers”.