I have a problem with the vst plugin tcregen_64.dll, a looper plugin which I put in the global rackspace.
It works fine on my pc, yet not on my notebook. Both work with win10 pro systems.
GP4 deactivated the plugin (red list) and nanohost64bit (a simple vst loader and wrapper) can’t open it and asks, if it’s a 32bit plugin. But only on the notebook, not on the pc.
Anybody has an idea about what’s going wrong here and how to solve the problem? I really would like to sit with guitar, notebook and the looper on GP in the park or garden and play a little!
To make sure you copy the right (working) plugin, best use the GP-Plugin Manager on your PC to navigate to the right folder by right-clicking the pluging in the plugin’s list and choose “Open containing folder”.
That way you cannot mistaken file locations!
I went both ways but it unfortunately didn’t solve the issue.
In savihost I get the information, that the “side-by-side configuration” is the problem. Whatever this means…
I don’t know if this can even have an impact on vst: on my pc I use a local administrator account whereas on the notebook I use a regular account with admin rights.
I use GP4 with Scuffham S-gear and Midi Guitar2. I use just rackspaces, no songs.
As midi controller serves a Novation LaunchpadMini MK3, where I mapped 40 buttons for program changes to select 40 patches, which sometimes contain two sounds via a CH1 - CH2 switch.
Two rows serve as volume sliders to level out the vol in live situations. One more row for effects on and off (autowah, flanger/chorus, overdrive, delay, tap time, CH1-2) and the tuner.
I just play on sessions and do some recording in StudioOne. My roots are in blues-rock and funk yet I am developping towards fusion and progrock.
I live close to Bayreuth (no Wagner fan) and to Thomann. And - as I have done a lot of editing on the computer my motto for coming months is: Less computer, more playing!
Are you sure? Remember that all your other plugins were working just fine.
Sounds to me that you need to install this runtime library if you have a problem with that specific plugin, or with something else that specifically depends on that library. It’s not something one should blindly install on your computer.
More relevantly, if that plugin required that older runtime library then the plugin’s installer should have taken care of it.
It would not be bizarre to most users unless they are deeply technical. It would just be another piece of “magic” that users think they have to do to fix a broken system. And who knows what that “fix” might break.
I have already edited the title and your solution to make it clearer.
We do appreciate your taking the time to report how the specific problem was solved.