<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Yeah - my uDMX device locks up and needs a close/open with all the externals that I can get running. <div class=""><br class=""></div><div class="">I see the same behavior with the midi2udmx compiled max application they provide as well.</div><div class=""><br class=""></div><div class="">Maybe it’s a fundamental problem with the unit - or with my hardware…</div><div class=""><br class=""></div><div class="">That said - the compiled max application actually performs a lot better (doesn’t lag my system down. So I wonder if there’s a way I can further optimize what I’m doing in PD. I gotta stick with controlling it from the external so I can automate the open/close workaround :/</div><div class=""><br class=""></div><div class="">It might also be worth mentioning that I can’t even run any audio alongside this patch without intense blocking. I’ve been doing audio in a different pd instance for the reason.. but latency is pretty bad still.</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jun 13, 2016, at 12:36 PM, Lucas Cordiviola <<a href="mailto:lucarda27@hotmail.com" class="">lucarda27@hotmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" style="font-family: Calibri; font-size: 16px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><div class="">Ok,</div><div class=""><br class=""></div><div class="">I think that the PD part is Ok with the patch I gave you, at least to continue the tests.</div><div class=""><br class=""></div><div class="">In the manufacturer site there are more than 4 “externals”, Have you check them all?</div><div class=""><br class=""></div><div class="">You will have to restart Pd to switch between them.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><br class=""><font face="Courier New, Courier, Monospace" size="2" class="">Mensaje telepatico asistido por maquinas.</font><br class=""><br class=""><div class=""><hr id="stopSpelling" class="">Subject: Re: [PD] uDMX hanging/locking up<br class="">From: <a href="mailto:jmejia@anestheticaudio.com" class="">jmejia@anestheticaudio.com</a><br class="">Date: Mon, 13 Jun 2016 11:47:17 -0700<br class="">CC: <a href="mailto:pd-list@lists.iem.at" class="">pd-list@lists.iem.at</a><br class="">To: <a href="mailto:lucarda27@hotmail.com" class="">lucarda27@hotmail.com</a><br class=""><br class="">This is a much simpler table/array solution - thanks for that!<div class=""><br class=""></div><div class="">Unfortunately it hasn’t solved my locking up problems. (But maybe it’s made them less frequent/regular) I’m still needing to continually kill and reopen the connection.</div><div class=""><br class=""></div><div class="">The external needs a list in order to change values on multiple channels at once. I’m currently sending a list of 180 since that’s actually the full number of channels I’m using and lists of 512 entries were adding quite a bit more latency to PD.</div></div></div></div></blockquote></div><br class=""></div></body></html>