KVR Audio

ObsoleteAcc99 · Post by **ObsoleteAcc99** » Tue Oct 12, 2004 4:04 pm

[DELETED]

DevonB · Post by **DevonB** » Tue Oct 12, 2004 4:35 pm

Because the change of the VST standard, some old plugins don't work. In general, I go down the list and check them all.

Expand out the columns to really see what is what. Some plugs like Culture need to have this set. A lot of them don't though. If you get a plugin that gives you very odd behavior like noise bursts or locking right away, check the box. There's nothing else you need to do besides that.

Devon

kagemusha · Post by **kagemusha** » Tue Oct 12, 2004 4:35 pm

When the R is visible 'old host behaviour' is active. The R (Reprocessing) has something to do with how processing in old standard VSTs was don before.

Mostly you get strange feedbacks if a plug is not comaptatible with the new vst specs. Only then you should activate 'Old host bahaviour'

From what I remember.

K

ObsoleteAcc99 · Post by **ObsoleteAcc99** » Tue Oct 12, 2004 8:17 pm

[DELETED]

kagemusha · Post by **kagemusha** » Tue Oct 12, 2004 10:20 pm

when you mark them it's old host behaviour.

From cubase.net Tips and tricks

Code: Select all

Old plug-in host behaviour vs new plug-in host behaviour.

Cubase SX and Nuendo 2.0 allow users to change the plug-in behaviour to "old host behaviour" in the plug-in information window (Devices menu). This is sometimes necessary since some plug-ins and VST instruments (e.g. Battery and Kontakt) cannot handle the new plug-in host behaviour correctly and thus produce feedback noises.

So how do both modes differ?

Older versions of the VST Audio Engine primarily used the old plug-in behaviour, the so called "process" method. With this method, the plug-in/VST instrument adds its output to the host application's output buffer.

The new plug-in behaviour uses the different "processReplacing" method.
Here, the plug-in or VST instrument simply overwrites the output buffer.

Due to the more complex routing capabilities of the new VST Audio Engine,
the "processReplacing" method is more efficient because:
a) the old buffer content doesn't have to be read again in order to be able to calculate the new buffers
b) the old content doesn't have to be deleted internally in order to avoid adding it to the new plug-in output

All plug-ins and VST instruments can work with the older "process" method but not all of them can also handle the "processReplacing" method correctly. Either they are simply not designed to or they pretend to support "processReplacing" but fail.
The latter leads to feedbacks or VU peaks. Even CPU peaks or poor performance can occur due to invalid floating point values in the buffer.

In order to avoid this malfunction we implemented a switch for the plug-in host behaviour.
Using the old behaviour does not affect the functionality of the plug-in or VST instrument, although in some cases a slightly increased constant CPU load might occur.

Upcoming versions of the affected plug-ins should address this problem and follow the VST 2.3 guidelines.

From the manual

Code: Select all

Old Host Behaviour
Check this column for a specific plug-in if you want it to be processed like it was by previous versions of Cubase SX/SL, to avoid problems such as feedback-like sounds. Note that you have to reload the plug-in for the change to take effect.

Some plugins have no R but I think this is because they are not recognized by cubase for it. Most plugs that have no R are from Jorgen (energyXT etc). But you can check them anyway. The only VST which is checked for Old host behaviour in my case is SIR
With the other I have no problem.

ObsoleteAcc99 · Post by **ObsoleteAcc99** » Wed Oct 13, 2004 6:08 am

[DELETED]

pitchdrifter · Post by **pitchdrifter** » Wed Oct 13, 2004 9:52 am

R without a tick next to it = old host behavior not activated

R with a tick = old host behavior is active

Basically when a plugin gives you no sound / goes to 100% cpu when you just play a note, then ticking that R should fix it. At least thats the symptom I've had on all plugins that required old plugin behavior. Nowadays you shouldn't need that on many plugs, most plugs work spiffy right out of the box.

ObsoleteAcc99 · Post by **ObsoleteAcc99** » Wed Oct 13, 2004 11:25 am

[DELETED]

pitchdrifter · Post by **pitchdrifter** » Wed Oct 13, 2004 11:32 am

oh, sorry. SX3 here, can't recall how it was in SX2.

kagemusha · Post by **kagemusha** » Wed Oct 13, 2004 11:37 am

ttoz wrote:
ok thanks. However I can't tick the R's, I cross them out. but I take that's what you meant. cheers

You can stretch the column. It's because it so small that the checkmark is over the R

Was my explenation that bad

ObsoleteAcc99 · Post by **ObsoleteAcc99** » Wed Oct 13, 2004 2:00 pm

[DELETED]

kagemusha · Post by **kagemusha** » Thu Oct 14, 2004 7:34 am

Can SX guru explain "old host behaviour"