thanks!

Hey all,
Looked for an answer to this. I am starting use arrays to store lists. I would like to be able to put the array into a list. I am currently stepping through each value in the array to input into the list. Is there a faster way?

I would think there is, but I cannot find any.

Hey,
This is helpful. Can you help explain how the variables work? I am trying to understand it.

William

Hey all,
My composition now for electric cello and pd is being released on Parma Recordings, Mind and Machine, Vol. V on September 23, 2023.

In preparation for the release I am doing a couple of concerts in Chicago. I will be doing a concert at Constellation on Sunday, August 27, 2023 at 8:30pm Central. The concert will be livestreamed as well. I will be using Pd as well to accompany Cage's Lecture on Nothing. Would love to see some of you there.

Links to information:

Sunday, August 27, 2023 @ 8:30pm
Cage: Lecture on Nothing
Raynovich: now
https://wl.seetickets.us/event/Frequency-Series-Presents:-MAVerick-Ensemble/564057?afflky=ConstellationChicago&fbclid=IwAR0_XSE2mK_7D8MpXQhDx7tbGHwhWazrt-gZm7gGLmijOvqZ2Ab9Og6tJcM

rr8091_animated-cover.mp4

Hmmm.... iemguts is not working for me. It has been awhile since I have uploaded a library of objects.

iemguts-0.1 was what I was trying to upload. Any ideas on why it is not working? I am on a mac. and using pd 51.4.

Trying to use canvasselect but it cannot be found.

Any ideas?

I am trying to make this work, but am struggling.

Here is the message I am sending:

find [object_name] [number 0f object created to delete]

but I am getting this message:

consistency check failed: sys_decodedialog: Cage_varIII_circle
(Tcl) INVALID COMMAND NAME: invalid command name ".find.searchin"
while executing
".find.searchin configure -text "$infostring""
(procedure "pdtk_showfindresult" line 19)
invoked from withi

heck failed: sys_decodedialog: Cage_varIII_circle
(Tcl) INVALID COMMAND NAME: invalid command name ".find.searchin"
while executing
".find.searchin configure -text "$infostring""
(procedure "pdtk_showfindresult" line 19)
invoked from within
"pdtk_showfindresult .x10044c780 1 1 42"
("uplevel" body line 11)
invoked from within
"uplevel #0 $docmds"bad

heck failed: sys_decodedialog: Cage_varIII_circle
(Tcl) INVALID COMMAND NAME: invalid command name ".find.searchin"
while executing
".find.searchin configure -text "$infostring""
(procedure "pdtk_showfindresult" line 19)
invoked from within
"pdtk_showfindresult .x10044c780 1 1 42"
("uplevel" body line 11)
invoked from within
"uplevel #0 $docmds"bad

hjh, I get it. The thing is that I am trying to just write the "number" for a date. . . . so, it feels rather wrong, but I get it. Without double precision, a "number" can only be indicated to six digits. . . I do not know the exact number but I get the idea.

I was trying to write a date as a number. . . . yes, I can do it other ways, but this was a "simple" way I was hoping to do it. It is cool that I cannot, but there is another piece I want to write that requires even more detail than double precision. The other thing is that I cannot even write the number as a symbol which seems even more annoying.

Anyway, I am good with it all. Just wish we could have more precision.

And so there is no way to expand the number of digits a number can have? Seems counter to an application that uses numbers in composition. I can imagine there are some workarounds, but I wish there was a way to expand the numbers allowed to assess.

It seems that the == object cannot assess a number with seven digits.