| I am referring to opcodes. The Csound API access is guaranteed across versions by ctcsound.
========================
Prof. Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952
> On 4 Aug 2019, at 20:29, Worrall, David wrote:
>
> Are you referring to just the embedded python/opcode, or other situations as well?
>
>
> ---
> Dr David Worrall
> Professor, Audio Arts and Acoustics
> Columbia College Chicago
> Wikipedia: David Worrall
> Personal research/creative practice website: avatar.com.au
> Some music/sonification: on soundcloud Youtube videos
> New Book: Sonification Design: From data to intelligible soundfields (Springer)
>
> From: Csound-developers on behalf of Victor Lazzarini
> Reply-To: Csound-developers
> Date: Friday, August 2, 2019 at 13:50
> To: "CSOUND-DEV@LISTSERV.HEANET.IE"
> Subject: Re: [Csnd-dev] the ctcsound.setMessageCallback()
>
> I suspect we will need to retire Python 2.x support in Csound 7.
>
> Not sure whether we can keep backward compatibility if we update the code to 3.x
>
> I am also not sure we should do this update
> only to cause more problems in the future.
>
> Victor Lazzarini
> Dean of Arts, Celtic Studies, and Philosophy
> Maynooth University
> Ireland
>
> On 2 Aug 2019, at 07:41, Francois PINOT wrote:
>
>> ctcsound is a pure Python library. It detects the platform where it is loaded (lines 38 to 45 in ctcsound.py) so that it can bind to the correct dynamic library. So it is effectively the same ctcsound.py file that is used on linux, window, and OSX.
>>
>> Actually Csound is built with Python 2.7.x due to the compilation of the Python opcodes. I recommend to use ctcsound with Python 3.x. On my linux system, I copy manually the ctcsound.py file into ~/.local/lib/python3.6/site-pacakages which is the user directory for Python3.6 packages, because the Csound build system put ctcsound.py into ~/.local/lib/python2.7/site-pacakages.
>>
>> You can display the python3 path on your system with this command:
>> python3 -c "import sys; print(sys.path)"
>>
>> Then it is easy to write a script for copying ctcsound.py from the directory where the Csound installer put it into the python3 path.
>>
>> François
>>
>> Le ven. 2 août 2019 à 02:49, Worrall, David a écrit :
>>> Sorry for the omission: OSX in this case.
>>> I suspect this is a csound install issue. Maybe not.
>>>
>>> Is ctcsound the same across platforms for the same version of Csound?
>>>
>>> Thanks,
>>> David
>>>
>>>
>>> From: Csound-developers on behalf of Francois PINOT
>>> Reply-To: Csound-developers
>>> Date: Thursday, August 1, 2019 at 14:47
>>> To: "CSOUND-DEV@LISTSERV.HEANET.IE"
>>> Subject: Re: [Csnd-dev] the ctcsound.setMessageCallback()
>>>
>>> Which OS on your machines?
>>>
>>> François
>>>
>>> Le jeu. 1 août 2019 à 20:25, Worrall, David a écrit :
>>>> Hi François,
>>>> Thank you for your detailed reply. Much appreciated.
>>>> I will try to implement an alternative, as you suggest.
>>>>
>>>> I AM aware of the need to use the version of ctcsound that comes with the csound installer. Yesterday I was just searching quickly for online documentation…
>>>>
>>>> On a related matter – should be a different post, I know :-) – I’m doing installations on many machines. I always install anaconda python first – and the csound installer picks it up OK.
>>>> But somehow, access to ctcsound is not automatic.: following installation, sometimes python import it, othertimes not and I have to manually copy it to a general place.
>>>> To make it a bit more complicated, Anaconda python does not use $PYTHONPATH.
>>>> Do you have a suggestion/mod for how to ensure that, following installation, ctcsound will be available to the python used during the install?
>>>>
>>>> Thank you for your assistance, and your work on this wonderful tool!
>>>>
>>>> Regards,
>>>>
>>>> David
>>>>
>>>> ---
>>>> Dr David Worrall
>>>> Professor, Audio Arts and Acoustics
>>>> Columbia College Chicago
>>>> 33 E. Ida B. Wells Drive Room 601A
>>>> Chicago, ILLINOIS, USA 60605
>>>> Tel: (1)312.369.8821 Fax: (1)312.369.8427
>>>> Wikipedia: David Worrall
>>>> President, International Community for Auditory Display icad.org
>>>> Personal research/creative practice website: avatar.com.au
>>>> Some music/sonification: on soundcloud Youtube videos
>>>> New Book: Sonification Design: From data to intelligible soundfields (Springer)
>>>>
>>>> From: Csound-developers on behalf of Francois PINOT
>>>> Reply-To: Csound-developers
>>>> Date: Thursday, August 1, 2019 at 03:35
>>>> To: "CSOUND-DEV@LISTSERV.HEANET.IE"
>>>> Subject: Re: [Csnd-dev] the ctcsound.setMessageCallback()
>>>>
>>>> Hi David,
>>>>
>>>> I didn't implement the setMessageCallback methods in ctcsound because actually ctypes cannot translate correctly the varlist arg. A workaround is to use the createMessageBuffer(False) method of the Csound object. This will redirect all the messages generated by Csound in a buffer that you can use as you want with the firstMessage(), firstMessageAttr(), popFirstMessage(), messageCnt() and destroyMessageBuffer() methods of the Csound object.
>>>>
>>>> Note that you should not use the pydoc version of ctcsound.py. ctcsound.py is part of Csound and it is distributed within each release of Csound. The reason is that if the API changes in a release, those modifications are reflected in the ctcsound.py file distributed with this release. I don't now who uploaded ctcsound.py to pydoc, but it wasn't a good idea.
>>>>
>>>> François
>>>>
>>>> Le jeu. 1 août 2019 à 02:39, Worrall, David a écrit :
>>>>> Hello All,
>>>>> I searched but couldn’t see a discussion on this so Perhaps I’m missing something….
>>>>>
>>>>> I’m looking at the ctcsound equivalent or workaround for csnd6.SetMessageCallback()
>>>>>
>>>>> In François’ documentation (thanks François), it says:
>>>>> https://csound.com/docs/ctcsound/ctcsound-API.html?highlight=setmessagecallback
>>>>> is says (my red)
>>>>> UDPConsole(addr, port, mirror)
>>>>> Turns on the transmission of console messages to UDP on addr:port.
>>>>>
>>>>> If mirror is one, the messages will continue to be sent to the usual destination (see setMessageCallback()) as well as to UDP. Returns CSOUND_SUCCESS or CSOUND_ERROR if the UDP transmission could not be set up.
>>>>>
>>>>> and at http://pydoc.net/ctcsound/0.0.2/ctcsound/ it shows:
>>>>>
>>>>> #def setDefaultMessageCallback():
>>>>>
>>>>> #def setMessageCallback():
>>>>>
>>>>> Can someone please advise me, what the correct way of setting a callback message?
>>>>> This is what I used to do using csnd6:
>>>>> cs = csnd6.Csound()
>>>>>
>>>>> def passCallback():
>>>>>
>>>>> pass # suppress all terminal output from CS
>>>>>
>>>>> TRACE = False
>>>>>
>>>>> if not TRACE:
>>>>>
>>>>> cs.SetMessageCallback(passCallback())
>>>>>
>>>>>
>>>>> Many thanks,
>>>>> David
>>>>>
>>>>> ---
>>>>> Dr David Worrall
>>>>> Professor, Audio Arts and Acoustics
>>>>> Columbia College Chicago
>>>>> 33 E. Ida B. Wells Drive Room 601A
>>>>> Chicago, ILLINOIS, USA 60605
>>>>> Tel: (1)312.369.8821 Fax: (1)312.369.8427
>>>>> Wikipedia: David Worrall
>>>>> Personal research/creative practice website: avatar.com.au
>>>>> Some music/sonification: on soundcloud Youtube videos
|
