i guess the main issues with an mysql external is that it breaks all realtime constraints.
so does [soundfiler]. for things like initializing/saving it won't matter, but you're right, constantly polling the DB in the audio thread is probably not a good idea.
which is about one message away in pyext.
yes, but isn't this true for many things we do in Pd? :-D
Gesendet: Dienstag, 23. Januar 2018 um 09:31 Uhr Von: "IOhannes m zmoelnig" zmoelnig@iem.at An: pd-list@lists.iem.at Betreff: Re: [PD] MySQL Pd external?
On 2018-01-23 01:40, Christof Ressi wrote:
thanks! I guess I'll directly work with the mysql library, just as you did with sqlite. the C API doesn't look so complicated, actually.
i guess the main issues with an mysql external is that it breaks all realtime constraints. either you make the calls synchronous, then you probably shouldn't do audio in the same thread (and you could have used e.g. a standalone python application in the first place) or you make it asynchronous (happy coding), which is about one message away in pyext.
fgams IOhannes
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list