Now with Win-7 64bit ... FS issues

[MyCo]

Why do the others not work

Haven't checked it yet, but at first glance I see a problem in the Schematic. You have to give each selector (and any other control) a unique preset name. Right now every selector uses the preset name "selector", so basically they use the same VST-Parameter. This can confuse FS a bit, when the VST host sends this "selector" Parameter back.

[RJHollins]

I put all the selectors I have into this test module to show which work or not.

I changed the PRESET NAME just now on my test .... no difference.

NOTE: They ALL work when in the FS program. By that, I mean, the pull down menu OPENS up.

HOWEVER ... after export, only the old SM design will open. The others will not even open to display the choices.

---- EDIT ----

The ones that don't work are based on RUBY coding.

[RJHollins]

I hope someone gets the time to check out what the problem might be. I can only guess at it.

It seems suspicious that only the RUBY based modules are not working AFTER export.

NOTE: these non-working ones are supposedly stock FS ones from the toolbox. They work just find when I run them in FS ... but not after export to VST. Yet the old SM modules work just fine. They're based on primitives.

Please please help. This affects most every project

Thanks and much appreciated !

[RJHollins]

OK Guys ... I continue to track down the cause of the problem, and now find something of interest.

The destination format is for a VST plugin. The HOST is REAPER.

When I load the test VST into REAPER, none of the RUBY based drop-down selectors work. The 'primitive' based ones DO work.

Now for the new result.

The moment I hit the PLAY button with Reaper, ALL the selectors work.

As soon as I hit STOP ... those Ruby based selectors go inactive.

So ... what does this mean ??? Why would the DAW need to be running [play mode] in order for the VST components to be active ? Recall .... the primitive based selectors work at all times ... just not the RUBY ones.

Does RUBY need special conditions ???

I hope the experts can shed some light on this.

Thanks Guys .... this is very confusing, and quite detrimental to all my projects.

Again, Thanks for taking the time to follow on this.

[RJHollins]

From an older thread ... I think we have identified the culprit, and possible solution.
http://www.dsprobotics.com/support/viewtopic.php?f=2&t=3265&p=20857#p20857

In Reaper audio preferences there is an option, 'close audio device when stopped and application inactive'.

I UN-ticked it .... now the GUI works.

More testing ... but this is a good start I hope.