Hi Claude,
LX Console v3.5.4 crash when active dmx in with Enttec Pro USB.
Stops working after an unspecified time.
Thanks
LX Console Crash
LX Console Crash
Un saludo,
Can you post or e-mail the crash log? Its highly likely that this is a threading issue and not something that can be reproduced by just leaving DMX input on until it fails. The crash log narrows down the possibilities because it will show exactly what went wrong to cause the crash.
Also helpful to know if you are using the D2XX driver and what version of OS X you are using.
Also helpful to know if you are using the D2XX driver and what version of OS X you are using.
Its not clear from the crash log that you sent exactly what happened to cause the application to hang. But there are two likely possibilities:
First, while importingDMX an error occurred that left a thread locked with no possibility of being unlocked. The next build will prevent this.
Second, a loop happened with importDMX and OSC out where the importedDMX caused a change in OSC output that caused a change in DMX in, and so on... This is less likely because DMX input is polled rather than a direct response. But, it could slow things down enough to make it appear that the application was frozen.
When DMX input is being monitored, especially if it uses the patch rather than being received as channels, it can slow down the interface response to a crawl. It could appear that the application was hung because clicking on a menu might take many seconds before you would actually see the menu appear. This is because the interface is trying to keep updating itself for the DMX information which comes in faster than it can process. This is especially true if it has to convert dimmers to channels. While this normally is quick enough you don't notice, it adds up when there are 40 updates per second which is maximum DMX speed.
First, while importingDMX an error occurred that left a thread locked with no possibility of being unlocked. The next build will prevent this.
Second, a loop happened with importDMX and OSC out where the importedDMX caused a change in OSC output that caused a change in DMX in, and so on... This is less likely because DMX input is polled rather than a direct response. But, it could slow things down enough to make it appear that the application was frozen.
When DMX input is being monitored, especially if it uses the patch rather than being received as channels, it can slow down the interface response to a crawl. It could appear that the application was hung because clicking on a menu might take many seconds before you would actually see the menu appear. This is because the interface is trying to keep updating itself for the DMX information which comes in faster than it can process. This is especially true if it has to convert dimmers to channels. While this normally is quick enough you don't notice, it adds up when there are 40 updates per second which is maximum DMX speed.