@FFW said:

EDIT: you stack computation branch and they are released deepest to shallowest so numbers are reverted.

I don't understand your comment. Why aren't the numbers coming out in the order in which they were computed? This seems like a bug to me. Is this behavior documented?

@FFW I had the control flow correct in my example. Adding [trigger] didn't fix the problem. Here's my example with [trigger]. The numbers incremented in the [i] object still come out in the wrong order. It appears that they are coming out in LIFO order when they should be coming out in FIFO order.

loop_test.pd

I'm trying to increment two sets of numbers in a loop. One set comes out in the correct order; the other comes out in the reverse order. How can I make this work correctly? I've attached a simplified patch that demonstrates the problem. It should print
0 0
1 1
2 2
3 3
4 4
Instead it prints
0 4
1 3
2 2
3 1
4 0

loop_test.pd

Have you set Input Devices in Audio Settings?

@whale-av Thank you.

@whale-av Thanks! That gives the syntax of -mididevout, but doesn't give enough information for me to understand what it does. What does
-audiooutdev 1,3
actually do?
Does specifying it in Setup->Preferences as described in this post
https://forum.pdpatchrepo.info/topic/2980/more-midi-output-device-options-needed/4
change the behavior of the device list in MIDI settings?

I'm having issues with using multiple MIDI devices. I think the -mididevout option might help, but I can't find any doc on it other than what's in this post:
https://forum.pdpatchrepo.info/topic/3582/how-to-specify-the-midi-channel

Where can I get the specifics on how -mididevout works?

I have this problem too. I have a number of MIDI devices, and they can't all be plugged in at the same time. It's very annoying to have to stop and restart Pure Data every time I plug in a MIDI device, especially since I'm usually working with multiple patches at the same time, and it's a pain to get back to where I was before restarting Pure Data.

I was looking at writing my own bezier function to generate curves when I ran across this option to generate a bezier curve in a graph. I was hoping that it would do more than make a nice looking display.

Arrays have an option to generate a bezier curve. In the attached patch, seven points are put into an array and displayed as a bezier curve. It looks nice, but does it have any function? When you read the array, you just get the points you put into it, not the points on the bezier curve. Is there a way to use the bezier curve as a wavetable or envelope, instead of the original seven points?

bezier.pd

I've been avoiding externals since the demise of Pd-extended, but I'll check out tabgen. Thanks.

I'm creating a wavetable using sinesum to write harmonics to an array, which works fine for integer overtones. I'd also like to be able to be able to write non-integer overtones and undertones to the array. Is there a way to do it with sinesum or some other function? Or do I have to make a complex expr to write a combination of integer and non-integer overtones to the array?

Thanks, that worked. Is there some Pd doc that I don't know about? I keep running into basic things like this that don't seem to be documented anywhere.

I'd like to make help files for my Pd modules that work like Pd object help files, but I can't find any documentation on how to do it. Where is this documented?

@whale-av Thanks! What is the purpose of the third and fourth outlets? How should I used them when generating stereo output?

[rev3~] has two audio inputs. It it true stereo? The help file doesn't say. It just shows just a single audio source that is routed directly into one input and inverted into the other, but doesn't explain why it does that.

Also, [rev3~] has 4 outputs. What are the functions of the third and fourth outlets? The help file doesn't explain it.

@EEight Thanks, I'll give that a try.

I upgraded to Pd 0.55.2, and still get the same message. How can I find out what the problem is?

I occasionally get an "Audio I/O error" message in red on the Pd console. I'm not getting any other clues what the problem is. The patch sounds the same whether I get the message or not. What's the problem? What's the fix?

This is happening on Windows 10.