Crash problem with ArtDmx Receiver

Hi, I am Italian excuse for my English... I have problem with ArtDmx Receiver (ArtNet Sender works correctly). With test file SendReceive.qtz when stop and run again Viewer, Quartz Composer show an error and exit.. In attach the report file. I have try with another Imac but same problem remains. If I don't stop and run the viewer, ArtDmx Receiver receive just one time and then it doesn't refresh the structure. I have regulary purchased the Art-net tools but work just on sender. I use Mac Os X 10.6.4 and the last Quartz Composer. Thanks for your help

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

ugasparon's picture
Re: Crash problem with ArtDmx Receiver

Here the report

PreviewAttachmentSize
QuartzComposerProblem.rtf51.29 KB

bmellen's picture
Re: Crash problem with ArtDmx Receiver

Yeah, I'm able to reproduce this crash too; looks like I introduced a bug with the latest version. Thank you for reporting this, I'll try to get it fixed today. Sorry for the inconvenience.

ugasparon's picture
Re: Crash problem with ArtDmx Receiver

Thanks, the first problem seems to be resolved, but remains the second problem: the ArtDmx Receiver receive just one time, when push RUN button on Quartz Viewer. here the video http://www.youtube.com/watch?v=eSAopnJJ4pg

Thanks for your help

ugasparon's picture
Re: Crash problem with ArtDmx Receiver

With new today version all work perfect! I have try also with many universe in simultaneously (from one PC to the other) excellent work!!! Thank you very much

gtoledo3's picture
Re: Crash problem with ArtDmx Receiver

You may want to go backwards in updates, before whichever one announced multiple universes.

Also, you may want to make sure you're transmitting on art-net spec ip range, because it makes a difference with some devices.

bmellen's picture
Re: Crash problem with ArtDmx Receiver

I just released version 1.4 which fixes both problems mentioned above. Sorry for any inconvenience this may have caused anyone. (The receiver refresh problem is really embarassing on my part; worse yet, I specifically remember catching and fixing it, but I must have accidentally reverted the fix right before building the 1.3 release.)