Andy Fennesz

I'm getting this error, and the Console is pointing me to relatively simple objects and patch aspects: add, subtract, sig~, selector, etc. Infinite recursion is a loop, right? I can't fathom where a loop is happening. Like one of the problematic sig~ objects is literally just monitoring an oscillator output.

Also, sometimes the Console locates the problematic object for me when I click the message, but sometimes it doesn't seem to highlight anything. How do I locate the object in the latter case? Thanks for your help.

I'm getting this error, and the Console is pointing me to relatively simple objects and patch aspects: add, subtract, sig~, selector, etc.  Infinite recursion is a loop, right? I can't fathom where a loop is happening.  Like one of the problematic sig~ objects is literally just monitoring an oscillator output.

Also, sometimes the Console locates the problematic object for me when I click the message, but sometimes it doesn't seem to highlight anything.  How do I locate the object in the latter case?  Thanks for your help.

I'm getting this error, and the Console is pointing me to relatively simple objects and patch aspects: add, subtract, sig~, selector, etc.  

msp-object-inputs-not-satisifed-likely-due-to-infinite-recursion

can't tell for sure without seeing the patch, but i have a feeling you're making a common mistake:

sig~ doesn't take signals... it only takes events and turns them into signals; use 'snapshot~' to monitor an oscillator output(i assume the 'oscillator' in your patch you mentioned is a sample-rate/signal one, this could cause problems if sig~ is turning a sample-rate signal into a sample-rate signal... or if you were hoping to use its output for something that expected events while it only outputs a signal, etc..)...

also, in that latter case you mentioned, not much else you can do... recursion can make error reporting go by too fast to properly report the exact point of a problem(luckily it's very difficult to run into recursion without it being an instant problem upon making the one wrongful connection, so usually you just need to remember only a few of the last steps you took or undo up to the point it stops complaining).

can't tell for sure without seeing the patch, but i have a feeling you're making a common mistake:
sig~ doesn't take signals... it only takes events and turns them into signals; use 'snapshot~' to monitor an oscillator output(i assume the 'oscillator' in your patch you mentioned is a sample-rate/signal one, this could cause problems if sig~ is turning a sample-rate signal into a sample-rate signal... or if you were hoping to use its output for something that expected events while it only outputs a signal, etc..)...

MSP object inputs not satisifed, likely due to infinite recursion?