@gentleclockdivider What would happen if someday the devs decided to add methods to [select]? it would end up breaking any patch which used [select] to match symbols without the symbol selector. You have to pick a path and stick to it or you end up with objects with exceptions and we have to memorize all those exceptions or constantly get bitten by them.

@gentleclockdivider List and symbol objects apply their selector to anything sent through them, the exception being [list store]'s right inlet which has to deal with methods like [set 1 2 3(. The selector tells the object how it should deal with the incoming data. You can just use [route - kick hat] instead of [select] and have it work just like in the Max/MSP version but then you will need a [list trim] after your [list store] to strip the symbol selector. Or you can just put a single [symbol] before the [select] and just run everything through it including the [list store] which is safer than individual as needed [symbol]s, won't have to worry about selectors at all this way.

@kazeko -audioaddoutdev should work here. Any errors printed? What is the output of -listdev when your interfaces are connected? You can save the pd log to a file when running headless by starting pd up with -stderr 2> log.txt, using that will overwrite log.txt with the stuff pd would normally print to the console, -stderr 2>> log.txt will append to log.txt instead of overwrite it.

@kazeko You can access the arguments with [iemguts/canvasindex] but it is rare that getting the arguments of a subpatch is useful and you would be better served by going about things in a different way. For those very rare times when getting the arguments is needed and sensible just stick something like this in the subpatch:

This will not work with a [loadbang], you have to trigger it some other way, there is no loadbang with a subpatch.

@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.