>Hallo,<br>
>Chuckk Hubbard hat gesagt: // Chuckk Hubbard wrote:<br>
<br>
>> I've been trying for a few weeks to get my preset memory set up just right.<br>
>> I got it right just tonight, and then it disappeared.<br>
<br>
>Unfortunatly it is really hard to follow your patch for an outsider<br>
>like me.<br>
<br>
Yeah, I figured, I just wondered why Pd wasn't showing half of what was
in the file. I built it "organically", i.e. using numerous
workarounds, and it's grown pretty huge, so its function isn't very
clear. But suddenly there were no connections showing on the main
page, and several of the objects just weren't there at all- though I
figured out why last night.<br>
<br>
>Without knowing how it is supposed to work it's near impossible to<br>
>tell, where it starts breaking. So here are some random remarks:<br>
<br>
>You use things like [pd abc $1 $2]. This will not do what you may<br>
>expect: Subpatches made with [pd] don't accept their own arguments,<br>
>they use the arguments of the surrounding patch. You can delete the<br>
>"$1 $2" from [pd abc $1 $2], it's totally ignored by Pd.<br>
<br>
I figured this out too, I had just wanted to make sure the arguments
from the patch were passed on to the subpatch. I never bothered
to delete them when I noticed it didn't matter. I also haven't
taken the time to delete all the extraneous GUI objects, since it
wasn't quite ready for use.<br>
<br>
>[until] is a very dangerous object, as it might not receive the<br>
>stopping bang, if something unexpected happens. You use [until]<br>
>several times to drive a "from-to-counter". It is much more secure to<br>
>not send a bang into [until]'s first inlet and hope for the bang to<br>
>the right inlet to arrive, instead you can send a float value to the<br>
>until, which will make [until] bang as often as the float specifies,<br>
>after that the until will stop automatically.<br>
<br>
Thanks, I thought I had gotten rid of all of the ones without
floats. I had to reboot a few times early on and learned my
lesson.<br>
At any rate, I thought saving my work regularly was a failsafe, but,
like I said, this disappearance of objects took place on all saved
versions, when they were working fine before closing.<br>
It appears to be just too much stuff! The connections are all at
the end, so when the file reached a certain size it just didn't get to
them. Same with the 8 "JIvoice" objects, they were added later,
and it stopped reading before them. So I simply deleted all of
the data from my pd-presetmemory log (in a text editor), which I had
forgotten to do: every time I was testing the preset function, Pd was
adding every preset I used for testing to the log and saving it.
I added a "Clear" button and problem solved.<br>
Is there a maximum file size that Pd will read?<br>
Interestingly, I could still open the patch in a text editor and it was
all there, but if I added anything to the truncated version of the
patch and saved it in Pd, it actually deleted all the truncated
stuff. It was only a little over half a megabyte when it started
truncating, which doesn't sound right...<br>
<br>
Anyway, I fixed everything last night, and also proceeded to work out
the score-based tempo control, so things are looking pretty good.
When I get video playback set up I'll be ready to score some student
animations.<br>
This was great because it forced me to start deciphering patches in text format. Neat stuff.<br>
<br>
Thanks, Frank.<br>
-Chuckk<br>
<br>
>Ciao<br>
--<br>
Frank
Barknecht
_ ______footils.org_ __goto10.org__