hi folks! first thing i'd like to ask is where the application crash logs for PD are stored for Windows 10. i'm having an extremely frustrating time getting PD 0.50 64bit to perform reliably and stably.
the latest crashes are a result of a new preset system i'm using that sends positions of controls from a Unity created interface via OSC to PD. i suppose it might be an issue of too many data packets but i don't think i'm sending it gobs of data (maybe 60-70 controls total). however making the preset change from my interface makes PD crash. this is in addition to crashes and freezes that i get generally, especially when i configure MIDI or audio.
so i figure the first step is to look at the crash logs to see what part of PD or possibly a external, makes it crash. thanks to advice from others, esp Lucas, regarding ASIO, i'm getting better low-latency response from the audio at least, but overall it's still barely alpha stable in a performance setting. any advice appreciated!
scott
On 10/16/2019 1:04 AM, Scott R. Looney wrote: i'd like to ask is where the application crash logs for PD are stored for Windows 10
Hi,
Press the windows logo key on your keyboard and type "event". The "Event Viewer" app will be listed. Start it.
On the left pane go to "Windows Logs / Application".
On the right pane go to "Find" and type "pd.com"
On the lower part of the center pane you get the report of the crash (it might include the name of the [external].dll involved in the crash)
Mensaje telepatico asistido por maquinas.
so i figure the first step is to look at the crash logs to see what part of PD or possibly a external, makes it crash. thanks to advice from others, esp Lucas, regarding ASIO, i'm getting better low-latency response from the audio at least, but overall it's still barely alpha stable in a performance setting. any advice appreciated!
hi,
i just experienced a similar crash-scenario like scott did.
it happens when i send lots of OSC data (from MAX in that case) too fast to PD with the vanilla [netreceive] object as receiver. "too fast" means that i dumped a huge list of camera formats (~ 50 symbols) all at once to OSC.
there's no crash when i use IEMNET's [udpreceive] instead !
tested on PD 0.48 - 0.50 on a Windows 7 / 64bit system
best
oliver
hi Oliver - thanks for the advice! i was thinking of slowing the transmission speed as a solution, but i'll try it with iemnet library later today. incidentally i did try this data dump scenario via OSC on my macOS machine from the Unity Editor and it had no issue with PD at all. BTW i'm using the standard vanilla install of .50.0 from Miller's site, 64 bit in both cases (Mac and Windows).
best, scott
On Thu, Oct 24, 2019 at 5:28 AM oliver oliver@klingt.org wrote:
so i figure the first step is to look at the crash logs to see what part of PD or possibly a external, makes it crash. thanks to advice from others, esp Lucas, regarding ASIO, i'm getting better low-latency response from the audio at least, but overall it's still barely alpha stable in a performance setting. any advice appreciated!
hi,
i just experienced a similar crash-scenario like scott did.
it happens when i send lots of OSC data (from MAX in that case) too fast to PD with the vanilla [netreceive] object as receiver. "too fast" means that i dumped a huge list of camera formats (~ 50 symbols) all at once to OSC.
there's no crash when i use IEMNET's [udpreceive] instead !
tested on PD 0.48 - 0.50 on a Windows 7 / 64bit system
best
oliver
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list