|
|
ArtDMX 16bit mode problem Hi, i'm trying to patch a Martin Mac 700 Profile in 16 normal mode in QC, using the ArtDMX patch. MAC 700 in normal mode uses 8 bit data for all channels, except PAN and TILT, which uses 16 bit value, split into 2 consecutive channels. As explained in the patch help, i group 2 channels by naming for instance: "20,21", and sending a float to this index. However, QC crashes after a few seconds. Has anyone succesfully worked with ArtDMX 16bit mode ? For you experts, here's my patch: (output is un-connected, so that you can actually load the patch) any help truly welcome. Note: crashlog already sent via KnM core.
|
Which version of ArtNet are you using? There was an update yesterday (1.2) that might address this. It's not crashing for me (I just quit after running it for 3 minutes -- part was at 1000fps, part was at 20fps, part was at 50fps, to rule out any weird framerate dependence).
Please name your crashlogs (you, franz, usually do, but the latest one I have with your name on it is from the kineme3d project a week or two ago) -- we have over 1500 unresolved/unfiles ones in our database at the moment ;)
(holy cow, many are even for Snow Leopard -- whoever's got KinemeCore running stable in Snow Leopard, please contact me!)
i'm using 1.2b3 (installed during the artnet.framework thing). will try with new version. The bug is however spotted: it comes from KnM 16bit mode. If i use my own macro (attached) to manually separate MSB and LSB, it works without bug.
And no, KnM Core isn't working properly with SL, neither is GLtools (it voids all the transparency settings)
The range stuff is a bit weird, but I've not had it crash -- I'll take a closer look, but I need some sort of dependable crash, or a log, or something, to really focus on it :/
That's been my experience as well -- however, someone's posted several (>10?) 10.6 crashes, so someone has KCore working... shrugs (for me it works, but after a while QC stops launching)
Maybe if there are so many crashes reported, k-core isn't quite working in SL, and someone is just a hard head :)
By "working", I meant that it's living long enough to report crashes (mostly in ATI drivers, from the bunch I looked over) -- that's impressive to me because it typically fails as soon as QC loads it (before it has a chance to present the crash report dialog).