-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
README needs info about 2010 & 2015 VC++ Redistributable, for 64-bit Protoplug #32
Comments
Don't believe in leaving things open indefinitely. Anyone interested will have seen this. Web searches should find it. Thanks. |
Thanks so much for figuring all this out. Obviously, I already have all those runtimes on my systems, so I didn't realize what was or wasn't required. As mentioned in #31, I'd like to provide all the DLLs in a portable way and will look into that. |
Thanks for the reply. I reopen this issue rather than the other related one, since technically there's no problem other than a person needs to know what Visual C++ Redistributables to install. The other, #31, might be of interest to someone not completely initiated in the constant problems of trying to get DAWs to work and keep working. I reopen this because I did some more experimenting and found, at least for myself, that if I put
This is a short summary. I'll post another comment with some more details and observations, like what I see other distributions doing with Visuall C++ Redistributables. For myself, portability reigns supreme. I generally seek not to use programs that have magic installers that create mysterious or complicated dependencies, registry entries and that kind of thing. |
I guess that's it. Thanks. No real need to have reopened this. No need for it to stay open. |
Thanks again for the software. I work to keep unused Visual C++ Redistributables off of my PC. Programs install them but don't uninstall them. It's bad when great programs stop working on a new PC.
I got lucky with 32-bit Protoplug, but 64-bit Protoplug needs two versions of Visual C++ Redistributable installed: 2015 for
Lua Protoplug Fx (x64).dll/Lua Protoplug Gen (x64).dll
, and 2010 forlua51.dll
.Anyway, the problem is only a documentation problem. I provide links below to the Microsoft web pages I used to get the downloads, and I make a few comments about the file dates of
lua51.dll
.Aside Number 1: ReaPlugs/Protoplug as a team, ReaPlugs vs. Protoplug
Only God knows the future: bad problems will show up fast, bad problems will take time to show up, things will work good enough, or things will work great.
But the plan is like this:
It's all good, but comparisons can be made between JSFX/ReaPlugs and Lua/Protoplug. In particular, Lua is a full-blown scripting language, so if it will work for real-time audio processing, it's better.
Preface comment about Visual Studio 2017
As a preface to what download I decided to use, the GitHub Protoplug README says this in section Compiling from Source:
I try to use only the minimal dependencies, but I decided to use
Microsoft Visual C++ 2015-2019 Redistributable
. On the page linked to below, it says this:I know a little more now, but only a little.
Back to the Download Links
The file dates of 32-bit and 64-bit
lua51.dll
, of the v1.4.0 downloads, are 2014 file dates. The 32-bit Protoplug works with onlyMicrosoft Visual C++ 2015 Redistributable (x86)
installed, but 64-bit Protoplug needs two installs of Visuall C++ Redistributable.In the process of finding the problem, I installed the 2012 and 2013 VC++R, but it was the 2010 version that finally got 64-bit
lua51.dll
working.For the 64-bit VSTs, I installed
Microsoft Visual C++ 2015-2019 Redistributable (14.21.27702.2)
. For security, I've started to try and make sure I get the latest versions, but Microsoft doesn't work hard to make doing that easy. I finally found this page:For
lua51.dll
, I used this Microsoft download page:The way everything works, like getting download sites from searches, it sets people up to download infected files, from sites that provide helpful information, but I guess that's not my problem.
The text was updated successfully, but these errors were encountered: