Hi
I tried loading the csound~ found on
http://csound.github.io/download.html in Max on windows.
I copied the csound~.mxe64 to Max7/resources/externals/msp, then it
will attempt to load it in a max object. It does not produce an error,
but does not create the csound~ object either. The object remains
brown-ish, like it would for a non-existent object.

Just wanted to check if anyone knows anything about this, Is it
expected to work?


-- 

Oeyvind Brandtsegg
Professor of Music Technology
NTNU
7491 Trondheim
Norway
Cell: +47 92 203 205

http://www.partikkelaudio.com/
http://crossadaptive.hf.ntnu.no
http://gdsp.hf.ntnu.no/
http://soundcloud.com/brandtsegg
http://flyndresang.no/

I don't think there is a maintainer at the moment for csound~.  It'd
be good to get someone to help out there.

On Tue, Dec 6, 2016 at 4:16 PM, Oeyvind Brandtsegg
 wrote:
> Hi
> I tried loading the csound~ found on
> http://csound.github.io/download.html in Max on windows.
> I copied the csound~.mxe64 to Max7/resources/externals/msp, then it
> will attempt to load it in a max object. It does not produce an error,
> but does not create the csound~ object either. The object remains
> brown-ish, like it would for a non-existent object.
>
> Just wanted to check if anyone knows anything about this, Is it
> expected to work?
>
>
> --
>
> Oeyvind Brandtsegg
> Professor of Music Technology
> NTNU
> 7491 Trondheim
> Norway
> Cell: +47 92 203 205
>
> http://www.partikkelaudio.com/
> http://crossadaptive.hf.ntnu.no
> http://gdsp.hf.ntnu.no/
> http://soundcloud.com/brandtsegg
> http://flyndresang.no/

Hi guys!

I was thinking, would it be possible to port the `csoundapi~ `object
from Pd to Max? Maybe it'd be better to maintain one codebase instead of
two? For backwards compatibility we can create a Max-abstraction wrapper
which would translate `csound~`messages and attributes into the
`csoundapi~` ones.

Eugene

On Wed, Dec 7, 2016, at 18:33, Steven Yi wrote:
> I don't think there is a maintainer at the moment for csound~.  It'd
> be good to get someone to help out there.
> 
> On Tue, Dec 6, 2016 at 4:16 PM, Oeyvind Brandtsegg
>  wrote:
> > Hi
> > I tried loading the csound~ found on
> > http://csound.github.io/download.html in Max on windows.
> > I copied the csound~.mxe64 to Max7/resources/externals/msp, then it
> > will attempt to load it in a max object. It does not produce an error,
> > but does not create the csound~ object either. The object remains
> > brown-ish, like it would for a non-existent object.
> >
> > Just wanted to check if anyone knows anything about this, Is it
> > expected to work?
> >
> >
> > --
> >
> > Oeyvind Brandtsegg
> > Professor of Music Technology
> > NTNU
> > 7491 Trondheim
> > Norway
> > Cell: +47 92 203 205
> >
> > http://www.partikkelaudio.com/
> > http://crossadaptive.hf.ntnu.no
> > http://gdsp.hf.ntnu.no/
> > http://soundcloud.com/brandtsegg
> > http://flyndresang.no/

I think it is a good idea.  Max patches are in themselves not always
backwards compatible when new versions of Max come out.

2016-12-08 15:33 GMT-08:00 Rory Walsh :
> I thought about this some time ago and may even have proposed it on the
> list. The problem is that csound~ offers far more functionality than the
> csoundapi~ object. I'm not too familiar with the ins and outs, but I think
> csound~ offers some kind sequencer magic and other goodies that csoundapi~
> doesn't. Therefore I'm not sure any kind of backwards compatibility could be
> maintained. But surely a community csoundapi~ for Max would place Max/MSP
> users in a better place than they currently are?
>
> On 8 December 2016 at 23:15, Eugene Cherny  wrote:
>>
>> Hi guys!
>>
>> I was thinking, would it be possible to port the `csoundapi~ `object
>> from Pd to Max? Maybe it'd be better to maintain one codebase instead of
>> two? For backwards compatibility we can create a Max-abstraction wrapper
>> which would translate `csound~`messages and attributes into the
>> `csoundapi~` ones.
>>
>> Eugene
>>
>> On Wed, Dec 7, 2016, at 18:33, Steven Yi wrote:
>> > I don't think there is a maintainer at the moment for csound~.  It'd
>> > be good to get someone to help out there.
>> >
>> > On Tue, Dec 6, 2016 at 4:16 PM, Oeyvind Brandtsegg
>> >  wrote:
>> > > Hi
>> > > I tried loading the csound~ found on
>> > > http://csound.github.io/download.html in Max on windows.
>> > > I copied the csound~.mxe64 to Max7/resources/externals/msp, then it
>> > > will attempt to load it in a max object. It does not produce an error,
>> > > but does not create the csound~ object either. The object remains
>> > > brown-ish, like it would for a non-existent object.
>> > >
>> > > Just wanted to check if anyone knows anything about this, Is it
>> > > expected to work?
>> > >
>> > >
>> > > --
>> > >
>> > > Oeyvind Brandtsegg
>> > > Professor of Music Technology
>> > > NTNU
>> > > 7491 Trondheim
>> > > Norway
>> > > Cell: +47 92 203 205
>> > >
>> > > http://www.partikkelaudio.com/
>> > > http://crossadaptive.hf.ntnu.no
>> > > http://gdsp.hf.ntnu.no/
>> > > http://soundcloud.com/brandtsegg
>> > > http://flyndresang.no/
>> > > http://soundcloud.com/t-emp
>
>



-- 

Oeyvind Brandtsegg
Professor of Music Technology
NTNU
7491 Trondheim
Norway
Cell: +47 92 203 205

http://www.partikkelaudio.com/
http://crossadaptive.hf.ntnu.no
http://gdsp.hf.ntnu.no/
http://soundcloud.com/brandtsegg
http://flyndresang.no/

I think it is a good idea.  Max patches are in themselves not always
backwards compatible when new versions of Max come out.

2016-12-09 22:26 GMT-08:00 Oeyvind Brandtsegg :
> I think it is a good idea.  Max patches are in themselves not always
> backwards compatible when new versions of Max come out.
>
> 2016-12-08 15:33 GMT-08:00 Rory Walsh :
>> I thought about this some time ago and may even have proposed it on the
>> list. The problem is that csound~ offers far more functionality than the
>> csoundapi~ object. I'm not too familiar with the ins and outs, but I think
>> csound~ offers some kind sequencer magic and other goodies that csoundapi~
>> doesn't. Therefore I'm not sure any kind of backwards compatibility could be
>> maintained. But surely a community csoundapi~ for Max would place Max/MSP
>> users in a better place than they currently are?
>>
>> On 8 December 2016 at 23:15, Eugene Cherny  wrote:
>>>
>>> Hi guys!
>>>
>>> I was thinking, would it be possible to port the `csoundapi~ `object
>>> from Pd to Max? Maybe it'd be better to maintain one codebase instead of
>>> two? For backwards compatibility we can create a Max-abstraction wrapper
>>> which would translate `csound~`messages and attributes into the
>>> `csoundapi~` ones.
>>>
>>> Eugene
>>>
>>> On Wed, Dec 7, 2016, at 18:33, Steven Yi wrote:
>>> > I don't think there is a maintainer at the moment for csound~.  It'd
>>> > be good to get someone to help out there.
>>> >
>>> > On Tue, Dec 6, 2016 at 4:16 PM, Oeyvind Brandtsegg
>>> >  wrote:
>>> > > Hi
>>> > > I tried loading the csound~ found on
>>> > > http://csound.github.io/download.html in Max on windows.
>>> > > I copied the csound~.mxe64 to Max7/resources/externals/msp, then it
>>> > > will attempt to load it in a max object. It does not produce an error,
>>> > > but does not create the csound~ object either. The object remains
>>> > > brown-ish, like it would for a non-existent object.
>>> > >
>>> > > Just wanted to check if anyone knows anything about this, Is it
>>> > > expected to work?
>>> > >
>>> > >
>>> > > --
>>> > >
>>> > > Oeyvind Brandtsegg
>>> > > Professor of Music Technology
>>> > > NTNU
>>> > > 7491 Trondheim
>>> > > Norway
>>> > > Cell: +47 92 203 205
>>> > >
>>> > > http://www.partikkelaudio.com/
>>> > > http://crossadaptive.hf.ntnu.no
>>> > > http://gdsp.hf.ntnu.no/
>>> > > http://soundcloud.com/brandtsegg
>>> > > http://flyndresang.no/
>>> > > http://soundcloud.com/t-emp
>>
>>
>
>
>
> --
>
> Oeyvind Brandtsegg
> Professor of Music Technology
> NTNU
> 7491 Trondheim
> Norway
> Cell: +47 92 203 205
>
> http://www.partikkelaudio.com/
> http://crossadaptive.hf.ntnu.no
> http://gdsp.hf.ntnu.no/
> http://soundcloud.com/brandtsegg
> http://flyndresang.no/
> http://soundcloud.com/t-emp



-- 

Oeyvind Brandtsegg
Professor of Music Technology
NTNU
7491 Trondheim
Norway
Cell: +47 92 203 205

http://www.partikkelaudio.com/
http://crossadaptive.hf.ntnu.no
http://gdsp.hf.ntnu.no/
http://soundcloud.com/brandtsegg
http://flyndresang.no/

It is called csound6~ now, btw.

The question is why port it, if there is a
version in the form of csound~? The 
problem is finding a maintainer who
works with max.

I am happy to keep maintaining csound6~,
it is not at all a problem to work with Pd,
but max is another kettle of fish altogether.


Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

> On 10 Dec 2016, at 06:37, Oeyvind Brandtsegg  wrote:
> 
> I think it is a good idea.  Max patches are in themselves not always
> backwards compatible when new versions of Max come out.
> 
> 2016-12-09 22:26 GMT-08:00 Oeyvind Brandtsegg :
>> I think it is a good idea.  Max patches are in themselves not always
>> backwards compatible when new versions of Max come out.
>> 
>> 2016-12-08 15:33 GMT-08:00 Rory Walsh :
>>> I thought about this some time ago and may even have proposed it on the
>>> list. The problem is that csound~ offers far more functionality than the
>>> csoundapi~ object. I'm not too familiar with the ins and outs, but I think
>>> csound~ offers some kind sequencer magic and other goodies that csoundapi~
>>> doesn't. Therefore I'm not sure any kind of backwards compatibility could be
>>> maintained. But surely a community csoundapi~ for Max would place Max/MSP
>>> users in a better place than they currently are?
>>> 
>>>> On 8 December 2016 at 23:15, Eugene Cherny  wrote:
>>>> 
>>>> Hi guys!
>>>> 
>>>> I was thinking, would it be possible to port the `csoundapi~ `object
>>>> from Pd to Max? Maybe it'd be better to maintain one codebase instead of
>>>> two? For backwards compatibility we can create a Max-abstraction wrapper
>>>> which would translate `csound~`messages and attributes into the
>>>> `csoundapi~` ones.
>>>> 
>>>> Eugene
>>>> 
>>>>> On Wed, Dec 7, 2016, at 18:33, Steven Yi wrote:
>>>>> I don't think there is a maintainer at the moment for csound~.  It'd
>>>>> be good to get someone to help out there.
>>>>> 
>>>>> On Tue, Dec 6, 2016 at 4:16 PM, Oeyvind Brandtsegg
>>>>>  wrote:
>>>>>> Hi
>>>>>> I tried loading the csound~ found on
>>>>>> http://csound.github.io/download.html in Max on windows.
>>>>>> I copied the csound~.mxe64 to Max7/resources/externals/msp, then it
>>>>>> will attempt to load it in a max object. It does not produce an error,
>>>>>> but does not create the csound~ object either. The object remains
>>>>>> brown-ish, like it would for a non-existent object.
>>>>>> 
>>>>>> Just wanted to check if anyone knows anything about this, Is it
>>>>>> expected to work?
>>>>>> 
>>>>>> 
>>>>>> --
>>>>>> 
>>>>>> Oeyvind Brandtsegg
>>>>>> Professor of Music Technology
>>>>>> NTNU
>>>>>> 7491 Trondheim
>>>>>> Norway
>>>>>> Cell: +47 92 203 205
>>>>>> 
>>>>>> http://www.partikkelaudio.com/
>>>>>> http://crossadaptive.hf.ntnu.no
>>>>>> http://gdsp.hf.ntnu.no/
>>>>>> http://soundcloud.com/brandtsegg
>>>>>> http://flyndresang.no/
>>>>>> http://soundcloud.com/t-emp
>>> 
>>> 
>> 
>> 
>> 
>> --
>> 
>> Oeyvind Brandtsegg
>> Professor of Music Technology
>> NTNU
>> 7491 Trondheim
>> Norway
>> Cell: +47 92 203 205
>> 
>> http://www.partikkelaudio.com/
>> http://crossadaptive.hf.ntnu.no
>> http://gdsp.hf.ntnu.no/
>> http://soundcloud.com/brandtsegg
>> http://flyndresang.no/
>> http://soundcloud.com/t-emp
> 
> 
> 
> -- 
> 
> Oeyvind Brandtsegg
> Professor of Music Technology
> NTNU
> 7491 Trondheim
> Norway
> Cell: +47 92 203 205
> 
> http://www.partikkelaudio.com/
> http://crossadaptive.hf.ntnu.no
> http://gdsp.hf.ntnu.no/
> http://soundcloud.com/brandtsegg
> http://flyndresang.no/