hi all,
as you may already know, I have been shamelessly (but secretly) abusing PureData's qlist for some time, adding several sequencing features on an ad hoc basis. There are still many more features pending to be thrown into the mixture (and the hope is, that the best way to clean up the mess will be to make it public...)
So let me try, even if prematurely:
At suita.chopin.edu.pl/~czaja/miXed/externs/xeq.html you should be able to find tarballs with source and .pd_linux precompiled versions of xeq group of externals.
Installation should be painless under linux. I will gradually gather some documentation at the above address.
If anybody is interested, please accept this warning:
This is first alpha release of xeq and friends -- do not use them outside of your safe and peaceful studio or home yet. It is bound to be unreliable (except for the combination of input and features I have been using so far).
Krzysztof
Thanks for this...
With your permission I'd like to incorporate the MIDI file I/O code back into Pd's "qlist" object when I get around to it...
cheers Miller
On Wed, Jan 09, 2002 at 04:20:34PM +0100, Krzysztof Czaja wrote:
hi all,
as you may already know, I have been shamelessly (but secretly) abusing PureData's qlist for some time, adding several sequencing features on an ad hoc basis. There are still many more features pending to be thrown into the mixture (and the hope is, that the best way to clean up the mess will be to make it public...)
So let me try, even if prematurely:
At suita.chopin.edu.pl/~czaja/miXed/externs/xeq.html you should be able to find tarballs with source and .pd_linux precompiled versions of xeq group of externals.
Installation should be painless under linux. I will gradually gather some documentation at the above address.
If anybody is interested, please accept this warning:
This is first alpha release of xeq and friends -- do not use them outside of your safe and peaceful studio or home yet. It is bound to be unreliable (except for the combination of input and features I have been using so far).
Krzysztof
hi Miller and all,
great! That was really my original intention. Now I will try to better encapsulate the midi file part of the library.
And also please do not take for granted my mapping from midi file data stream to a list of Pd messages stored as a qlist sequence (and back) -- whether it is done properly, remains an open question.
If anyone has any suggestions, let me know.
Krzysztof
Miller Puckette wrote: ...
With your permission I'd like to incorporate the MIDI file I/O code back into Pd's "qlist" object when I get around to it...