Hi all,

I'm patching a granular delay abstraction that I want to work as a sort of module in a modular system. Here's a simple example:

Now, here's the behaviour I'd like to achieve: when nothing is connected to the right inlet, the grain_size_jitter slider works as a control for how much randomness is applied to the "size" of each grain every time a new grain is created. But when there is a signal connected to the right inlet, then the same slider would act as an attenuator for that incoming signal, and this attenuated signal goes on to alter the "size" parameter (rather than it being randomly changed). Does anybody have any suggestion on how I might go about it?

Of course I could have two sliders (one for the random jitter and one for the attenuator), but I'd still have to render invalid the jitter one whenever there is a signal connected, because if I'm sending a signal in I don't want it and the randomness to be both active. Besides, it seems neater to have only one slider.

Thanks a lot in advance.

If you don't mind using externals. you can use [iemguts/canvasconnections] to detect whether anything is connected to an inlet.

@LiamG Thanks I didn't know about the object but unfortunately it doesn't seem to work with signal inlets.

It's working fine with inlets~ for me. The following patch gives a 1 if the inlet~ is connected to anything and a 0 otherwise.

If I wanted to query the second inlet, the correct message would be "inlet 1".

@LiamG It works! I didn't read the help file properly. By connecting [bang~] to [inlet n( it updates in real time. This is exactly what I was looking for, thanks a lot.

@LiamG @weightless As I understand [canvasconnections] you would need to use it for the container patch interrogating inlet "one" (if its the second inlet) for your object [grainy-whotsit]........
So from within [grainy-whotsit] use [canvasconnections 1]....... maybe, to look "up-one-level"?
David.

@whale-av I put [canvasconnections] in the abstraction that contains the inlets as shown by @LiamG and it works, since the logic to switch the slider functionality is inside the abstraction.

[bang~] is a bit heavy for this kind of thing. If it were me, I'd use a metro and save some CPU.

That's a good point, as the patch will be heavy enough.

Here's how to do it for multiple inlets in case it's useful for someone else. (try connection [sig~] to the various inlets in the main patch).
Inlet_status.zip

Thanks again for your help.

@weightless Ah.... I thought you needed to know if they were connected "outside" the patch...... not inside.... i.e if a signal cord is connected to the patch.....
David.