Thank you all, particularly thank you Christof!

That the error messaging does not work within cloned abstractions the same as it does in normal patches was the key to finding the error!

Replacing the abstraction within clone with a single instance made it possible to use the last error find option available.

Thank again,
Sebastian

On 17 Jul 2020, 00:12 +0100, Christof Ressi <info@christofressi.com>, wrote:

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
_______________________________________________
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list