Some VSTs rejected on one machine only (solved)

Post your bug reports/problems here

Moderators: davidv, seb@plogue

pwhodges
Posts: 2
Joined: Thu Oct 08, 2015 9:20 am

Some VSTs rejected on one machine only (solved)

Postby pwhodges » Sun Jul 23, 2017 4:53 am

I am completely at a loss here. This is not a specific Bidule problem, but Bidule is one of the affected programs, so I thought someone here might have a clue.

I have two computers, a long-established desktop with loads of stuff on, and a recently reinstalled laptop (which has an SSD). On both I have Plogue Bidule, also WaveLab and Reaper, all in their current 64-bit Windows versions. I also have a number of VSTs (for ambisonic processing, so maybe ones you have never heard of). On the desktop, all these VSTs are recognised by all these programs, and operate as they should. But on the laptop, five of them (from three different suppliers) are not accepted. In WaveLab, they are placed into the "ignored plugins" list; in Bidule and Reaper they are simply not visible.

I have checked that all the file and directory permissions are correct (in one case other VSTs in the same directory are accepted), and have failed to find any way in any of those programs to determine the supposed reason for their rejection. Permissions are in general aligned, as the machines are both in a domain and using the same login.

Any ideas, either for further debugging or for cause?

EDIT:

I have just found Bidule.log, which had eluded me before. For the affected VSTs, it reports: "HMODULE is 0". However, I still don't know what that means, or why it is different on the two machines.

Paul

pwhodges
Posts: 2
Joined: Thu Oct 08, 2015 9:20 am

Re: Some VSTs rejected on one machine only (solved)

Postby pwhodges » Sun Jul 23, 2017 6:05 am

OK, I eventually worked out that it is a VC runtime issue. The desktop has accumulated six 64-bit VC runtimes, whereas the laptop has only got one. Installing the latest VC runtime has brought two of the VSTs into play, and I'll go back through the other missing ones until I get them all in place. It may be that I copied the VST files to the laptop rather than rerunning the installers, so it's probably my fault, sort of.

(Actually, not my fault - some of the VSTs concerned did not have the necessary runtime invoked by their installers)

Paul

seb@plogue
Site Admin
Posts: 9593
Joined: Tue Mar 02, 2004 7:23 pm
Location: Montreal
Contact:

Re: Some VSTs rejected on one machine only (solved)

Postby seb@plogue » Mon Jul 24, 2017 10:11 am

For the affected VSTs, it reports: "HMODULE is 0".


That means that attempting to load the .dll failed, usually it's either because of architecture (32 bit attempting to load 64 bit or the other way around) or missing dependency. I _think_ we used to write the error code coming back from Windows when this failure occurs but it ended up being No Error, I would need to test back to see if it's that and if it's not at least write the Windows error number in the log.


Return to “Bidule Bugs and Problems”

Who is online

Users browsing this forum: No registered users and 3 guests