Plugin incompatibility
Forum rules
This forum is for Audacity on Windows.
Please state which version of Windows you are using,
and the exact three-section version number of Audacity from "Help menu > About Audacity".
Audacity 1.2.x and 1.3.x are obsolete and no longer supported. If you still have those versions, please upgrade at https://www.audacityteam.org/download/.
The old forums for those versions are now closed, but you can still read the archives of the 1.2.x and 1.3.x forums.
Please state which version of Windows you are using,
and the exact three-section version number of Audacity from "Help menu > About Audacity".
Audacity 1.2.x and 1.3.x are obsolete and no longer supported. If you still have those versions, please upgrade at https://www.audacityteam.org/download/.
The old forums for those versions are now closed, but you can still read the archives of the 1.2.x and 1.3.x forums.
-
Piotr Grochowski
- Posts: 364
- Joined: Fri Jun 23, 2017 12:45 pm
- Operating System: Windows 10
Plugin incompatibility
The "Click Track" plugin I added to 2.1.3 now refuses to enable in 2.2.2. It does not give me any error — but it never appears on menu, and each time I come to Add / Remove Plug–ins... it is disabled.
Re: Plugin incompatibility
Which "Click Track plug-in"?
Where can I get this plug-in?
Are you aware that Audacity 2.2.2 has a click-track plug-in by default? It's called "Rhythm Track" http://manual.audacityteam.org/man/rhythm_track.html
Where can I get this plug-in?
Are you aware that Audacity 2.2.2 has a click-track plug-in by default? It's called "Rhythm Track" http://manual.audacityteam.org/man/rhythm_track.html
9/10 questions are answered in the FREQUENTLY ASKED QUESTIONS (FAQ)
-
Piotr Grochowski
- Posts: 364
- Joined: Fri Jun 23, 2017 12:45 pm
- Operating System: Windows 10
Re: Plugin incompatibility
I mean the plugin that used to exist on certain older Audacities. https://www.princeton.edu/~fanders/Auda ... cktrack.ny
The problem was not incompatibility, but that it was no longer in the folder for some reason. I remember adding it, back when I had 2.1.3.
The problem was not incompatibility, but that it was no longer in the folder for some reason. I remember adding it, back when I had 2.1.3.