typos.. of course i meant [try soundfiler]...
but adding something
the second idea would be interesting because it would be fast to change a patch, if you highlight the object that is throwing errors from the pd console (or using find last error), if you want to catch these errors you can just rename the object prepending "try" to it, instead of repatching, what do you think?
Em Ter, 15 de jun de 2021 09:35, José de Abreu abreubacelar@gmail.com escreveu:
Just 2 innocent ideas to add to brainstorm,
1.) what about a special subpatch? like pd-try, or just try, it could work as a normal subpatch, but with a mandatory outlet that would catch errors for the objects that live inside it
just like we can open a [pd] object or a [clone] object, [pd-try something] would be the same but with an added outlet for errors
2.) another idea would be that try just loads the object in its first argument (and passes the next arguments for that object creation) with an added outlet if this object throws an error
so you could use [try soundifiler], and this would be a normal soundfiler that gets one more outlet
i like the catch idea, just thinking about other options too
Em Ter, 15 de jun de 2021 05:34, Peter P. peterparker@fastmail.com escreveu:
- Christof Ressi info@christofressi.com [2021-06-14 22:35]:
that's an excellent idea!
I think it could work like this:
[catch] has one inlet and two outlets. If you send a message to the
inlet,
Sounds good, but please don't call it [catch] for the reasons given earlier (confusion with catch~).
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list