I have a few thoughts on this, but they will be questions for your questions.
Where are you at any time running a 32-bit version of audacity and now running
a 64-bit version of audacity? If you are running a 64-bit version now, did you
uninstall and completely remove any trace of the software a plug-in from the 32
version? You are probably having residual problems. The reason I ask these
questions is that within your error it referenced program files X 86. This
means that audacity was in a 32-bit version on your computer. If I have
confused you, feel free to give me a phone call a little later today.
Ted Galanos
Accessibility analyst, custom audio creator and editor.
C. 713-298-1846.
G. 713-396-3495
Please consider a contribution to my Texas ABLE account.
https://www.ablegifting.com/TX/K9L8A2
Rare Patient Voice:
Want to get paid for your opinion? Rare Patient Voice wants to hear your story
through confidential surveys and interviews, and pay you on a $100 per hour
https://rarepatientvoice.com/TGalanos/
On Jun 2, 2022, at 9:21 AM, Mr. Leol Williams <leolw@xxxxxxxxxxxxx> wrote:
Hello, Leol Williams here!
Can someone please assist?
When enabling any plugins or applying effects to the audio tracks, I will
repetedly get these error message!
[Window Title]
Message
[Content]
Effect or Command at C:\Program Files (x86)\Audacity\plug-ins\KickMaker.dll
failed to register:
Could not load the library
[OK]
[Window Title]
Effect failed to initialize
[Main Instruction]
Attempting to initialize the following effect failed:
[Content]
GSnap
More information may be available in 'Help > Diagnostics > Show Log'
[OK]
The audacity4blind web site is at
//www.freelists.org/webpage/audacity4blind
Subscribe and unsubscribe information, message archives,
Audacity keyboard commands, and more...
To unsubscribe from audacity4blind, send an email to
audacity4blind-request@xxxxxxxxxxxxx
with subject line
unsubscribe