Yeah - my uDMX device locks up and needs a close/open with all the externals that I can get running. 

I see the same behavior with the midi2udmx compiled max application they provide as well.

Maybe it’s a fundamental problem with the unit - or with my hardware…

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 :/

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.

On Jun 13, 2016, at 12:36 PM, Lucas Cordiviola <lucarda27@hotmail.com> wrote:

Ok,

I think that the PD part is Ok with the patch I gave you, at least to continue the tests.

In the manufacturer site there are more than 4 “externals”, Have you check them all?

You will have to restart Pd to switch between them.




Mensaje telepatico asistido por maquinas.

Subject: Re: [PD] uDMX hanging/locking up
From: jmejia@anestheticaudio.com
Date: Mon, 13 Jun 2016 11:47:17 -0700
CC: pd-list@lists.iem.at
To: lucarda27@hotmail.com

This is a much simpler table/array solution - thanks for that!

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.

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.