KVR Audio

Chroma One · Post by **Chroma One** » Mon Feb 11, 2008 9:40 am

Your web site still lists this as a SynthEdit bug.

It is my impression that a version of SynthEdit has been available since last fall that fixes this.

Can we expect new versions of the AlgoMusic synths that eliminate the need for the workarounds?

(Not every host will tolerate multiple DLL copies with the same VST ID and the alternative of disabling multi-processing is awfully drastic.)

whyterabbyt · Post by **whyterabbyt** » Mon Feb 11, 2008 9:56 am

Chroma One wrote:
It is my impression that a version of SynthEdit has been available since last fall that fixes this.

where did you get that impression? The fix is being worked on for SE 1.1, which is still in Alpha-testing, and only for module developers for testing of the new SDK. And thats been stated repeatedly on the SE Yahoo group, AFAIK.

tconrardy · Post by **tconrardy** » Tue Feb 12, 2008 4:56 pm

whyterabbyt wrote:
Chroma One wrote:
It is my impression that a version of SynthEdit has been available since last fall that fixes this.
where did you get that impression? The fix is being worked on for SE 1.1, which is still in Alpha-testing, and only for module developers for testing of the new SDK. And thats been stated repeatedly on the SE Yahoo group, AFAIK.

Ahh... thanks for this update. We were not sure about this ourselves, and Boris does not want to do any re-compiling until all the bugs are out and it's an official version. I don't blame him!

Tim

Chroma One · Post by **Chroma One** » Fri Feb 15, 2008 5:34 pm

Thanks for the info. (I read it was fixed somewhere and can't put my finger on it today. One can read anything somewhere on the internet, and so why I asked...)

multi-instance multi-core SynthEdit bug?