DSP Robotics Support

Let me preface this question by saying that I've completely read the forums over and over about the preset manager and all that and still cannot get my VST plugin to expose it's parameters to the daw system. Any help would be much appreciated.

My plugin is working fine, I just can't get see it's parameters in the daw so when I change something on it the settings don't save with the song file. I'll attach some pictures of the schematic below. The plugin controls 8 digital preamps so you see the 8 modules for each preamp below. It also has two midi device selectors to select the midi in/out ports for bi-directional control...



Here is an inner view of the first module. Except for the root midi channels in each module, they're all the same. The picture is too big to fit inline in the forum so linked here...

http://prntscr.com/8hdsp8

I've removed the few attempts at the preset manager I tried. Not sure where to put it or how to set it up so that the knob and button parameters are fully exposed to the daw. I will attach that module here in case anyone wants to wire it up into a test VST to demonstrate how to make that happen. If you can set that up so that it will expose the knob and button to any daw, so that it can be recalled (no plan to automate them, but parameters have to be exposed to be stored with the song I suppose). If I can get one module working then the rest should also work, or I'll just duplicate the one that works.

Thanks a lot in advance.

Note: Interesting that the forum doesn't allow the *.hom extension as an attachment, their own product file format? Attached as zip.

One other question. I'm trying to get rid of a lot of the small modules by using Ruby. It's working great but I can't get it to return mathematical results like 17/60 = 0.2833333333333333, it returns zero, not 0.xxxxxxx, not matter which format I use.

What am I doing wrong? Thanks.

P.S. Here's a much better schematic layout of that bi-directional mic control module. Much easier to read and follow.

http://prntscr.com/8hgypj

Ruby let me clean it up but I can't get rid of that /60 part.

S1User wrote:One other question. I'm trying to get rid of a lot of the small modules by using Ruby. It's working great but I can't get it to return mathematical results like 17/60 = 0.2833333333333333, it returns zero, not 0.xxxxxxx, not matter which format I use.

What am I doing wrong? Thanks.

P.S. Here's a much better schematic layout of that bi-directional mic control module. http://prntscr.com/8hgqtl

Ruby is sensitive to number formats. If you divide two integers, the result will be an integer as well. In your case, try

17.0 / 60.0

which will force floats.

Thanks. I figured it out. It just wouldn't do it all on the single code line. This below returns an integer or an error...

output @RawValue /2-1/60

When I split it up like below it works, spits out the long float number between 0 and 1...

newvalue=@RawValue /2-1
output newvalue /60

The schematics are so much cleaner using Ruby instead of all of those little math modules. Thanks a lot.

TBH you didn't figure it out, you just were lucky.

As I said, Ruby is sensitive to number formats. There needs to be at least one float for a result to also be a float. Ruby also has an automatic conversion feature that takes care of the right format (from Ruby's point of view). By splitting into two lines you obviously gave the automatic conversion a chance to do its job.

You shouldn't rely on it. That can produce code you will have difficulties with later on. Be precise from the beginning. If you want a result to be a float, use a float. Using an integer and then splitting code up in the hope that the automatic conversion will somehow get it done is too risky.

3 / 2 -> results in an integer
3.0 / 2; 3 / 2.0; 3.0 / 2.0 -> result in a float

Variables are also of a certain format.

var = 3
var / 2 -> results in an integer

var = 3.0
var / 2 -> results in a float

In your case it means, you construct will only work as long as one of the variables is a float. Since you let Ruby decide, it may not always be the case. So be careful.

Ah ok, thanks.

The first number being divided by two is always an integer and even if it's done on an odd number and results in a rounded integer it's still ok. It's just the second calculation that requires the float output with the /60 so in my case it seems to always return a float.

But that's good to know. I've not used Ruby before so I'll put that in the old memory bank. Thank you.