I installed ffmpeg. Did not help with Chordino. I also installed the avformat-55.dll file. That didn’t help either.
I neglected to include the log, so it’s attached here.
log.txt (3.31 KB)
I’ll try deleting the cfg file again.
Thanks for all of your help. Hopefully, the issue will get resolved.
FFmpeg has nothing to do with Chordino or installation/detection of any plugin types.
Gale
I’m only going by what I’ve read in a few places on the Internet. Here are a few examples. I thought this could be the solution, but you may be right in that plugins are not mentioned in these posts:
“The optional FFmpeg library allows Audacity to import and export a much larger range of audio formats including M4A (AAC), AC3, AMR (narrow band) and WMA and also to import audio from most video files.
Because of software patents, Audacity cannot include the FFmpeg software or distribute it from its own websites. Instead, use the following instructions to download and install the free and recommended FFmpeg third-party library”.
Also: https://www.youtube.com/watch?v=_1rcvBerl9k
And ffmpeg for Audicity for windows: http://ffmpeg-for-audacity-on-windows.software.informer.com
And:
"The optional FFmpeg library allows Audacity to import and export a much larger range of audio formats including M4A (AAC), AC3, AMR (narrow band) and WMA and also to import audio from most video files.
Because of software patents, Audacity cannot include the FFmpeg software or distribute it from its own websites. Instead, use the following instructions to download and install the free and recommended FFmpeg third-party library.
Warning icon FFmpeg 2.2.2 for Windows and Mac from the links below should be used with the latest version of Audacity.
The previous FFmpeg 0.6.2 for Audacity will not be recognized by Audacity 2.0.6 and later, and FFmpeg 2.2.2 will not be recognized by Audacity versions before 2.0.6.
FFmpeg 2.3.x shared libraries should also be recognized by Audacity 2.0.6 and later. FFmpeg 2.4.x and later is not supported, except for exports using Audacity’s command-line encoder.
Advanced usage: If you already have Audacity-compatible FFmpeg 2.2.x or 2.3.x shared libraries in the system PATH, Audacity will use those as long as you don’t install FFmpeg from the links below and as long as you don’t specify the FFmpeg you want Audacity to use in Libraries Preferences".
There are many more sites that describe the relationship between Audacity and ffmpeg. I’m not an expert, but I thought I’d give ffmpeg a try based on these readings.
Beats me.
It’s interesting that I reverted back to the original Windows 10 setup that came with the computer to see if Chordino would install properly in Audacity. Most everything was uninstalled and it was basically a fresh Win 10 installation. No other programs installed. Bare bones. I then installed Audacity and Choirdino (in its proper Vamp folder).
…and once again, Audacity did not find and install Chordino. I almost feel like sending you good folks my computer for analysis.
It’s too bad because I would have loved to use Chordino on this super-fast machine.
Anyway, I’ve processed a bug report to the Audacity people…and I’m not sure if they are the same folks that are on this forum. Hopefully, we can get other opinions, but if not, life goes on.
I was finally able to load Chordino and a couple other Vamp plugins.
I removed everything…Audacity and all plugins.
Installed Audacity again.
Went to load Chordino by going in to "Add remove plugins.
This time, Chordino was indeed listed.
I enabled Chordino and closed out.
Reopened "Add remove plugins.
Chordino was once again listed as “NEW”. I had a glass of Scotch.
This time I clicked on the “New” circle on the upper right, which showed only “New” plugins (not enabled).
Then I enabled the three Chordino plugins that were listed.
Closed out and reopened and THIS TIME CHORDINO REMAINED ENABLED. Had another glass of Scotch.
Apparently, you need to isolate the “NEW” plugins first and then enable them. At least, this worked for me.
Also, when I attempted to load the qm Vamp plugins, an automatic bug report was generated and I could no longer
access Audacity. When I removed the three qm plugin files from (x86) Vamp Plugins folder, Audacity worked fine.
In my case at least, Audacity does not like the qm plugins.
Hopefully, Chordino will remain active in Audacity, as well as other Vamp plugins that I intend to install.
Thanks to Gale and others for their tireless efforts in troubleshooting this issue.
Did you remove pluginregistry.cfg?
Just to clarify for others’ benefit, no-one else has ever reported that. Most or all users will simply be able to enable Chordino in the “All” section of Plug-in Manager, as I have done several times since this thread was started.
If you encounter issues enabling plugins, exit Audacity and delete pluginregistry.cfg. Restart Audacity then re-enable your desired plugins by selecting them, clicking “Enable” then clicking OK.
As I said, on feedback@, please use the earlier QM plugins: Missing features - Audacity Support.
Gale
Yes. Uninstalling “everything” does just that.
When that didn’t work, I reinstalled it and then used Revo Uninstaller set at maximum which even removed the lid on my computer. Additionally, As I indicated to you earlier, I formatted the machine and reinstalled Win 10 with no other software installed other than Audacity and Chordino. I still was not able to enable Chordino in the “All” menu.
The fact that no one else ever reported it does not mean that it’s not out there. Perhaps folks simply isolate the “New” plugins by going to the “new” section of the plug in manager and work it the way that I did. No need to report the bug.
Did this on numerous occasions and stated so. As I indicated before, this did not allow me to enable Chordino in the “all” menu. It wasn’t until I enabled Chordino by isolating it in the “New” section that I was successful.
Will do. Thanks for the link.
Uninstalling Audacity with the supplied uninstaller does not remove Audacity settings files: FAQ:Installation, Startup and Plugins - Audacity Manual.
We do not recommend third-party installers or uninstallers, but if you use them please refer to the documentation for those applications to see what they do.
I was not able to find that post in this topic using the search term “format” or “formatted”.
Gale
OK…thanks for the link. I didn’t use the supplied uninstaller. See below. Don’t forget that I also did a complete format of the system and reinstalled Win 10. If that didn’t remove the Audacity settings files, nothing will.
Revo Uninstaller Pro is probably the best uninstaller out there. It’s far better than Windows (and Audacity’s) and removes everything. Although I did not check, I’m guessing that in “advanced mode” it tossed out the Audacity settings. Either way, the format certainly did.
As far as I’m concerned, this issue should be closed. I was able to rectify what I feel is a bug in Audacity by enabling Chordino and other Vamp plugins under the “NEW” section of the Plugin Manager.
It’s not in this topic. Check your correspondence.
When checking your correspondence, don’t forget to scroll all the way to the end.
Please try to use quotes properly so we don’t have to spend time editing your posts to see who said what. I find it as easy as anything just to copy/paste the quote tags as needed.
Gale
Topic marked [SOLVED] and locked (standard practice so other users don’t jump in to it).
We cannot reproduce your requirement to use the “New” section of Plugin Manager.
Gale