I'm just playing around with pyext and was wondering how to get an audio stream into a pyext object. what i've tried, is [tabwrite~] audio to a table and then read every single value from that table using [tabread]. that works, but is much too slow. is there any other way to get audio into pyext? sven.
actually sven isn't playing around but working on a really cool project. ;)
m
sven schrieb:
I'm just playing around with pyext and was wondering how to get an audio stream into a pyext object. what i've tried, is [tabwrite~] audio to a table and then read every single value from that table using [tabread]. that works, but is much too slow. is there any other way to get audio into pyext? sven.
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://iem.at/cgi-bin/mailman/listinfo/pd-list
Hi Sven, Python is too slow for audio processing. However, i'm working on the "dyn" project which will allow to build networks of normal PD signal objects from within pyext. If you want even more flexibility you should a look at Supercollider.
best greetings, Thomas
----- Original Message ----- From: "sven" ml.sven@wildsmile.de To: "Pd list" pd-list@iem.at Sent: Monday, August 23, 2004 6:56 PM Subject: [PD] audio~ -> pyext ?
I'm just playing around with pyext and was wondering how to get an audio stream into a pyext object. what i've tried, is [tabwrite~] audio to a table and then read every
single
value from that table using [tabread]. that works, but is much too slow. is there any other way to get audio into pyext? sven.
PD-list@iem.at mailing list UNSUBSCRIBE and account-management ->
At 17:34 23.08.2004, Thomas Grill wrote:
Hi Sven, Python is too slow for audio processing. However, i'm working on the "dyn" project which will allow to build networks of normal PD signal objects from within pyext. If you want even more flexibility you should a look at Supercollider.
hi thomas, I know that python is actually too slow for audio processing, but I just want to do a fft, extract critical bands and some other analysis
which is a highly optimized package for number crunching tasks. that package is written in c and I wouldn't get it much faster if I wrote an external in c than just using numpy. I've already checked if I could do all analysis using pd-objects and just passing the results to pyext but it doesn't seem to be possible, at least not as flexible as I'd need it. I've heard about "dyn" and the things that should get possible with it, but it doesn't help me for what i want to do. and supercollider is only for mac. if i'd just get chunks of audio into pyext it would be fine... sven.
Hi Sven,
but I just want to do a fft, extract critical bands and some other
analysis
- feature extraction in general. all that can be done using Numeric Python
which is a highly optimized package for number crunching tasks. that package is written in c and I wouldn't get it much faster if I wrote an external in c than just using numpy.
i see... i'm afraid there's no such connection in PD yet... this is planned to be integrated into a future version of vasp. Have you tried if the current vasp version can help you with your project?
best greetings, Thomas
and supercollider is only for mac.
-This is not simply not true. There is a version for linux done by stefen kersten: http://user.cs.tu-berlin.de/~kerstens/pub/
AvS
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .....................................................................
` |Schreck Ensemble . . . . . . . . . . . . . . . . . . . . +
` |# -laboratory for live electro-acoustic music- # |
| http://www.schreck.nl/ |
| http://www.xs4all.nl/~schreck/ |
` *===========================================================++
` |Compositions http://www.xs4all.nl/~schreck/html/compo.html |
` |Samples http://www.xs4all.nl/~schreck/html/samp.html |
` |Patches http://www.xs4all.nl/~schreck/html/pat.html |
` |Videos http://www.xs4all.nl/~schreck/html/video.html |
` |Scores http://www.xs4all.nl/~schreck/html/scores.html |
*===========================================================++
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .....................................................................