Hi,
The only object I am aware of being able to produce an error like this is the [inlet~]
This error message is also shown whenever you send a bang to any signal inlet - except for the main inlet. Try to send a bang to the right inlet of [+~], for example.
The 'last error' feature does unfortunately not give a result or clue.
Maybe the offending object is inside a cloned abstraction? Pd can't locate such errors (yet).
Christof
PS: if you want to start a new thread, don't reply to an existing e-mail.
On 17.07.2020 00:48, Sebastian Lexer wrote:
Hi,
Getting desperate after spending hours to locate the error "inlet: expected 'signal' but got ‘bang’” I am getting from a fairly huge project, running in pd 0.49 on a raspberry pi.
The only object I am aware of being able to produce an error like this is the [inlet~]. After checking all subpatches I have not found any [inlet~] that has any non-signal patch cords connected.
Is anyone here aware of any other objects that might produce the above error message? The 'last error' feature does unfortunately not give a result or clue.
Thanks, Sebastian
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list