Re: [Csnd-dev] [EXTERNAL] Re: [Csnd-dev] New host API

Ok will do!
Prof. Victor Lazzarini
Maynooth University
Ireland

On 2 Aug 2024, at 09:39, Francois PINOT <[email protected]> wrote:


*Warning*

This email originated from outside of Maynooth University's Mail System. Do not reply, click links or open attachments unless you recognise the sender and know the content is safe.

Effectively, csoundEventString() does the job.

CsoundGetSpin() and CsoundGetSpout() share memory too. I think people who use the host API should be aware of the risks of sharing memory with Csound. I prefer to keep csoundGetTable() and remove the copy functions. Sharing memory allows us to use numpy ndarray to access directly Csound memory: a powerful but evidently dangerous feature.

François

Le ven. 2 août 2024 à 09:48, vlz <[email protected]<mailto:[email protected]>> a écrit :
The csoundReadScore functions are renamed as

csoundEventString()

(and consolidated).

The reason I wasn't sure if we should keep csoundGetTable() is whether it is safe to share the memory. If we feel it is ok, then we should remove the copy functions because the host can easily implement them.


Prof. Victor Lazzarini
Maynooth University
Ireland

> On 2 Aug 2024, at 08:19, Francois PINOT <[email protected]<mailto:[email protected]>> wrote:
>
> 
> I nearly finished refactoring ctcsound.py for the new host API. I'd like to reintroduce the following functions in csound.h:
>
> csoundReadScore, csoundReadScoreAsync (maybe merged with an async_mode flag), csoundGetTable and csoundGetTableArgs.
>
> Reading score from a string is useful when coupled with csoundCompileOrc.
> csoundGetTable is interesting because it gives direct access to the memory data of the function table.
> csoundGetTableArgs can be useful when dealing with a  lot of tables.
>
>  François