@RT5000 [iemguts/canvasobjectposition]. The iemguts library has a selection of objects for manipulating patches/objects.

@Ice-Ice I believe what is going on is that pd finds and loads the external but the external fails to find the csound files it needs to to run. there is a csound6.dll or the like which is not installed anywhere [csound6~] can find it so it fails to load, it is not where who ever compiled the external had it on their computer. What else is printed in the log window that you cut out?

Edit: Also, how did you install Csound? did you use the installer or the binaries? Guessing that the installer would put things were they need to be for [csound6~] to find them but the binaries would not and will require you to put things in their proper places.

@johannem I assume you are talking about the screen on the Push? Quick look and it looks like that is controlled through sysex messages so it will not be an issue to control that from pd and the messages look to be documented so it will not be too difficult to make it work. For the encoders, they look to use relative CCs so turning to the right sends a value of 65-127 depending on how fast you turn the knob and to the left sends a value of 64-0, so you need add up the value its sends, not difficult and I have an old abstraction in this thread which handles them and allows you to easily use a single encoder for multiple parameters. The abstraction is from when I was learning pd and probably is not the best way to go about things but it does the job. I think I may have reworked them but they are not on this computer, will check later and upload them if I did.

@rosemyxine Just use the first f of the pack for the bang and follow it with a [list split 1] or a [$2 $3 ...(

@soundproofskin said:

I don't know why the sound doesn't trigger when the message is banged with using symbol this way

Because you skipped over learning the basics, objects have hot and cold inlets, hot intlets produce output, cold inlets affect the object's state, vast majority of objects only have the left inlet as a hot inlet with the other inlets configuring the object but producing no output. Might want to dig into the manual, it will save you a good amount of time down the road. @lacuna's answer is actually the correct answer, I did not look close enough at your patch, as it stands you are reloading the sample every time you play it, only need to load it when the sample being played changes.

@soundproofskin Connect the [list split]s to the right inlet of the [symbol] and the [sel 0 1 2 3] to the left. Also, [unpack s s s s] will make things a bit neater than the [list split]s and as a general rule of thumb [pack] and [unpack] are more efficient than [list] objects so are a better way to go when you are dealing with short lists of a known number of elements.

@kkl You need to tell the [array get] how many elements to get, either a 1 sent to the second inlet or through arguments [array get array1 0 1]. Your counter likely also has an issue if you have sent a value other than 0 to the first inlet, if the counter works sending a 1 to the first inlet should send the first element through to the last element. Along with @lacuna's recommendation of the help files also good to check the help browser, control-b or open it through the Help menu, first item is Pure Data and in there you have lots of examples and the like.

@alexandros If I understand correctly, that method interrupts the decay curve and we can see that in the transition from the decay to the sustain, not as smooth as it should be? The way I do it is make every segment run from 0 to 1 and then scale and offset to the proper values. Much of the time I don't think it would matter, we would not hear the flaw in your method, if there is one, guessing based off of the image but don't really know since I am not completely sure what is in your abstraction. Here is roughly how I do it. Mostly posting to see if I understand and for the sake of discussion, if I do understand I think for most uses your method is more sensible.

@Vorg [reson~] from the cyclone library is a good bet for your filter needs.

@Oscillcreate The welcome to the forum thread pinned in the Technical Questions section is actually a thread about the importance of [trigger] and should answer your question.
https://forum.pdpatchrepo.info/topic/13320/welcome-to-the-forum

@porres A helpfile patch in the docs under 8. topics would probably get slightly more notice and it could also be a style guide/best practices for making helpfiles, maybe toss in a helpfile template in there as well to encourage those best practices.

@rph-r [savestate] runs after the abstraction is created and before [loadbang], I used a [loadbang] in the abstraction to load arguments which ends up deleting the [savestate] information. I added a [spigot] after the [loadbang] in the abstraction and any information coming into the right inlet will now disable the [loadbang], I believe this will solve you issue? Assuming I understand the problem, if this does not solve the issue an actual example patch demonstrating the issue would be helpful.
list-store51.pd

We can also make [savestate] happen after the [loadbang];

[del] and [del 0] are not actually zero delay, they delay it one event in the scheduler so makes that list bang after the patches [loadbang] fires. Generally you would not want to use this method and simply fix the abstraction in question, but could be helpful when using an abstraction from a library since your patch will not mysteriously break when you update the library or reinstall. Ideally you will be able to let the maintainer of the library know about the issue and they will fix it, but that is not always possible.

@gentleclockdivider said:

I wonder , is there also an option to get it into the symbol object by other means and not by writing it as an argument ?

That is essentially what the others do, they just use a message since [symbol] can not construct a symbol, only store a symbol for later use. For most uses the first is generally what you want but the others each have their uses. The second lets you change the $0 with the right inlet of the [f ] which can be useful for communicating between abstractions. The third and fourth offer different ways of constructing the symbol when you have more than two arguments, [pack f s $0] for example, symbol and float can be changed as needed. [list] objects are handy in that they can provide a default set of arguments to start with which can be changed as needed [list $0 dollarzero 1 2 3] for example or generally more useful [list store $0 dollarzero 1 2 3] since it makes it easy to change a single element.

@FFW You need to hide the gop and then show it to force redraw, send 0 then 1 to the third argument. You also will want to send [dirty 0( to the canvas or pd will think the canvas has been edited and prompt you asking if you want to save changes.
gop.pd

@gentleclockdivider Your symbol should be [symbol $0-miditopitch].

@willblackhurst Finally got a chance to finish this up. Got it working as an abstraction and added a few other features for both save and open dialogs. Also has the nice side effect that each instance remembers where in the file system it was when last used so decreases some of the headaches of [openpanel] and [savepanel]. Think I got all the bugs out. Requires [hcs/sys_gui] and a recent enough version of pd to have [file splitname].
spanel_opanel.zip

@KMETE [file patchpath]

@KMETE I did not implement the file playing, just the random file stuff but I think this should do you assuming you are using a somewhat recent pd. Added a toggle to delete the file from the list if you want it to never play the file a second time, wasn't sure if you wanted to avoid repeats or avoid ever playing a file twice.
rnd-file.pd

@rph-r You sure it doesn't store like the original? Just redownloaded it and it seems to work for me. The right inlet is just a [send] which sends to all the internal [list store]s right inlets, while that send is also used for the internal logic that internal logic is quite simple and I can not think of a situation where it would fail. Check again and if it still fails redownload to make sure nothing corrupted, if it still fails upload a patch demonstrating the failure so I can fix it.

@rph-r Forgot that [list store] was a much simpler object in 0.51, https://forum.pdpatchrepo.info/topic/14432/equivalent-of-list-store-insert-delete-pre-pd-0-52/2 is an abstraction that implements the methods added to [list store] in 0.52. Always forget about this.

Edit: You could also use [text] or [array] instead of [list store]