Csound Csound-dev Csound-tekno Search About

Re: LISP frontend & CM (was Re: [Cs-dev] Important API & OPCODEDIR problems)

Date2005-10-13 14:58
FromMichael Gogins
SubjectRe: LISP frontend & CM (was Re: [Cs-dev] Important API & OPCODEDIR problems)
I also think it would be great if CsoundAV and MacCsound would use the Csound API.

Regards,
Mike

-----Original Message-----
From: Istvan Varga 
Sent: Oct 13, 2005 5:18 AM
To: csound-devel@lists.sourceforge.net
Subject: Re: LISP frontend & CM (was Re: [Cs-dev] Important API & OPCODEDIR problems)

jpff@codemist.co.uk wrote:

> May I repeat the question that I keep asking?  What is stopping a
> release of CS5?  I am aware of only the need for installers.  I would
> like to add the SDFT code but that is not of the essence.  I am
> assuming we have abandoned a sane parser for v5.0
> 
>   I realise there are concerns that the API is not perfect, but I do
> not see why that should delay release.  We need wider use to get it
> right.

Actually, I think it is the library and API that should be finished
first, and could perhaps be released separately so that it can be used
in frontends like CsoundAV or MacCsound, yet it gets the least attention.


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel





-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2005-10-13 15:39
FromDavid Akbari
SubjectRe: LISP frontend & CM (was Re: [Cs-dev] Important API & OPCODEDIR problems)
On Oct 13, 2005, at 9:58 AM, Michael Gogins wrote:

> I also think it would be great if CsoundAV and MacCsound would use the 
> Csound API.
>
> Regards,
> Mike

I am in 100% agreement with this, as MacCsound seems to have an error 
with setting buffer sizes on the "bounce to file in realtime" mode.

It does not take the value from -b or -B but rather defaults to size 
128 so with hardware that required a size of 1024 samples sounds fine 
when performing but the file has gaps (of size (1024 - 128)) between 
segments of audio. This is something that would seem trivial to fix but 
is impossible since MacCsound is closed source...


-David



-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Date2005-10-14 01:29
FromIain Duncan
SubjectRe: LISP frontend & CM (was Re: [Cs-dev] Important API & OPCODEDIR problems)
> I also think it would be great if CsoundAV and MacCsound would use the Csound API.
> 
> Regards,
> Mike

I think everything should use the csound API including my cell phone and 
my coffee machine. Thanks again to everyone who contributed to it, it 
rocks! ; )

( On a more serious note, yes it would be great if all csounds used a 
stable api. )

Iain



-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net