Flext is not really necessary. A PD csound~ class based
on the API can be modelled on Matt's csound~ class
for MaxMSP. Translating MaxMSP classes to PD is not a
big problem. 

The advantage of this to the existing csound~ is that
it will probably be cross-platform.

Victor

> 
> It should be possible to make a PD extension for the
> Csound API using flext. It would probaby be easier than
> getting a cross-platform OSC opcode set working. The ports
> on the Csound object could be audio in, audio out, MIDI in
> , MIDI out, and score events in.
> 
> -----Original Message-----
> From: Iain Duncan 
> Sent: Mar 24, 2005 5:03 PM
> To: csound-devel@lists.sourceforge.net
> Subject: Re: [Cs-dev] Broken again
> 
> > huh?
> > Sorry, but I use csound as a realtime synthesis engine
> > all the time   without any widgets.
> > (of course I use it with a midi controller or inside pd)
> 
> If you weren't on the other side of the world, I want to
> come see this!
> 
> > Define control signal-i/o in a generic way in the engine
> > and a seperate   gui implementation/design tool to make
> > the gui. The gui would all be done by a front end.
> > Such a front end, could and should be included in the
> > main csound   distribution as a reference
> > implementation. It could include an  extension to the
> > input files - or section in a csd  -  besides the orc
> > and sco, defining the gui. You can replace the gui file
> > with another one, defining a different   interface etc
> etc.
> 
> That's what I'm trying to do with those fl_controller and
> wx_controller  examples that Michael and I made, I just
> haven't worked on them lately.  I think a really cool way
> to do things would be to have a set of PD  objects that
> could be used to directly access csound5 through api
> calls.  One could then build guis really quickly in PD and
> unhinge them just as  easily.
> 
> Iain
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products
> from real users. Discover which products truly live up to
> the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=
click
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
> 
> 
> 
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products
> from real users. Discover which products truly live up to
> the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=
click
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

isnt there already a pd csound~?  although i think it uses pipes
not the api

On Mar 24, 2005, at 2:37 PM, Victor Lazzarini wrote:

> Flext is not really necessary. A PD csound~ class based
> on the API can be modelled on Matt's csound~ class
> for MaxMSP. Translating MaxMSP classes to PD is not a
> big problem.
>
> The advantage of this to the existing csound~ is that
> it will probably be cross-platform.
>
> Victor
>
>>
>> It should be possible to make a PD extension for the
>> Csound API using flext. It would probaby be easier than
>> getting a cross-platform OSC opcode set working. The ports
>> on the Csound object could be audio in, audio out, MIDI in
>> , MIDI out, and score events in.
>>
>> -----Original Message-----
>> From: Iain Duncan 
>> Sent: Mar 24, 2005 5:03 PM
>> To: csound-devel@lists.sourceforge.net
>> Subject: Re: [Cs-dev] Broken again
>>
>>> huh?
>>> Sorry, but I use csound as a realtime synthesis engine
>>> all the time   without any widgets.
>>> (of course I use it with a midi controller or inside pd)
>>
>> If you weren't on the other side of the world, I want to
>> come see this!
>>
>>> Define control signal-i/o in a generic way in the engine
>>> and a seperate   gui implementation/design tool to make
>>> the gui. The gui would all be done by a front end.
>>> Such a front end, could and should be included in the
>>> main csound   distribution as a reference
>>> implementation. It could include an  extension to the
>>> input files - or section in a csd  -  besides the orc
>>> and sco, defining the gui. You can replace the gui file
>>> with another one, defining a different   interface etc
>> etc.
>>
>> That's what I'm trying to do with those fl_controller and
>> wx_controller  examples that Michael and I made, I just
>> haven't worked on them lately.  I think a really cool way
>> to do things would be to have a set of PD  objects that
>> could be used to directly access csound5 through api
>> calls.  One could then build guis really quickly in PD and
>> unhinge them just as  easily.
>>
>> Iain
>>
>>
>> -------------------------------------------------------
>> SF email is sponsored by - The IT Product Guide
>> Read honest & candid reviews on hundreds of IT Products
>> from real users. Discover which products truly live up to
>> the hype. Start reading now.
>> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=
> click
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>>
>>
>>
>> -------------------------------------------------------
>> SF email is sponsored by - The IT Product Guide
>> Read honest & candid reviews on hundreds of IT Products
>> from real users. Discover which products truly live up to
>> the hype. Start reading now.
>> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=
> click
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real 
> users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

> isnt there already a pd csound~?  although i think it uses pipes
> not the api

Yeah, that was my point, that it would eleventy billion times more rad 
if it used the api and allowed ALL the api functions to be used from PD 
instead of pipes. = )

Iain



> On Mar 24, 2005, at 2:37 PM, Victor Lazzarini wrote:
> 
>> Flext is not really necessary. A PD csound~ class based
>> on the API can be modelled on Matt's csound~ class
>> for MaxMSP. Translating MaxMSP classes to PD is not a
>> big problem.
>>
>> The advantage of this to the existing csound~ is that
>> it will probably be cross-platform.
>>
>> Victor
>>
>>>
>>> It should be possible to make a PD extension for the
>>> Csound API using flext. It would probaby be easier than
>>> getting a cross-platform OSC opcode set working. The ports
>>> on the Csound object could be audio in, audio out, MIDI in
>>> , MIDI out, and score events in.
>>>
>>> -----Original Message-----
>>> From: Iain Duncan 
>>> Sent: Mar 24, 2005 5:03 PM
>>> To: csound-devel@lists.sourceforge.net
>>> Subject: Re: [Cs-dev] Broken again
>>>
>>>> huh?
>>>> Sorry, but I use csound as a realtime synthesis engine
>>>> all the time   without any widgets.
>>>> (of course I use it with a midi controller or inside pd)
>>>
>>>
>>> If you weren't on the other side of the world, I want to
>>> come see this!
>>>
>>>> Define control signal-i/o in a generic way in the engine
>>>> and a seperate   gui implementation/design tool to make
>>>> the gui. The gui would all be done by a front end.
>>>> Such a front end, could and should be included in the
>>>> main csound   distribution as a reference
>>>> implementation. It could include an  extension to the
>>>> input files - or section in a csd  -  besides the orc
>>>> and sco, defining the gui. You can replace the gui file
>>>> with another one, defining a different   interface etc
>>>
>>> etc.
>>>
>>> That's what I'm trying to do with those fl_controller and
>>> wx_controller  examples that Michael and I made, I just
>>> haven't worked on them lately.  I think a really cool way
>>> to do things would be to have a set of PD  objects that
>>> could be used to directly access csound5 through api
>>> calls.  One could then build guis really quickly in PD and
>>> unhinge them just as  easily.
>>>
>>> Iain
>>>
>>>
>>> -------------------------------------------------------
>>> SF email is sponsored by - The IT Product Guide
>>> Read honest & candid reviews on hundreds of IT Products
>>> from real users. Discover which products truly live up to
>>> the hype. Start reading now.
>>> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=
>>
>> click
>>
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>>
>>>
>>>
>>>
>>> -------------------------------------------------------
>>> SF email is sponsored by - The IT Product Guide
>>> Read honest & candid reviews on hundreds of IT Products
>>> from real users. Discover which products truly live up to
>>> the hype. Start reading now.
>>> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=
>>
>> click
>>
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>>
>> -------------------------------------------------------
>> SF email is sponsored by - The IT Product Guide
>> Read honest & candid reviews on hundreds of IT Products from real users.
>> Discover which products truly live up to the hype. Start reading now.
>> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
> 
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
> 


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net