DSP Robotics Support

OK ... snag.

I was testing the use of the prim EdOPEN, which I understand triggers a Boolean value TRUE when a VST plugin GUI is opened. [something like that]

The issue ... with REAPER ... all FS plugins load in as 'bridged' ... fine.

The problem ... if the FS VST is loaded in and displays [automatically] because it is bridged, the EdOPEN does not go TRUE.

If the VST GUI is closed, and THEN re-opened ... EdOPEN goes TRUE ... everybody happy.

I need 'happy' when the VST first loads and is displayed.

help.

hmm, it works here ( v4.76), but there are some things to point out,

per default reaper deactivates the audio device when it is inactive, so also selectors (i think only ruby) do not work as expected (after clicking on the selector you need to click outside the vst window to get the action done)

to avoid this go to preferences in reaper -> audio -> and turn off "close audiodevices when application is stopped or inactive"

then everything should work as expected..

hope this helps!

Hi NuBeat,

Yes ... I've had that disabled for some time ... probably you helped me identify that issue back then.

This is something different ...

I have a TIMER [countdown] that starts after a defined period of time. I currently use AFTERLOAD to trigger the timer, but wanted to try EdOPEN as that seemed an option that might be even better.

It ain't working unless I first close the VST, then re-open ... then works.

just tried it with this little test vst and the ticker starts at first loading.

FS 2.06 / reaper 4.76 64bit

Nubeat7 wrote:just tried it with this little test vst and the ticker starts at first loading.

FS 2.06 / reaper 4.76 64bit

I can confirm this for FS 3.0.6 / Reaper 5.1.1 32 bit

wait a minute ...

WHY do you have an 'AFTERLoad' prim connected with the EdOpen prim ???

I was using the EdOpen only to provide the trigger to start the clock. If I put BOTH, won't the clock routine start because of the afterload trigger ?

I should add ... I'm not using the same type of a timer/clock as in your RUBY module. I'd have to completely redo that for my project ...

but to the first question ?!?

RJHollins wrote:WHY do you have an 'AFTERLoad' prim connected with the EdOpen prim ???

i just left it there, its the stock ruby ticker, i just exchanged the manual on / off boolean with the edopen prim...

you can try it without... and see if there is a difference.

the ticker itself is just an example, should be no problem with any custom ticker or counter or what ever you want to activate, the question is if the boolean state is forward triggered after loading the plugin...

the question is if the boolean state is forward triggered after loading the plugin...

aahhh ... after seeing your example, that's what made me wonder.

ok ... to test this, I think I should be able to just display a BOOLEAN and use one of the graphical trigger indicators to see if I get a pulse.

THANKS for peeking in. Your insight is always appreciated.

snag #2

Inside this RUBY timer I'm getting NoMethodError: underfined method - scheduleMethod

using FS v3.04

is there a fix or another way ?

oh, you should have a stock ruby ticker with the old methode in your toolbox, just use this one instead...