Multiple VSTi instances GUI problem...

jorge · 8 Mar 2005

Hi Shifrin

Shifrin wrote: Is this a known problem, does it happen in other hosts? Or is it more likely a problem with EnergyXT (that I can nag Jorgen about) ?

Thanks for reporting it, it is a known problem and very high priority. We started fixing it but didnt quite finish. Were you using v0.9.1c ?

ik_ik_ik · 8 Mar 2005

Yeah, I have had this problem too. Good to know there's a reconised problem 🙂

Perhaps it's related but one thing that crossed my mind too is what internal plugin ID is allocated to VSTi when they are generated? They're supposed to be unique AFAIK. Maybe that's just a myth but it is mentioned in the VST SDK 🙂

Cheers,

Inigo

stefan · 8 Mar 2005

They should be unique indeed. But that's not related to the multi instances. The main goal with unique id's is to be able to recognize presets and patches (fxb/fxp) and see if they can be loaded in a specific plugin or not.

malc · 8 Mar 2005

In the next release you'll be able to specify the 'Unique ID' for your plugins. That just leaves you the small issue of determining whether what you choose is unique or not 😉

I don't know of any central list of plugin ids that are in use so I doubt anyone can guarantee that they will pick one that hasn't already been used.

stefan · 8 Mar 2005

malc wrote: In the next release you'll be able to specify the 'Unique ID' for your plugins. That just leaves you the small issue of determining whether what you choose is unique or not 😉

I don't know of any central list of plugin ids that are in use so I doubt anyone can guarantee that they will pick one that hasn't already been used.

Steinberg used to try to handle the ID handling. I think they gave up... 🙂

jorge · 8 Mar 2005

I think lalo mentioned that using the same ID all the time is an issue with Bidule.

lalo · 8 Mar 2005

jorge wrote: I think lalo mentioned that using the same ID all the time is an issue with Bidule.

it is in Bidule infact....the developers know that but they prefer not to change this...often i have to do some hexeditor trick to change the VST ID of conflicting plugs in bidule.

choosing the VST ID is maybe the best way round

lalo

ik_ik_ik · 8 Mar 2005

stefancrs wrote: Steinberg used to try to handle the ID handling. I think they gave up... 🙂

Yeah 🙂 You can still find the form [here] 😀

Shifrin · 8 Mar 2005

jorge wrote: Thanks for reporting it, it is a known problem and very high priority. We started fixing it but didnt quite finish. Were you using v0.9.1c ?

Ok, I'd originally had the problem with v0.9.1a, just tried it after compiling the VSTi with v0.9.1c and this time I can't even add another instance, EnergyXT throughs an exception when I try to load up the second instance - just so you know!

Oh yeah, seeing as the subject of PluginID's has been brought up, will there be a way to provide strings in response to the host calling getVendorString, getProductString, getVendorVersion? Or will these be hard-wired to SynthMaker?

Cheers,

Shif.

ik_ik_ik · 8 Mar 2005

Heh, it's funny to see the same names and faces appear on this forum, EnergyXT, Short Circuit, Synth Edit, etc. A bunch of really great applications that go hand in hand so well and that are being developed with a real passion. It would be fun to see how they're being harnessed 🙂

They've all certainly had a huge effect on my workflow, methods, creativity and inspiration over the last couple of years.

Cheers,

Inigo

malc · 8 Mar 2005

Shifrin wrote: this time I can't even add another instance, EnergyXT throughs an exception when I try to load up the second instance - just so you know!

That's not good. Leave it with us. It's fine with FL Studio and Tracktion so I can't imagine it will be anything too difficult to fix, just a matter of looking into it.

Shifrin wrote: will there be a way to provide strings in response to the host calling getVendorString, getProductString, getVendorVersion?

Easy enough to do, so I don't see why not.

Shifrin · 8 Mar 2005

malc wrote: It's fine with FL Studio and Tracktion so I can't imagine it will be anything too difficult to fix, just a matter of looking into it.

FYI I just tried my VSTi (built with v0.9.1c) in Tracktion (my other host) and this time when I tried to add a second instance I got a :-

"ERROR! - This VST plug-in didn't initialise correctly" message in Tracktion 😮 Weird indeed!

malc wrote: Shifrin wrote: will there be a way to provide strings in response to the host calling getVendorString, getProductString, getVendorVersion?

Easy enough to do, so I don't see why not.

Cheers!

One last thing, when I first installed the latest version 0.9.1c and tried to run it I was told that the procedure entry point for MiniDumpWriteDump could not be found in dbghelp.dll - I fixed this by d/ling a more recent version of dbghelp.dll and putting it in the same folder as the .exe for SynthMaker. But thought I'd mention it to you (Running Win2000 SP4).

Incedently I tried to put the updated dbghelp.dll in WINNT\SYSTEM32 but it was continually overwritten with the older version which is very confusing!

Shif.

malc · 9 Mar 2005

Shifrin,

Any chance you could email me the VSTi you created so I can look into that problem? If it works for me then I'll know that the problem is machine/setup related.

Thanks.

Shifrin · 9 Mar 2005

malc wrote: Shifrin,

Any chance you could email me the VSTi you created so I can look into that problem? If it works for me then I'll know that the problem is machine/setup related.

Thanks.

Check your email 😉

Shif.

malc · 10 Mar 2005

Got it, thanks Shif 🙂

lalo · 10 Mar 2005

hi i got the same error with a SM plug of mine too... in Tracktion , eXT and Bidule..did'nt tried on podium but i will

malc · 10 Mar 2005

Sorry people, I think I've completely misunderstood - doh!

I had it in my mind that this was the same as a previous problem. I now realise this is different. So please disregard my previous statements about it working in FL Studio and Tracktion - for me none of them work.

This is actually a good sign as it means it's not related to the host you're using and will probably be something reasonably obvious once I start looking (famous last words).

Shifrin · 10 Mar 2005

malc wrote: This is actually a good sign as it means it's not related to the host you're using and will probably be something reasonably obvious once I start looking (famous last words).

Phew, I was worried it would be some sort of peculiarity with my system when you'd said multiple instances were running fine for you!

Hope you find the problem 🙂

Shif.

malc · 11 Mar 2005

Ok, that's fixed now. As predicted, it was something reasonably obvious and very easy to fix in the end.

Thanks for all your help.

Shifrin · 11 Mar 2005

malc wrote: Ok, that's fixed now. As predicted, it was something reasonably obvious and very easy to fix in the end.

Nice one 😀

Shif.

lalo · 12 Mar 2005

malc wrote: Ok, that's fixed now. As predicted, it was something reasonably obvious and very easy to fix in the end.

Thanks for all your help.

cool 🙂

great guys!

jorge · 12 Mar 2005

malc wrote: Ok, that's fixed now. As predicted, it was something reasonably obvious and very easy to fix in the end.

I confirm. Yesterday I've been playing with our next beta release candidate, I created multiple instances of the same VSTi and it worked fine.