Pinho

Hi...I've been wondering...is there any way to know if an object has a patchcord connected to it ?

Hi...I've been wondering...is there any way to know if an object has a patchcord connected to it ?
thanks


knowing-if-an-object-has-a-patchcord-connected-to-it

I don't think so. I already looked for something similar, which is to know how many outlets an object has. It seems to be not possible, either with thispatcher, or with javascript. Maybe by programing its own external (can anyone confirm) ?

with javascript, you can know if a patcher has parent patchers, if that helps (

https://cycling74.com/forums/simple-question-detect-if-a-patcher-is-a-parent-patcher-or-a-subpatcher)

with javascript, you can know if a patcher has parent patchers, if that helps (https://cycling74.com/forums/simple-question-detect-if-a-patcher-is-a-parent-patcher-or-a-subpatcher)


This is a super old post, but I thought I would shed some light on this for anyone else looking for this info! 

Using some delay magic and some metros, you can set-up what seems to be a nifty way of detecting whether a patch cord is connected to another. Unfortunately this requires a metro so whatever you're sending into the patch will have to be tamed if it's destination is trigger sensitive.

CheckConnectivity.maxpat

testSubPatch.maxpat

It's possible that this may not be the safest technique around due to my lack of understanding on the max msp timing system, but essentially the metro spits out a bang every 50ms, triggering whatever variable you want to be sent through to a patcher. In this example I'm simply sending the number 7 which could be used to control a parameter inside the subpatcher. Inside the subpatcher a delay set at 100ms, but this could be anything above 50ms, is triggered by the incoming signal which is turned into a bang (buttons act as detectors for activity). As the delay is over 50ms, the delay doesn't have time to fire before another bang is sent in, thus resetting the delay and no bang being sent out the other side. When the patcher has it's cord disconnected, there are no recurrent bangs coming into the patch and finally the delay can fire its stored bang, triggering the toggle. The button detects this and turns on the final toggle which acts independently from the delay toggle.

For interests sake, I'm modelling a modular synth inside of max for an exhibition on sound! This is useful in testing the beast whilst I'm devloping it, such that I can model the "plugging" and "unplugging" of patch cables to different modules. 

Give me a shout if you need any further explanation!

This is a super old post, but I thought I would shed some light on this for anyone else looking for this info! 

Using some delay magic and some metros, you can set-up what seems to be a nifty way of detecting whether a patch cord is connected to another. Unfortunately this requires a metro so whatever you're sending into the patch will have to be tamed if it's destination is trigger sensitive.


How it works: 
It's possible that this may not be the safest technique around due to my lack of understanding on the max msp timing system, but essentially the metro spits out a bang every 50ms, triggering whatever variable you want to be sent through to a patcher. In this example I'm simply sending the number 7 which could be used to control a parameter inside the subpatcher. Inside the subpatcher a delay set at 100ms, but this could be anything above 50ms, is triggered by the incoming signal which is turned into a bang (buttons act as detectors for activity). As the delay is over 50ms, the delay doesn't have time to fire before another bang is sent in, thus resetting the delay and no bang being sent out the other side. When the patcher has it's cord disconnected, there are no recurrent bangs coming into the patch and finally the delay can fire its stored bang, triggering the toggle. The button detects this and turns on the final toggle which acts independently from the delay toggle. 

For interests sake, I'm modelling a modular synth inside of max for an exhibition on sound! This is useful in testing the beast whilst I'm devloping it, such that I can model the "plugging" and "unplugging" of patch cables to different modules. 

Give me a shout if you need any further explanation! 

knowing if an object has a patchcord connected to it