KVR Audio

Barf · Post by **Barf** » Fri Jan 04, 2008 8:24 am

Sometimes i read about 'problems' with some vst's and duo-core, whats that all about? And what about quad-cores, same problems?

John Vulich · Post by **John Vulich** » Fri Jan 04, 2008 9:10 am

ckatrun411 · Post by **ckatrun411** » Fri Jan 04, 2008 9:12 am

John Vulich wrote:

MaliceX · Post by **MaliceX** » Fri Jan 04, 2008 9:34 am

From what I heard, these are actually problems that are only present if one has two or more instances of the same VSTi opened within a host that supports multithreading.

To get around this, either:
---Use a host that doesn't support dual-core
---Make a duplicate DLL of the plugin and run that as the second instance if need be. (messy solution)
---Dunno if this works, but set affinity to your current host.
---Nag the developer to get off his/her f**king ass and make them add support for multithreading/multicore processing.

John Vulich · Post by **John Vulich** » Fri Jan 04, 2008 10:37 am

MaliceX wrote:From what I heard, these are actually problems that are only present if one has two or more instances of the same VSTi opened within a host that supports multithreading.

To get around this, either:
---Use a host that doesn't support dual-core
---Make a duplicate DLL of the plugin and run that as the second instance if need be. (messy solution)
---Dunno if this works, but set affinity to your current host.
---Nag the developer to get off his/her f**king ass and make them add support for multithreading/multicore processing.

You forgot to mention that this applies to SynthEdit crap, not "real" VSTis.

DevonB · Post by **DevonB** » Fri Jan 04, 2008 10:39 am

There is a knwon limitation with SynthEdit creations. Beyond that, I'm not aware of any other problems. I have used and reviewed a ton of stuff since I got my dual core box in December of 2005, so....

Devon

MaliceX · Post by **MaliceX** » Fri Jan 04, 2008 12:43 pm

John Vulich wrote:
MaliceX wrote:From what I heard, these are actually problems that are only present if one has two or more instances of the same VSTi opened within a host that supports multithreading.

To get around this, either:
---Use a host that doesn't support dual-core
---Make a duplicate DLL of the plugin and run that as the second instance if need be. (messy solution)
---Dunno if this works, but set affinity to your current host.
---Nag the developer to get off his/her f**king ass and make them add support for multithreading/multicore processing.
You forgot to mention that this applies to SynthEdit crap, not "real" VSTis.

Well, in a different case, Oatmeal (a non-SE VSTi) exhibits output problems with dual-core processors, from what I heard.

EDIT: Just for the record, this ONLY applies to most, if not all, SynthEdit VST's, and a small number of non-SE VST's. This is regardless if your host doesn't support multi-processors anyway.

John Vulich · Post by **John Vulich** » Fri Jan 04, 2008 12:47 pm

And that's a good enough reason to imply that all VSTis suffer from this problem?

nBeat · Post by **nBeat** » Fri Jan 04, 2008 1:32 pm

Well, I guess I'm lucky then.
My Monolisa and Daedalus, both SE, work with multiple instances here in
eXT1(v1.4.1), eXT2(v2.0.2) and Orion P(v7.1) on C2D (E6600).

So at least, the problem isn't consistent.
But obviously there's a problem for some not so lucky users, SE or not.

ObsoleteAcc99 · Post by **ObsoleteAcc99** » Fri Jan 04, 2008 1:34 pm

[DELETED]

Cyrosis · Post by **Cyrosis** » Fri Jan 04, 2008 1:37 pm

FYI, Duo is the name of a processor line by Intel, its not a particular technology, thats dual core.

Sorry, had to.

MaliceX · Post by **MaliceX** » Fri Jan 04, 2008 1:38 pm

John Vulich wrote:And that's a good enough reason to imply that all VSTis suffer from this problem?

I wasn't particularly aiming at "all VSTi's" entirety, but more of a generalized answer to the OP's question which you're clearly indicating I'm not being clear enough.

But now that I look at it, indeed it sounds like my choice of words are misleading.

nBeat: The problem's generally absent with hosts that don't normally support multithreading (hence, dual-core processing).

Artvera · Post by **Artvera** » Fri Jan 04, 2008 1:48 pm

Somebody here on KVR had the opinion that problem with SE plugins can happen only with dual core Intel and if SE plugins are used on dual core AMD, so it works fine.

Ben H · Post by **Ben H** » Fri Jan 04, 2008 1:55 pm

I think the problem comes from believing everything you read on KvR.

It's not ALL gospel.

nBeat · Post by **nBeat** » Fri Jan 04, 2008 2:04 pm

MaliceX wrote:
John Vulich wrote:And that's a good enough reason to imply that all VSTis suffer from this problem?
I wasn't particularly aiming at "all VSTi's" entirety, but more of a generalized answer to the OP's question which you're clearly indicating I'm not being clear enough.

But now that I look at it, indeed it sounds like my choice of words are misleading.

I think it was clear that Oatmeal was just an example.
I think he's just working on his image.

MaliceX wrote: nBeat: The problem's generally absent with hosts that don't normally support multithreading (hence, dual-core processing).

All three hosts have two CPU fields ticked (0 & 1) in the activity manager.
Granted, I'm no expert on this. Maybe I'm missing something ?

Vst problems with duo-core?!