More precisely, I get:

>>> cs.SetPythonMessageCallback(csdlog)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib/python2.5/csnd.py", line 1737, in SetPythonMessageCallback
    return _csnd.Csound_SetPythonMessageCallback(*args)
AttributeError: 'module' object has no attribute
'Csound_SetPythonMessageCallback'


Looking a little closer it looks like that's actually a problem, not
just me doing the wrong thing.  I'll try replacing my csnd.py and
_csnd.so files.
-Chuckk

On Mon, Oct 27, 2008 at 3:08 PM, Chuckk Hubbard
<badmuthahubbard@gmail.com> wrote:
> The closest I have available is .setPythonMessageCallback() for
> CppSound, and .SetPythonMessageCallback() for Csound class.
> .SetPythonMessageCallback() somehow can't find the attribute, although
> it is listed with dir(CppSound) and help(CppSound), and
> .setPythonMessageCallback() takes 1 argument (self), won't take a
> function as argument.
>
> -Chuckk
>
> On Mon, Oct 27, 2008 at 2:53 PM, victor <Victor.Lazzarini@nuim.ie> wrote:
>> Use the Csound() (or derived) class and the Csound::SetMessageCallback()
>> method.
>>
>> the callback should be something like
>>
>> def  mcallback(s):
>>   # s is a string
>>   # e.g. you can print it
>>   print s
>>
>>
>> cs.SetMessageCallback(mcallback)
>>
>>
>> Victor
>> ----- Original Message ----- From: "Chuckk Hubbard"
>> <badmuthahubbard@gmail.com>
>> To: <csound@lists.bath.ac.uk>
>> Sent: Monday, October 27, 2008 12:04 PM
>> Subject: [Csnd] Re: Re: Querying available audio devices
>>
>>
>>> Sounds like a plan.  I'll let people choose from whichever modules are
>>> available for their platform and then see the devices for whatever
>>> they choose.
>>>
>>> I tried directing both stderr and stdout to file objects, and didn't
>>> pick up the Csound output from cs.compile().  Anyone know how I do
>>> that in Python?
>>>
>>> -Chuckk
>>>
>>> On Mon, Oct 27, 2008 at 11:12 AM, victor <Victor.Lazzarini@nuim.ie> wrote:
>>>>
>>>> For -+rtaudio you can just check the platform OS and the
>>>> modules for each are well-defined (ie portaudio and alsa for linux, etc).
>>>>
>>>> The only way I think is to run csound with -odac99, then parse
>>>> the message output.
>>>>
>>>> Perhaps an API function to do this might be possible, but it
>>>> will need to be implemented by the IO modules.
>>>>
>>>> Regards
>>>>
>>>> Victor
>>>>
>>>> ----- Original Message ----- From: "Chuckk Hubbard"
>>>> <badmuthahubbard@gmail.com>
>>>> To: "Csound List" <csound@lists.bath.ac.uk>
>>>> Sent: Monday, October 27, 2008 7:54 AM
>>>> Subject: [Csnd] Querying available audio devices
>>>>
>>>>
>>>>> Is there a way to do this with the API?  To build a list of available
>>>>> devices to show in my app?
>>>>> I think it would have to know possible values for both -+rtaudio and
>>>>> -odac, no?
>>>>>
>>>>> -Chuckk
>>>>> --
>>>>> http://www.badmuthahubbard.com
>>>>>
>>>>>
>>>>> Send bugs reports to this list.
>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>>>> csound"
>>>>
>>>>
>>>>
>>>> Send bugs reports to this list.
>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>>> csound"
>>>>
>>>
>>>
>>>
>>> --
>>> http://www.badmuthahubbard.com
>>>
>>>
>>> Send bugs reports to this list.
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>> csound"
>>
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>
>
>
> --
> http://www.badmuthahubbard.com
>



-- 
http://www.badmuthahubbard.com