boblight gets an OLA client

[ola-importer]

From dmx...@gmail.com on July 31, 2010 23:22:58

http://code.google.com/p/boblight/issues/detail?id=9&q=label%3AType-Defect

Original issue: http://code.google.com/p/open-lighting/issues/detail?id=98

[ola-importer]

From nomis52 on August 01, 2010 14:39:11

Is there anything you need from me for this?

[ola-importer]

From dmx...@gmail.com on August 01, 2010 22:47:05

yeah sorry, i keep getting this:

StreamRpcChannel.cpp:230: RPC Socket closed, not sending messages StreamRpcChannel.cpp:230: RPC Socket closed, not sending messages StreamRpcChannel.cpp:230: RPC Socket closed, not sending messages StreamRpcChannel.cpp:230: RPC Socket closed, not sending messages ....

after a while, for no particular reason. boblightd sets up a simple client on localhost and sends a DmxBuffer with senddmx to ola (as your example showed how to do it). ola_dmxmonitor shows its working with the spinning -/- and changing levels, but when the failure occurs it says Data Lost!

olad logging does not not seem to offer explanation and continues to run, so it's like the client looses touch with olad. Could this have anything to do with the rate at which the client sends updates to olad?

Cheers, Hip

[ola-importer]

From nomis52 on August 01, 2010 23:00:04

Yeah, this is the client sending too fast which causes the client or server to close the network socket.

From http://opendmx.net/index.php/OLA_Client_API :

"Also take note of the call to usleep(). Without this you're likely to fill the network socket buffer at which point the client code will detect an error and close the socket (you may need to increase the number of loop iterations to trigger this)."

[ola-importer]

From dmx...@gmail.com on August 02, 2010 01:58:48

Cheers mate, boblightd has an option called interval which controls this, I had it set to 20000, which seems the boblight norm for a claimed 50fps. But your example has 20000 too. Anyway i've jacked it up to 25000 and i'll see how that rolls.

boblight is cool, i've got xbox_media_centre -> boblight-X11 client -> boblightd -> olad -> dmxusbpro -> led pinspot behind the tv, and it's a happening thing :)

the cool thing is, boblight was only intended for a couple of leds via a couple of serial devices, but with OLA it could be used for serious, multi universe, pixel mapping operations in a live environment. It uses very little CPU and can work with v4l devices as well!

[ola-importer]

From nomis52 on August 02, 2010 11:23:09

I'm closing this. By the way the mailing list is a more appropriate place for discussions like these (and more people follow it than the bug tracker).

Status: Invalid