SurroundByUs.com

I have this particular plugin, of which I like the sound very much, but the thing is that it will only allow me to adjust it's settings in 2dB increments (it only has one knob) , which is way to much in most cases.

Now, on another forum (not about surround) somebody posted a work arround for another host, which uses two instances of that same plug with gains attached to them and then one of them was set to mute. The plugin, not the gain. Now if you moved the knob on one instance of the plugin - the non-muted one - you were able to get 0.5dB increments instead of 2dB.

A bit hard to explain without a pic I guess, but I hope some of the more technical advanced arround here can understand what I'm getting at here and can help me to get it to work in Ploque like that.

If you're going to use multiple instances in Plogue, you could create a group and, in your group controls, set up some sliders which link to the UI of the VST. You probably could do this with just a single instance as well.

Uh, I think that only makes sense for a VST that is Adding to a sound (like an effects return) not something that you use in line.

In which case why not just use the effects return volume?

Maybe you could post a link to the original discussion?

However, if you want a gain bidule, it's under Mixing --> Gain.

You can also build a gain stage with a variable, a dB to Linear Unit Converter, and a multiplier.

Here's the equivalent in plogue:



The -6 dB and -12 dB bidules are just gain blocks. I renamed them to show the gain values.

The two delay lines could be replaced by another instance of the VST (as in the screen shot you posted). You just need something in that path that has the same latency as the RS127 Box VST. I'm guessing that the delay lines would use less DSP but perhaps the layout would look a little cleaner with just another instance of the VST. I checked and the VST has a constant latency of 3 samples, regardless of settings, so if you went that way. you wouldn't have to worry about keeping the same "kc/s" setting on both instances.

Anyway, if you're going to be using this a lot you could make it into a group.

Cheers,
Z

Thanks a lot, Z! I think I can manage that.

Only thing that kind of worries me now is, how about the 'Recording Gate & Sync' thingy when I start to use ZAG (not there yet, but I want to learn how to do that this week), because it only has two busses and these are both taken already, won't the extra latency caused by this (and possible other) plugin(s) offset the whole syncronisation process?

[edit] I just opened it's properties and I see 'input samples' a value of '2', can I just change that to 3 (or more) or doesn't it work like that? It does gives me an extra input bus when I do that.

I'm running my first ZAG conversion right now! This is a lot easier then I innitially thought it would be, guess I got overwhelmed by all the info at once, but after I printed out the manual and sat down in front of my PC with it, I just couldn't believe how easy it was!

Now I don't know if this mix will come out right (will know that in about 40 minutes or so), that will probably be my fault if it doesnt, but you did an incredible job on this! Just WOW! Thanks for all the help so far and for putting this amazing stuff out here!