Hi all,
I have had, for a while, an issue opening patches, that I was able to open before without problems, and now I get the message: "watchdog: signaling pd..."
I have tried calling pd with -noaudio and -nomidi, but it still gets stuck.
I am on ubuntu 16.10 and pd 0.47-1, but this has been happening in several ubuntu versions.
This happens to certain patches and then I cannot open them again, it is as if they were locked. It is currently happening to one I used yesterday!
any pointers?
J
On 01/20/2017 04:18 AM, Jaime Oliver La Rosa wrote:
This happens to certain patches and then I cannot open them again, it is as if they were locked. It is currently happening to one I used yesterday!
i guess one of the objects in their fails to create within reasonable limits. so i would do:
- disable rt (this will make the "signaling pd..." message disappear,
but the loading might still hang. I guess it is still worth trying it out.
- enable "-verbose -stderr" to see what Pd is actually trying to do.
- get a list of all the objects used in the patch, and check whether
there's one in there that could block in the constructor.
fgmrdsa IOhannes
calling pd with -noaudio and -nomidi
- enable "-verbose -stderr"
also don't forget to try "-noloadbang", it could help too.
Antoine Rousseau http://www.metalu.net http://metalu.net __ http://www.metaluachahuter.com/ http://www.metaluachahuter.com/compagnies/al1-ant1/
2017-01-20 9:40 GMT+01:00 IOhannes m zmölnig zmoelnig@iem.at:
On 01/20/2017 04:18 AM, Jaime Oliver La Rosa wrote:
This happens to certain patches and then I cannot open them again, it is as if they were locked. It is currently happening to one I used
yesterday!
i guess one of the objects in their fails to create within reasonable limits. so i would do:
- disable rt (this will make the "signaling pd..." message disappear,
but the loading might still hang. I guess it is still worth trying it out.
- enable "-verbose -stderr" to see what Pd is actually trying to do.
- get a list of all the objects used in the patch, and check whether
there's one in there that could block in the constructor.
fgmrdsa IOhannes
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/ listinfo/pd-list
Thanks all!
It seems that changes in [declare]'s behavior were creating problems finding certain libraries of externals. the -noloadbang flag allowed me to change this behavior and now things load normally...
best,
J
On 01/20/2017 08:01 AM, Antoine Rousseau wrote:
calling pd with -noaudio and -nomidi - enable "-verbose -stderr"also don't forget to try "-noloadbang", it could help too.
Antoine Rousseau http://www.metalu.net http://metalu.net __ http://www.metaluachahuter.com/ http://www.metaluachahuter.com/compagnies/al1-ant1/
2017-01-20 9:40 GMT+01:00 IOhannes m zmölnig <zmoelnig@iem.at mailto:zmoelnig@iem.at>:
On 01/20/2017 04:18 AM, Jaime Oliver La Rosa wrote: > This happens to certain patches and then I cannot open them again, it is > as if they were locked. It is currently happening to one I used yesterday! i guess one of the objects in their fails to create within reasonable limits. so i would do: - disable rt (this will make the "signaling pd..." message disappear, but the loading might still hang. I guess it is still worth trying it out. - enable "-verbose -stderr" to see what Pd is actually trying to do. - get a list of all the objects used in the patch, and check whether there's one in there that could block in the constructor. fgmrdsa IOhannes _______________________________________________ Pd-list@lists.iem.at <mailto:Pd-list@lists.iem.at> mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list <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
-
Antoine Rousseau -
IOhannes m zmölnig -
Jaime Oliver La Rosa