py/pyext, was: Re: [PD] Re: [Vasp] VASP future
gr at grrrr.org
Wed Mar 23 11:01:31 CET 2005
the current cvs py/pyext version does exactly what you want, except
that it doesn't use numpy but rather numarray.
There is currently a debate going on about what the future of arrays in
Python might be, and there's a new project called numeric3 which shall
once unite the strengths of both numeric and numarray. Numeric3 is said
to have good chances to go into the Python core.
py/pyext supports numarray for buffer and signal processing - i haven't
released it yet as i heard there have been crashes with the dsp part
and at the moment i don't have time to test that. buffer processing is
quite efficient as PD buffers are directly mapped to Python arrays,
signal processing is quite slow on the other hand because of the
overhead of calling into Python code. Using psyco JIT compilation helps
a bit though.
A large part of current VASP functionality is already covered by the
numarray functions, and i plan to bundle the other, more music-specific
things into a VASP module, using mainly Python code and - if needed -
the C-extensibility of numarray.
Please note that i chose numarray over Numeric only because there was a
recommendation to do so, which has changed in the meantime - i'm ready
to jump on the line that leads to standardization.
Summarizing, i would recommend that you check out the cvs versions of
flext and py/pyext, install the numarray and psyco extensions to
Python, and try out the new features (there are example patches for
buffer and signal processing). I'm convinced that threading has become
_quite_ stable in the meantime - if there are still issues please
report back in detail, so that i can fix them.
Oh yes, clearly i'd like to integrate image processing some day -
although i have no idea yet, when this will happen. I'd really like to
have a PDP/GEM-py/pyext bridge, but again, Python array support is not
stable yet, so there's no need to hurry.
Am 23.03.2005 um 00:52 schrieb sven:
> hey thomas,
> since i've discovered numpy i use vasp just to get audio into python
> (evil hack and lot's of overhead) to process it with numpy.
> anything that's possible with vasp and much more is possible with
> numpy and numpy is really very optimised.
> even if one is not a python programmer learning basic python and numpy
> shouldn't take much longer than learning how to use vasp.
> and learning python is something you'll never regret anyway...
> imho> if it was possible with pyext to get audio into python and back
> and if threading in pyext was more stable, there wouldn't be
> much need for vasp (assumed that one is willing to learn basic python).
> AND not to be forgotten, numpy is also great for imageprocessing......
> . . . ! ! ! !! !! !!! !!!!!!!!!
> PD-list at iem.at mailing list
> UNSUBSCRIBE and account-management ->
More information about the Pd-list