On Wednesday, Oct 22, 2003, at 13:11 America/New_York, Frank Barknecht
wrote:
Hallo, Claudius Maximus hat gesagt: // Claudius Maximus wrote:
Is there a list of objects which do not behave in a continuous way as you decrease the block size below 64?
I *think*, but I'm not that sure and cannot test currently, that all message passing is limited to the 64 samples minimum. To get faster, you will need to resort to signal connections or the time tagged triggers from iemlib.
I don't know an object that opens files in bin-mode, but it could be written as an external.
I do not have a Windows C compiler. I need to investigate whether there are any freely available, can you recommend one?
I don't have a Windows C compiler, too. I don't even have Windows. :) Now, I think, that only Visual C++ from MS is able to compile Pd on Windows. This might not be valid for externals, though.
There are two free compiler setups for Windows that I know of, both
based on gcc. http://MinGW.org and http://cygwin.org. MinGW aims to
me more Windows-like, and Cygwin aims to be UNIX on top of Windows.
Cygwin is better supported and more complete, but its downside is that
you need the cygwin.dll to run programs, and they behave somewhat
UNIX-like.
I have started trying to port parts of Pd to MinGW. It would be great
if ultimately all of Pd would compile in MinGW so that Windows devs
would have to buy (or ahem, "buy") a compiler.
.hc
[set $1 $2( -> "set aardvark sawtooth" when I feed it a pair of symbols "aardvark sawtooth". But when I try to put a "-" instead of the space between the variables:
[set $1-$2( -> "set aardvark-$2" instead of "set aardvark-sawtooth". A problem.
Are there prizes awarded for finding bugs? I would like my prize to be an umbrella - I need to go to the post office but it's raining.
No umbrella, sorry: $x only works if it's at the begining of the identifier. So $x-name is okay, name-$x is not.
A solution to the waveform selection problem is:
[route sawtooth square ...] | | ... | | [trigger bang] | | [symbol $0-sawtooth] | | [set $1( | | [whatever wants to read the array]
Here's an alternative:
[inlet] | [symbol] | [select sawtooth square ...] | | ... | | [set $1( [ print Unknown_Waveform] | | [whatever wants to read the array]
Another thing to think about here, is if it is possible to put all common behaviour into an abstraction. If most of the sound generation seems to be the same, except the different table contents, you might want to put the table content into a file ( tablename write/read somename.txt) and use an abstraction argument to select the waveform file.
Just a suggestion.
ciao
Frank Barknecht _ ______footils.org__
PD-list mailing list PD-list@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-list
There is no way to peace, peace is the way.
-A.J. Muste