Csound Csound-dev Csound-tekno Search About

[CSOUND-DEV:4984] vst4cs

Date2004-07-15 04:13
From"Michael Gogins"
Subject[CSOUND-DEV:4984] vst4cs
I have fixed the whining and polyphony problems with vst4cs, at least for
the Cheeze Machine plugin. There is more work to be done: the event timing
should be sample accurate, and the VST event buffers should be dynamic. Then
I can work on the edit dialogs.

Date2004-07-15 13:07
FromAndres Cabrera
Subject[CSOUND-DEV:4992] Re: vst4cs
Good. I've been working on the bank loading. It's not there yet, but I 
can see the light.
I think vstinfo should probably be left there because it is useful to 
use after loading a bank to know the names of the new patches. However, 
vstinfo currently crashes when used this way (i.e. when not 
initializaing the plugin). The following implementation of vstinfo works:

    int vstinfo (void *data)
    {
        VSTINFO *p = (VSTINFO *)data;
        MYFLT *iVSThandle = p->iVSThandle;
        VSTPlugin *plugin = vstPlugins[(int) *iVSThandle];
        plugin->Info();
        return OK;
    }
 Don't know why, but it does.... =)

As you can tell by now, I haven't been able to use cvs... I have done 
the following:
-Downloaded putty, generated a key, uploaded the public key to 
sourceforge (the key is working fine when logging in manually with 
putty.exe and also with pageant.exe), but commands inside putty (even to 
just check out sources) and wincvs are not working...
In wincvs preferences I've set: authentication ssh,  in ssh settings: 
ssh client = plink.exe. CVSROOT  is : 
mantaraya36@cvs.sourceforge.net:/cvsroot/csound. I've set ssh additional 
options to -pw "my password". But I'm getting:
cvs checkout: warning: unrecognized response 
`mantaraya36@cvs.sourceforge.net's password:
' from cvs server

Any ideas as to what's missing?
Also, should there be directories in my home folder on the ssh terminal?

Cheers,
Andrés



Michael Gogins wrote:

>I have fixed the whining and polyphony problems with vst4cs, at least for
>the Cheeze Machine plugin. There is more work to be done: the event timing
>should be sample accurate, and the VST event buffers should be dynamic. Then
>I can work on the edit dialogs.
>
>
>  
>