Hi,
I thought the inlet of adc~ would make its inputs settable via messages but I don' t manage to do it. Is it the real purpose of this inlet ?
Thanks.
No. I should make it go away.
cheers Miller
On Mon, May 19, 2003 at 12:24:35PM +0100, Alex wrote:
Hi,
I thought the inlet of adc~ would make its inputs settable via messages but I don' t manage to do it. Is it the real purpose of this inlet ?
Thanks.
PD-list mailing list PD-list@iem.kug.ac.at http://iem.kug.ac.at/cgi-bin/mailman/listinfo/pd-list
hi Miller,
call me a pest, but my suggestion is to keep adc~ as it is now.
Taking its inlet out would cause lots of ``connection failed'' errors during MSP-to-Pd import.
While some other incompatible objects can be (and in fact are) substituted with cyclone's, in case of adc~ neither wrapper abstraction (overhead), nor external substitution (sys_soundin is not visible, and probably should not be) seems fine to me at the moment.
Whenever you fancy taking a quick look at cyclone's source, you will find it in cvs at pure-data.sf.net (under externals/miXed).
Krzysztof
Miller Puckette wrote:
No. I should make it go away.
...
On Mon, May 19, 2003 at 12:24:35PM +0100, Alex wrote:
...
I thought the inlet of adc~ would make its inputs settable via messages but I don' t manage to do it. Is it the real purpose of this inlet ?
-
Alex -
Krzysztof Czaja -
Miller Puckette