It's taking longer to compile because I use std::vector to create and
manage the audio buffers and MIDI queues. This greatly simplifies the code
and makes bugs much less likely, but this kind of code takes longer to
compile. But I have a fast PC so this is not bothersome.

No idea about polyiblit. Probably the sequence of calls in vst4cs is not
quite what polyiblit is expecting.

Original Message:
-----------------
From: Andres Cabrera acabrera@teleset.com.co
Date: Thu, 22 Jul 2004 08:18:02 -0500
To: csound-dev@eartha.mills.edu
Subject: [CSOUND-DEV:5083] vst4cs Compatibilty


I've been working on improving compatibility for vst4cs, and things are 
going well, but I found something I can't figure out. Polyiblit and Claw 
only work well if a vstprogset is sent before sending any notes. I can't 
see why this should affect since on  void VSTPlugin::Init()  (line 446) 
there is:
Dispatch(effSetProgram  ,  0, 0, NULL, 0.0f);
Any clues?


Michael,
This is just a technical question. I'm wondering why it is taking now
longer to build vst4cs. Is it because of it's interaction with the
csound API? Is there a way to improve this?

Andrés


--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .