@FFW You can dynamically re-create the connections, but of course you need to know the object numbers of the objects in the main patch that you want to connect to the inlet/outlet.
I have had to do this building patchable input /output cords in a matrix..... matrix~.zip
Everything inside [matrix~] is created according to its arguments and then the test patch connects to the abstraction.
The test (matrix-test~.pd) works in extended.... but strangely the object numbers have changed when opened in vanilla. Inside [matrix~] everything creates correctly in both versions.
It should create this....... which demonstrates the principle...

It is best to recreate your main patch with the objects you will want to connect being the first objects created... and then copy back the rest of the patch and connect those objects.
Then if you modify the patch later you will not change those object numbers and break the dynamic cord creation.
David.

How can I actually see the routed list in a list box without using list store ?

If you look into the help file of the list box, you'll see that the list selector is always needed if the list starts with a symbol. So you need to convert whatever you wanna see to a list message, and the help file of [route] uses the [list] for that.

So, it should be obvious that you simply can't send a non list message to the list box. If you're asking how should it work without [list store], well, you can't, you need something. If you want an alternative to it, what is the problem with it? What else would you like and why? And if you expect somehow to send a non list message to list box, you simply can't and this is a very basic Pd thing, dealing with its data types. So use just use [list] or whatever...

As for the dollar sign thing, it's also another very basic Pd thing that concerns the management of selectors and data types, and it is treated throughout the documentation, one of which is the help file of [list].

So yeah, this is yet another request on my part to kindly insist yet once more, after many times, that you take your time to read the manual and help file of objects if you want to work with Pd. You've been using it for quite some time and you have too many questions that could be simply be answered if you took the time to read tutorials, the help files and the manual.

And simply don't expect Pd to be the same as MAX, they're different pieces of software (there's even a section in the manual that tells about their differences - it's section "2.11. Pd vs. MAX"). While you're at the manual, check "2.4.1. Message types (selectors) and numerical precision".

As for the help files, I told you to check the help file of all these involved objects, the list box, the [route] object, and the [list] object, which has a [pd about-lists] subpatch that should answer your question.

The help file of message boxes also talk about dollar expansion and has a section that explains all this in a subpatch called [pd dollar-variables].

The fist chapter of my Live Electronics Tutorial is "01-Pd.Quickstart" and gives you a good and quick overview, you should look into subsection "2.Syntax". This comes as part of PlugData, which you're using. I realized now that the 'control tutorial' does not have a good example about this, so I will add it. You should read that too anyway.

So yeah, I'm not really answering your question, but I'm telling you where you can find answers, and please understand my situation. I wrote a tutorial of my own, I revised and rewrote all the help files, I revised, wrote new sections and rewrote most of the Manual. I revised the tutorials, all in the hope that people would read them and find answers and not ask such basic questions over and over. And also so me or others wouldn't have to keep explaining the basics. Others can come in and teach you if they want to, but I'll just reinforce that you really should do that.

This is ok when someone just got here, is a newbie, and wants some guidance, like pointers to the documentation, but it's been a while you joined the community, and you're doing a lot of work, and you seem to resist and simply not do the basic homework. Personally, I feel this is abusing our desire to help others, but that's just me.

So please, just read the (blip) manual. And if you're still confused, if you haven't found what you need, if it's misleading somehow, I'd be more than glad to explain it to you and improve the documentation.

I'd love to hear from you things like "hey, I read this help file and I couldn't see something about xxxx", or, "I didn't find anything about message types in Pd, where can I read and check?". You know?

cheers

@rosemyxine said:

One other thing was for the outputting triggers - when an active step emits a bang, that bang needs to send a burst of CV out the Lich's gate output to make a trigger.

Oh, I missed that part of the question. Triggers are usually flat pulses. vline~ would be a good choice.

bang-pulse.pd

The last number in the message box controls the pulse duration -- should probably be shorter than 50 ms? But I don't know how your analog kit will respond.

hjh

Hey @ddw_music,
Please, please, please. I am not criticizing you. I honestly am just trying to understand. Sincerely and respectfully.

You have honestly helped out a great deal. Seriously. I was having to do somethings and changing my patches in ways that was rather disappointing to say the least or upsetting to be blunt. Your explanation and your persistence has helped me to understand better.

How can I make it up to you for helping out @ddw_music? I would gladly provide you compensation or some other way to make it up to you.

FYI, if the ofelia is opened or was opened, then the file cannot be made without the leading slash (I think I got my slash terminology reversed?) In fact to prove this to my self. I used mkdir and rm -r to create and delete a directory without the leading slash, then I opened up ofelia and it did not work. So, I assume ofelia rudely takes over shell or command or something else.

And you also provided a good point as well that I need a leading slash when going with an absolute path. Thank you.

I honestly did not know the nuances of of the slash usage which I understand a bit better now.
And thank you @old for the additional information. I think pd starts in the root directory, if I am understanding the terminology correctly.

@old, thank you as well for the response!

@rph-r The only way Pulse could be the culprit is if you are running jack/portaudio through Pulse, but that is generally not done since Pulse has too much latency for realtime audio. I can't speak of portaudio (never used it) but with jack the general setup is to either have Pulse as a client of jack or have jack kill Pulse when it starts and restart Pulse when it shuts down. I would guess that the later is your setup, Pulse configures your audio card and jack is not great at doing that so just accepts what Pulse set it at. You might be able to get jack to set it properly or configure Pulse to use 44.1. Some soundcards jack just can not configure as far as I can tell so if you are using Pulse and having jack kill Pulse you need to either configure the soundcard manually or do it in Pulse before starting jack, I have to do this with my laptop, jack can not select between headphone and speaker outs and will use which ever is enabled when it starts.

Edit: I suppose it could also be the case that your soundcard is 48k only?

Hello patchers! I have been watching a tutorial series by Really Useful Plugins where they recreate yamaha dx7 synth and repeated after them. Finishing, i ran into a problem related to polyphony.
So, the problem is when i press a note it plays all 8 voices at the same time, when i play other note, it keeps playing previous ones with the current one. This may happen due to ADSR, but i checked everything several times and still cannot solve it. I admit that the solution may be pretty obvious, but i am new to this sorry. I checked manuals and tutorials, but they weren't very useful.
Here is the zip with the patch.
dx7.zip

1. Here are poly and clone themselves
   
2. Here is dx7-poly object, which is cloned
   
3. On previous photo the $0-oscmsgs is sent, here is where it is delivered
   
4. ADSR object which is stolen from pd documentation examples
   
   I hope very much for your help! thx

@ddw_music It might not be a bug. Objects should never have the same name but that seems to be how it is.
Plugdata has loaded the vanilla [line~] object, but has picked up the object reference for [cyclone/line~] when it searched for the help file, simply because it found it first? The help files are not built in to the Pd binary. If they were then the problem would not arise, or more likely be reversed and cyclone help would never be found.
But the real problem is the use of the same object name.
Anyway, the author has already spotted this thread and submitted a bug report.

@gentleclockdivider You probably know, but if you set the Pd command window to at least log level 2 (normal) you will see where Pd has searched for an object or a help file. Maybe that is not the same for plugdata, but if it is then you will see all the directories that were searched when looking for the help.
As you discovered, as [line~] is "built-in" to the Pd single binary no search is performed, and the vanilla [line~] will always be loaded unless as you say the cyclone library has been specified.

As you have also found....... [cyclone/line~] does accept a maximum of 128 natoms.......... https://github.com/porres/pd-cyclone/blob/master/cyclone_objects/binaries/audio/line.c#L179
.... but as a long list (no commas). It works out separation of the pairs by the odd and even atoms in the list.

So is it possible that it was it [cyclone/line~] that you tested in your opening post? .... as you separated the pairs in that screenshot?
You can tell by the right outlet...... but the help message hides where it could be in the screenshot?
It might be worth your time to find out what search paths are operating for your different forks of Pd.
I wonder whether some of them are sharing playlist files or preferences in the registry.
David.

A few years ago I made a convoluted patch (no pun intended) that outputs a single sample 1-valued pulse on each of its [outlet~]s sequentially in round-robin fashion in response to a positive transition on its [input~]. It's pretty gruesome so I don't want to post it here, but for the morbidly curious suffice it to say it's based on cascaded shift registers with the last stage fed back to the first stage and requires [block~ 8 1 1] to work reliably at 2500 Hz. Anyway, it behaves like this:

• positive transition seen on [input~] -> pulse first [outlet~]
• positive transition seen on [input~] -> pulse second [outlet~]
• positive transition seen on [input~] -> pulse third [outlet~]
  ...
• positive transition seen on [input~] -> pulse last [outlet~]
• positive transition seen on [input~] -> pulse first [outlet~]
  ...

Anytime I look at my code I gag. Does anyone in the esteemed readership of this forum have a suggestion on how to do this in a less offensive way? I don't care about the signal specifics of the inputs and outputs as long as they are at audio-rate and easily detectable within a constant number of samples. I would gladly accept consistent latency in exchange for efficiency and elegance. Extra respect if the number of outputs can be easily changed without dynamic patching.

I am working on a piece that will turn on and off multiple motors at certain time based on certain variables.
What I'm trying to do is sequence like this:

sequence 1:
button is pressed

motor 1:
start at min 00: random pulse(ON time of 35 ms) every 7 - 10 sec
motor2:
start at min 01: random pulse(ON time of 35 ms) every 5 - 11 sec
motor3:
start at min 04: random pulse(ON time of 35 ms) every 3 - 13 sec
motor4:
start at min 06: random pulse(ON time of 35 ms) every 7 - 10 sec
motor5:
start at min 08: random pulse(ON time of 35 ms) every 5 - 12 sec
motor6:
start at min 10: random pulse(ON time of 35 ms) every 4 - 10 sec
all motors run

when button is pressed again (button count = 2):
sequence 2 starting:

motor 1:
continue random pulse(ON time of 35 ms) every 5 - 10 sec
stop after 01 min
motor 2: continue random pulse(ON time of 35 ms) every 3 - 12 sec
stop after 04 min
motor 3: continue random pulse(ON time of 35 ms) every 7 - 12 sec
stop after 10 min
motor 4: continue random pulse(ON time of 35 ms) every 3 - 8 sec
stop after 16 min
motor 5: continue random pulse(ON time of 35 ms) every 5 - 16 sec
stop after 18 min
motor 6: continue random pulse(ON time of 35 ms) every 7 - 10 sec

-- now only motor 6 is running >> button pressed>> last motor that running(motor 6) is stops.

sequence 3:

all motors pulsing together every 7 seconds for 2 minutes
after 2 minutes elapsed all motor stops.

how can I implements the above in PD?
how is possible to timing events without using metro rather something more accurate?

Thanks

Hi, I'm just trying to figure out how to work with this object and the help file is really confusing to me

Firstly- can any kind soul point me toward a better resource for understanding how to use this object?

Secondly, I'm going to point out a few of my confusions with the help file, specifically in [text define]:

• "text define" maintains a text object and can name it so that other objects can find it (and later should have some, alternative, anonymous way to be found)."
• • What does that second half mean? An "anonymous way to be found" sounds like an oxymoron to me.

• When i click the message box [write text-object-help.txt] that is connected to [text define -k text-help-1], I get an error in the console that reads "text-object-help.txt: write failed"
• • Why should something in a help file fail like this? There's nothing apparent in the help file to explain the error. I'm running realtime Purr-Data on Manjaro's latest realtime kernel, everything is updated.
• Next to the message box [sort], there's just a comment that reads "comment"
• • lol what?
• It seems like [text define] creates the text file with its third argument (e.g., [text define -k file-name-here]" However, the help patch is reading from a file called "text-object-help.txt" and when the file is opened, "text-help-1" is on the top of the window.
• • Dear god, what is going on?

If anyone feels like helping me out here, I would gladly help put together a better help patch. Or maybe I'm just reading this totally incorrectly.

Thanks continually for all of your support, everyone!