[Csnd] Ctcsound for 7.0?
Date | 2024-05-25 09:01 |
From | Pierre Clisson |
Subject | [Csnd] Ctcsound for 7.0? |
Attachments | smime.p7s |
Hi everyone, I was trying to use ctcsound from the develop branch, but there are unresolved symbols. Is there any documentation on how to generate the Python bindings? Thanks, Pierre Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here |
Date | 2024-05-25 10:05 |
From | Francois PINOT |
Subject | Re: [Csnd] Ctcsound for 7.0? |
I'm using it with this release of the develop branch: --Csound version 7.0 (double samples) Mar 10 2024 [commit: 79f84c6e260968828fe2a0492e87ff39360694a0] Which version do you use? Which symbols are unresolved? Are you importing the ctcsound.py file from the develop branch commit you're using? François Le sam. 25 mai 2024 à 10:01, Pierre Clisson <pierre@clisson.com> a écrit : Hi everyone, |
Date | 2024-05-25 10:59 |
From | vlz |
Subject | Re: [Csnd] Ctcsound for 7.0? |
Short answer: It should have worked, I have adapted it to remove the interfaces library and to accommodate the new PerfThread location. I'm sure I have tested it here, need to check. Make sure you are building Csound with the perf thread class in it, it's a cmake option. The full answer: the host API will change and I am sure François will rewrite the bindings to match. He is actually working on the new API proposal, so he may have something to say. Can we move this conversation to the developer's list? It's more appropriate to follow it up there (or possibly a github ticket). best Prof. Victor Lazzarini Maynooth University Ireland > On 25 May 2024, at 09:01, Pierre Clisson |