yes, making it cross-platform might really be a problem.
Rick
Taube presented a paper last ICMC about using FFIs to
integrate
GTK to provide a graphical interface for CM. He seemed to
have
a system that could easily be used to do the same with the
csound lib through the API. I mentioned that to him and he
seemed
very interested, as he was not aware of csound 5 (as many
people
are not).

Victor

>
> I've considered this since I use Common Music with Csound.
>  But I would start by figuring out how to use the Csound
> library from Macintosh Common Lisp on MacOS 9 since that
> is my platform.
>
> Making it cross-platform could be very difficult as I
> understand that the foreign-function interfaces of the
> various Lisps are rather different.  But Bill Schottstaedt
> seems to have managed somehow with CLM for many years.
>
> *shrug*
>
> Anthony
>
>
> Victor Lazzarini wrote on 10/4/05 7:54 PM:
>
> > The API has actually opened the way for a multitude
> > of frontends. I would like to see one in Lisp, to run
> > with common music.
>
>
>
> -------------------------------------------------------
> 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

I think an important step will be to get the release along with a 
readable "what's new" summary into as many audio distros and packages as 
possible. I know pure:dyne will include, I assume agnula and CCRMA will 
too right?

And of course there's our tireless evangelist Dave! ; )

Iain

Steven Yi wrote:
> Hi Victor,
> 
> It's interesting that many aren't aware of Csound5.  I know with the
> Java IDE Netbeans, they've started to advertise the 5.0 beta with a
> very prominent icon and links.  Maybe when we can get installers and
> packages done, we should pursue the same type of thing on the
> csounds.com page, with some kind of fancy icon (there's an example of
> this on http://www.netbeans.org).  A Csound5 page with a summary note
> of major changes like the netbeans page would be informative for
> people who have used Csound in the past and may be interested to see
> what the major changes are.
> 
> steven
> 
> 
> On 10/5/05, Victor Lazzarini  wrote:
> 
>>yes, making it cross-platform might really be a problem.
>>Rick
>>Taube presented a paper last ICMC about using FFIs to
>>integrate
>>GTK to provide a graphical interface for CM. He seemed to
>>have
>>a system that could easily be used to do the same with the
>>csound lib through the API. I mentioned that to him and he
>>seemed
>>very interested, as he was not aware of csound 5 (as many
>>people
>>are not).
>>
>>Victor
>>
>>
>>>I've considered this since I use Common Music with Csound.
>>> But I would start by figuring out how to use the Csound
>>>library from Macintosh Common Lisp on MacOS 9 since that
>>>is my platform.
>>>
>>>Making it cross-platform could be very difficult as I
>>>understand that the foreign-function interfaces of the
>>>various Lisps are rather different.  But Bill Schottstaedt
>>>seems to have managed somehow with CLM for many years.
>>>
>>>*shrug*
>>>
>>>Anthony
>>>
>>>
>>>Victor Lazzarini wrote on 10/4/05 7:54 PM:
>>>
>>>
>>>>The API has actually opened the way for a multitude
>>>>of frontends. I would like to see one in Lisp, to run
>>>>with common music.
>>>
>>>
>>>
>>>-------------------------------------------------------
>>>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
>>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
> 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

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.

  I propose that we prepare a 5rc1 forthwith, with basic installers.

==John ffitch


-------------------------------------------------------
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

Yes, we can go for the installers. I thought the best thing was
to provide installer targets in SConstruct. I was looking into
OSX installing tools, but I'd prefer if it was possible to have
a multiplatform script-based installer.

Can you add the SDFT as a plugin opcode alongside the
FFT-based opcodes?

Victor

At 09:09 06/10/2005, you 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.
>
>   I propose that we prepare a 5rc1 forthwith, with basic installers.
>
>==John ffitch
>
>
>-------------------------------------------------------
>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

Victor Lazzarini
Music Technology Laboratory
Music Department
National University of Ireland, Maynooth 



-------------------------------------------------------
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

Well, I am in the middle of making some modifications to the API including
integrating Cscore.  But, as I only have a couple of hours a week for this
right now, it will likely take me two or three more weeks.

Changing the API after putting out a "release candidate" does not seem
appropriate since they will be binary incompatible.

Also, to function like I imagine other cross-platform projects do, I hope
that we can announce the intention to put out a release candidate several
days before it actually happens so that every platform maintainer has the
opportunity to test the code before releasing.  During this time, only
changes to make the release work identically on all platforms should be
made.

Releases in the past have generally been unannounced, and I tend to find out
afterwards that source code changes are necessary in order to compile on my
system, thus making the code different (eg. 4.23f12 on the Mac is a little
different than other platforms).  I would like to avoid this if possible.

Thanks.

Anthony Kozar
anthonykozar AT sbcglobal DOT net
http://akozar.spymac.net/


jpff@codemist.co.uk wrote on 10/6/05 4:09 AM:

> May I repeat the question that I keep asking?  What is stopping a
> release of CS5?

> 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.



-------------------------------------------------------
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

Anthony Kozar wrote:

> Well, I am in the middle of making some modifications to the API including
> integrating Cscore.  But, as I only have a couple of hours a week for this
> right now, it will likely take me two or three more weeks.
> 
> Changing the API after putting out a "release candidate" does not seem
> appropriate since they will be binary incompatible.

What incompatible API changes are required by your Cscore functions ?


-------------------------------------------------------
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

At a minimum, I will have to add a function pointer to that region of
CSOUND_ that is preserved during a reset.  I am not really sure what other
changes may introduce incompatible changes.  (Probably, the signature of a
few of the Cscore functions will change).

Anthony

Istvan Varga wrote on 10/6/05 12:46 PM:

> What incompatible API changes are required by your Cscore functions ?



-------------------------------------------------------
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

Start cs5 in a shell. Run this code with the < -L stdin > flag set.  
Type in the shell:

i1 0 2 440

I get a one second delay.
I am also getting very strange hiccups when reading audio from Gen1 
tables...




sr=44100
kr=100
nchnls=2
nchnls = 2
instr  1

ao	oscil 5000,p4,1

outs	ao

endin



f0 600
e






__________________________________________
http://jeanpiche.com


On 05-10-06, at 10:36, Victor Lazzarini wrote:

> Yes, we can go for the installers. I thought the best thing was
> to provide installer targets in SConstruct. I was looking into
> OSX installing tools, but I'd prefer if it was possible to have
> a multiplatform script-based installer.
>
> Can you add the SDFT as a plugin opcode alongside the
> FFT-based opcodes?
>
> Victor
>
> At 09:09 06/10/2005, you 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.
>>
>>   I propose that we prepare a 5rc1 forthwith, with basic installers.
>>
>> ==John ffitch
>>
>>
>> -------------------------------------------------------
>> 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
>
> Victor Lazzarini
> Music Technology Laboratory
> Music Department
> National University of Ireland, Maynooth
>
>
> -------------------------------------------------------
> 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

that's running on 10.4 OSX

__________________________________________
http://jeanpiche.com



-------------------------------------------------------
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

I've got time to check out and report on anything specific to WinXP and
Fedora 4.

I had some version issues in Fedora 4 on dependencies (libsndfile,
PortAudio, Python, etc), so I think in general it would be good to have
a survey of the dependencies including the specific versions (whether
cvs, snapshot, or release). Also, I found in Fedora 4 I needed to edit
the ldconfig files (I don't remember the specific files since I'm not at
my Fedora 'puter right now) because the LD_LIBRARY_PATH was not enough
to get csound5 to run - in fact in the end LD_LIBRARY_PATH did not need
to be set. I could run through the whole setup sequence in a pristine
sandbox to get any platform-specific issues documented for release
notes, I could update docs, update and confirm samples, or do any basic
work for the release.

I'm a newbie here, and hope over time to become a signifiant
contributor, but for now some platform testing is probably the most I
can do - and perhaps some basic debugging. I'm a 14-years C++ veeteran,
but new to the CSound code.

Let me now!

Mike Worobec

Istvan Varga wrote:

> Anthony Kozar wrote:
>
>> Well, I am in the middle of making some modifications to the API
>> including
>> integrating Cscore.  But, as I only have a couple of hours a week for
>> this
>> right now, it will likely take me two or three more weeks.
>>
>> Changing the API after putting out a "release candidate" does not seem
>> appropriate since they will be binary incompatible.
>
>
> What incompatible API changes are required by your Cscore functions ?
>
>
> -------------------------------------------------------
> 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

Anthony Kozar wrote:

> At a minimum, I will have to add a function pointer to that region of
> CSOUND_ that is preserved during a reset.

That is not an incompatible change because only Csound internals are
expected to access that area (it is #ifdef'd with __BUILDING_LIBCSOUND).

> I am not really sure what other changes may introduce incompatible changes.
 > (Probably, the signature of a few of the Cscore functions will change).

Those were not part of the API yet, so being backward compatible with
the previous Csound4 interface is not really important.
Incompatible changes that are relevant include those made to already
existing Csound5 interfaces.


-------------------------------------------------------
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

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