PG Music Home Forums PG Music Product Forums PowerTracks Pro Audio Coyote won't install in PT 2022

Was working fine in PT and RB 2016. Upgraded PC to W10.
Purchased BIAB/PT2022.

When I try to load Coyote I get an error prompt saying it's not been loaded because I either canceled or because it's not a valid VSTi.dll ?

Read some stuff on line. I ran the SetupCoyoteWT13.exe install but same issue.

TIA! Wayne

Wayne.
Heres my suggested steps.
...Note all your 2016 settings/preferences.
...Try test same 2016 settings in 2022.

If no joy in 2022 post pics of your 2016 midi and audio driver preferences…and midi and audio settings/preferences for 2022. Pics are only way to save guesses by rest of us.

Best
om

Your issue may be incompatibility because Power Tracks updated to 64 bit in the 2021 version.

Here's a link to an earlier discussion:

https://www.pgmusic.com/forums/ubbthreads.php?ubb=showflat&Number=160913

Charlie.
Maybe i’m being a dumb bloke , and i hadnt tried coyote wt in 2022 biab 64 bit or rb 64 bit…but for laughs lo and behold wt shows up in both in prefs. This is odd, anyhoo i use other instrument vsti’s not coyote…
Thus what is going on ? i was able to load all midi no rt styles also and play // gen etc.
What gives ? what am i missing ? not that i use coyote anyway.

Best
om

Well, this is the PT forum, so references to BiaB/RB may or may not apply.
You said you bought recent "BIAB/PT2022" .. so that is a little confusing.

Did you buy PT2022 from BiaB, or did you buy both PT & BiaB?

Either way, it is still worth noting that the change to 64 bit from 2016 to 2022 may still be a culprit if you are pointing Coyote to a 32 bit version (noticing the error message), and the change to 64 bit just recently occurred in PT

*Edit
This is just me noticing;
you said you installed SetupCoyoteWT13.exe
On my system, both SetupCoyoteWT11.exe & 12 have a newer date (and different file size than either 10 or 13)
which of course seems weird .. maybe try installing the most recent by date(?)
Sorry, I don't have PT2022, but have I friends that do and I know they have Coyote WT running without issue

I appreciate ALL of the helpful comments, albeit some made little sense. I'll comment to each of you in this post below. For now, let me reiterate the issue . . .

I had BIAB 2016. (and RB & PT) Coyote worked fine.
I upgraded my PC from W7 to W10. And bought the 2022
versions of BIAB and PT.

When I went to preferences/midi, Coyote was not listed as an optional VST.
So I did the vst look up and had the software look for available vsts. And
it found several. However it did not "see" Coyote because it did not appear
in my preferences. And the coyote.dll is in the same folder as all the other
vsts it installed. The same folder that it initially was in when I set up 2016.

SO . . . I manually tried to add it. The same exact .dll that was installed
previously. And I get an error prompt saying Coyote is not a valid VSTi.dll file.

Even though I saw no practical reason to do so, I did run the .exe for Coyote
setup. Yes, I did the v13 first. Then by suggestion I also did the newest dated
version which for some reason wasn't 13, but 12.

However all the pertinent pages on the PGM site say Coyote is automatically
set up when you set up BIAB. Apparently it was not.

FYI: Running the Coyote set up exe does not produce a new .dll.

That all being said . . .

1) RE: ...Note all your 2016 settings/preferences. ...Try test same 2016 settings in 2022.
Um, makes no sense my friend. For one thing, I don't have 2016 running. I'm using 2022 and have
no way of "looking up" exactly what the 2016 settings were. HOWEVER I DO know what they were.
Also . . . I CANNOT set my 2022 settings exactly as my 2016 settings were because Coyote IS NOT
available in my settings! And again I have no way to send you pix of my 2016 preferences, not
that it help IMHO in this instance any way.

2). RE the link to the guy with the Sonar issue. That's primarily just saying it might not work with 32bit systems. However . . . PG music includes it with BIAB and I can't get it set up. If they include it, I suspect it will work with BIAB. I agree with the article that Coyote is pretty close to crap compared to other available VSTs, soundfonts, etc. I use Timbres Of Heaven which is a remarkable soundfont. But I need Coyote for a unique reason. I would be using both TOH and Coyote.

3). justanoldmuso apparently had no problem setting it up. As he said, it was there in preferences and it works fine for him. And he apparently did nothing to "get it there".

4). rharv, re your question: "Did you buy PT2022 from BiaB, or did you buy both PT & BiaB?" How exactly would someone purchase PT "from" BIAB? BIAB is software. But I appreciate your help. As I said above I did try running the latest setup .exe. Even though I know it's not going to generate a new .dll. Also, you mention you feel it's because BIAB / PT is now 64bit. Again, justanoldmuso had no problems.

SUMMARY . . . This is what really has me puzzled. 2022 versions came out in what, October 2021, right. That's over 6 months ago. I'm stymied that no one has come across this issue until now. And even more stymied over the fact that no one really knows a "fix" or the resolve. I thank you guys for chipping in with some "ideas". But I would think, after 6 months of the product being available, I could get more than someone's best guess.

I've been using BIAB/PT since 2006. And it's been my personal experience that tech support is pretty much useless. Yeah, they're friendly enough. And can help you out with basic, simplistic issues. But throw something technical at them! But I've had issues with PT since day one that no one has ever been able to resolve. All I get is rhetoric, and "send me this file" or "send me that file." Then no response until I call back and ask them what the file revealed. Always the same answer . . . Nothing.

I remember talking with a guy and explained an issue. He said . . . No, that's not an issue. You're doing something wrong. So I said . . . OK, do such and such and tell me the results. A few seconds later I get . . . Hmmmm. That shouldn't happen! FYI . . . it's been over 6 years and they STILL haven't fixed the issue. And I've called multiple times. Emailed them. NADA!

So it looks to me like I punt!

Thanks for all your help everyone. Much appreciated. Wayne

PS: Just so you know . . . I'm not a novice. I wrote my first computer program in Sept of 1968. And computers have been a major part of my career and personal life.

No, BiaB came out end of November/beginning of December 2021 and PT 2022 was released *much more recent.
FWIW I was just trying to clarify that you have both BiaB 2022 and PT 2022 in my previous post .. suppose I could have been clearer in how I asked

To clarify, you copied over the old one from 2016 to try and get it to work for 2022? CoyoteWT in 2016 would have been 32-bit, but in newer ones is 64-bit, and PowerTracks 2022 is 64-bit. You can try in Band-in-a-Box reinstalling the Coyote Wavetable Synth under Help | Utilities and see if that fixes the issue - it could be it was somehow missed in the installation of your new versions when you ran the .exes to install. Unlikely, but not impossible. It's kind of a roundabout way of doing it, but it may resolve the issue.

I apologize for not replying. Life got in the way! LOL

I don't see Utilities under Help.

Also, per advice I tried reinstalling the SetupCoyoteWTxx.exe file.
There are 4 exes to choose from. The xx being 10, 11, 12 or 13. Tried
them all. No luck.

This is found under the Help menu of Band-in-a-Box.

In Band-in-a-Box specifically, there is a Help menu and then Utilities option. From there, there's an option to re-run the Coyote WT from there. It's not in PowerTracks, but in Band-in-a-Box - that will run the one you need if you have Band-in-a-Box as well. If that's still not working, if you try to change the default synth in PowerTracks do you get any sort of error messages that pop besides the non-valid VST one (and is that one the exact phrasing?), such as no synths being installed even though Coyote WT appears in the Control Panel? If so, this may be a different issue.