I am thoroughly stumped. I'm using the random object and it won't bang. I've taken a screenshot and provided the pd file.

There's no need to figure out what's going on really, just look at the very top part near the toggle. It's the first random object that's banged. When you run it you'll notice it doesn't bang and the error message "error: random: no method for 'float'" comes up. It operates despite this but it doesn't do what I intend to do because this object is acting up. This random number is inputted directly into an expression. Any insight is greatly appreciated.

UPDATE: forgot to include the files... doh!

http://www.pdpatchrepo.info/hurleur/4noteRandomSequencer.pd

Is it possible without a patch to initialize a python program from within pd, then to receive the result from the python program? If not, what would be the most painless method to accomplish this?

I just started messing around with the tuio simulator and it will work anywhere from 5 seconds to a minute before the pd window that has the code in it will freeze and I won't be able to unlock it. At that point I can restart both pd and the simulator to have this same thing happen again.

It seems to also be triggered if I move one of the simulated fedushels 360 degrees around another fedushel.

Has anyone had this problem before? or know of any reason why this would happen?

I want my username to be "cbslyfox" instead. I won't ask you to change it again.

Thanks

This irks me a bit. I've finally become comfortable counting with 0 as my first number and now zl slice starts with 1?? WHY?????? It's not even consistent with the rest of pd! Every other object I've encountered in pd starts counting at 0 - so why the exception?

Just to make sure, do lists start counting with 0 or 1 as their first element?

I'm not saying you should change it... I'm just letting you all know it does bother me and it inspired me to write this.

Thanks for reading.

For some reason the text for any objects I make in pd will go over the box length. When I see videos of people working in pd they don't seem to have this problem.

It's not a big deal but it's aesthetically unpleasing, and also makes for a much more cluttered look on anything I make. Is there any way to remedy this?

I've included a screenshot to show what I mean.

http://www.pdpatchrepo.info/hurleur/textoverboxes.jpg

I didn't find it in the help index but maybe I missed it? Was it just considered not useful?

In the tutorial I'm learning pd in (it's a few years old), the instructor stresses connection order to insure the functions fire as intended. I double checked this with a list (changing the order I connected the values in the list) and I experienced no difference when I printed it.

Is this a special property of the list (pack) function? or does connection order not matter anymore? (meaning triggers can safely be more rarely used)

For some reason if I output midi from pd to a saved ableton file that I had routed before I saved it, it will either work for one bang, or a couple and then stop working completely. Sometimes it won't even work from the start.

Now if I use the same exact program on a new, unsaved ableton file, it will work indefinitely, no problems at all.

I know it's not the midi router either because the same thing occurs when I use midiyoke or loopmidi.

It's a bummer too because if it can't be fixed then I can't do any midi routing with pd on any files I've saved in ableton, I can only do it one time on a new project before I save it. I don't know if the fact that the file is saved or not is the root cause of this problem - it's just the only correlation that I've detected.

I did notice that when I open these saved files that the lettering in the midi input channel is colored orange to indicate there's an error. When I pick a different available port the orange goes away with no error signaling. But then this problem occurs.

I'm definitely routing properly since I can get it to work perfectly in a new, unsaved ableton file.

Does anybody know what's happening here?

Thanks in advance.

Hi, this is my first post here and I really love this program as I'm learning it! I've been following a tutorial on youtube and in it, when the instructor presses the bang button on his, the whole chain (or patches) loops until he sends a stop message. Mine doesn't do this. I have to continually click the bang to step through it.

Is there any way I can toggle an auto-loop on and off?

Here's a clip of what I'm talking about (skip to 9:25):

Thank you very much!!