Ok, that was correct - thanks, and my bad for being in a hurry, what with
reloading new machine...<smile>
One other thing though is, if I copy in a chain file from previous
installation, which, for example, uses vocoder, when I try to apply it to a
track, audacity is telling me:
Your batch command of Vocoder... was not recognized.
Suppose can just redefine chain, but, wonder what's changed across
installations.
Stay well
Jacob Kruger
Blind Biker
Skype: BlindZA
"Roger Wilco wants to welcome you...to the space janitor's closet..."
----- Original Message -----
From: David Engebretson Jr.
To: audacity4blind@xxxxxxxxxxxxx
Sent: 09 December, 2015 8:05 PM
Subject: [audacity4blind] Re: Latspa plug-ins, etc.
Some effects are only available if you have some audio selected. Any chance
there's no audio selected?
Sometimes there is a bit of a mystery when Audacity decides to deselect
audio. Even after applying certain effects and saving files the previously
selected audio will deselect itself. I haven't nailed down the sequences to
make it happen consistently but, if I could stop recording new material, I
would do more strenuous testing.
Best,
d
From: Jacob Kruger
Sent: Wednesday, December 09, 2015 12:04 AM
To: audacity4blind@xxxxxxxxxxxxx
Subject: [audacity4blind] Latspa plug-ins, etc.
While in past could just install all the latspa plug-ins in one go, and have
audacity scan them, and work with them, now with a new installation of audacity
2.1.1 on a new machine, while can install latspa plug-ins package, and while
some of them are now available, some of the others are showing up under effects
menu, but, are showing up as disabled.
For example, it now tells me vocoder effect is there, but disabled?
Is this a version compatibility issue, or have I forgotten some other part of
process that could/should have handled, etc.?
TIA
Jacob Kruger
Blind Biker
Skype: BlindZA
"Roger Wilco wants to welcome you...to the space janitor's closet..."
