@ MyCo
Hi MyCo
I sent an email to support but didn't get a response, so I wondered if you could have a look at this please?
I’ve found an issue with Ruby-based controls. I hesitate to call it a bug because there may be no way around it.
This concerns VST exports of effects, tested in Reaper and Sonar 8.
When the DAW is inactive, i.e. not playing or recording, the output command in Ruby becomes inactive but the rest of the Ruby module continues to function.
What this means is that when I make a VST and see it in the DAW FX plugin window, some of the controls fail to operate unless I play the track or arm recording. These are the controls that use Ruby where Ruby provides an output for further use, such as a knob value or selection item. To me, as a user, this looks like a partially non-responsive plugin, since some stuff responds to the mouse and some doesn’t.
With help from the forum we’ve determined that it’s the Ruby output command. Any drawing and mouse actions inside Ruby are still active, even without playback or armed recording.
In Reaper there is a setting to run FX without play running and this solves the problem, but the default for this is off. Reaper says it’s needed for certain VSTis. This means any user of my VSTs will need to change a setting in the DAW and I don’t like this idea.
I also tested with several commercial and free VST FX plugins and not one showed this behaviour, presumably because they don’t use Ruby as a development tool.
Here is a schematic and its VST export which demonstrates this issue.
https://www.dropbox.com/s/c28ovqr636qks ... g.zip?dl=0 All works well in the Flowstone edit environment but try it in Reaper or Sonar and you’ll see that some things work and others don’t or only partially work (unless you arm for recording or have track playback running). Interesting is that the Preset Manager, where the non-Ruby preset selection works but the rest doesn’t, due to depending on a Ruby module inside.
I can understand that the output command has no need to function if the output is for audio frames, but Ruby can output various signal types for many different uses and is more usually used for these.
If the output function depends on a clock signal or similar being present, could you generate a pseudo-clock if the DAW is inactive then switch to the real clock when the DAW plays or records?
Whatever the cause I really would like this to be addressed if at all possible. It would be nice to have consistency you see: Green always runs but with Ruby “it depends” is not really a good situation!
Cheers
Spogg