Thanks!
This works pretty well for me but Iām having a bit of trouble loading old sets - some of the simpler ones open up ok but lots of them make Pd crash and close. Maybe there are some of my homegrown instruments that are causing a problem but Iām not sure that all the sets that crash include them.
Iām afraid I wonāt be able to really fix crashes, as the crashes either happen in Pd or in an external. Maybe we can narrow down the source of the crash and sometimes it is possible to work-around a specific condition that trigger crashes.
Can you share a set that reliably triggers a crash? And can you specify your setup, OS, Pd Version, netpd as app or Pd and netpd installed separately?
What you could try - in case you want to investigate some more on your own - is the rename the instruments used in the crashing set one after the other so that unpatch wonāt find it and load the set. If the crash doesnāt happen anymore, you know which instrument is āresponsibleā.
just tried a few variations going back and forth between netpd 2.2 (where the sets still load ok) and 2.3. It seems I can fix a set by taking out ādynlibā and more specifically ārcompā but i havenāt yet seen whether this is always the cause of the problem.
I thought I might as well share a few of the sets I have kicking aroundā¦
the one I used for testing was āmybloodytribalthingā - it crashes 2.3 but works if I remove ārcompā.
actually it still crashes even with rcomp removed.
Iāve tried a few further stepsā¦
-reinstalled all the externals
-put all the old versions of netpd out of the way so they canāt cause any confusion
-now just building simple setups in 2.3.0 and saving them then reloading them directly - lots of crashesā¦
Can you specify a set of yours that crashes almost reliably? All the ones I tried do not crash here. If I have a set that crashes, I can at least look with gnu debugger where the crash occurs.
Iām not sure if thatās helpful at all, but you can print all the messages received to the Pd console. Enter
/debug from on
into chat. Messages are printed right before they are executed. If always the same message is the last before the crash with a certain set, then this might give you hint which instrument causes the crash.
Loading your sets is actually so much fun and really interesting for me and it saddens me that we cannot talk about those without the technical issues in our neck.
ahā¦ think iāve got closer to working it out - if i connect to the netpd server and then load sets it works for all of them! so i guess there is something in the new netpd version that does something with the server as a saved patch is loaded and it breaks when netpd is offline.