The way bro@ms are implemented by blackbox, there is no registration process. All bro@ms (execpt the core bro@ms, which the core intercepts) are sent to all plugins which subscribe to recieve bro@ms, which AFIAK most do (including bbSocket). Plugins then compare each bro@m recieved to the bro@ms the plugin uses, and performs an action when it finds a match.

bbSockets passes each bro@m it recieves to the connected programs, which can then implement actions if they recieve a bro@m which they consider to be theirs.

To effectively respond to bro@ms in real time however, a program needs to continously read from the socket.

Testprog does this using non-blocking sockets and looping continously, calling the read function on each loop. This unfortunatly drives CPU usage to 100%

bbSocket does this (so that it can respond to connected programs) using asynchronous sockets, which causes windows to notify bbSocket when data has come in on the socket. bbSocket then uses read, because it knows data is present.

Python also allows the use of asynchronous sockets via the "asynccore" (or that might be "asyncore") module, which allows you to define callback functions.

The external program can also inject bro@ms into the core by sending @broamToSend across the socket(which cowmag is using to trigger bbBalloon), which is then passed into the core, and thus broadcast to all blackbox plugins.

I think this is what you you were asking about.

Well, it has been a while since I could play some more with this and I'm still kind busy ATM but, I had tried to setup some BBInterface buttons to send ficticious bro@ms and I couldn't get my python script to receive them. Also, keeping an eye on my toolbar - it didn't appear that the bro@ms were even being passed or recognized by Blackbox as no messages were displayed.

But I'll give it another shot when I get some time, maybe it was something wrong with my script - but, using the same script to receive bbBalloon bro@ms worked...

I've got bbPyInterWeatherExtravaganza working on the asyncore (actually using asynchat as it's more of a client library where asyncore seems more server orriented). nothing completed at this time but I can attest to the fact that BBSocket does send every bro@m issued to the plugins (and you can respond to them with all kinds of fun things.) Like sending @PluginShow on an @PluginHide (message name wrong but you get the idea)

I'm bad

So, if i add to my menu:

[exec] (Poke nose) {@RemoveBooger}

A program connected to bbSocket would receive that, and hopefully be able to virtually.. well.. you get the idea?

Cheers,
Christopher

yes

Nice

Working on a NanoPlayer plugin now to integrate with bbSocket. Considering that the blackbox interface renders the gradients from the current style, we could soon have a player that changes its look with the style

Hm. Doing some testing, and i'm not receiving any notification of style changes? Could this be implemented or am i just doing something wrong?

Cheers,
Chris

There isn't a specific notification for styles, but changing a style does generate a BB_RECONFIGURE message.

You could try and then request the current style whenever you recieve a BB_RECONFIGURE message by using That should allow you to change styles whenever Blackbox does. You might need to put a slight delay between recieving the BB_RECONFIGURE and requesting the style file (I'm not sure whether the message occurs just before or just after the actual change in style file).

The BB_RECONFIGURE message from bbSocket looks like this.

The above should work, but in case it doesn't I'll start looking around in the blackbox API to see if there is a specific notification for when the style changes.

If anybody knows about such a notification, could you please post it here?

BB_RECONFIGURE is sent after the style has been changed or the user has requested a reconfig. If you do a GetStyleFile it will give you the new style.

Implementation of an open sound control protocol -> bb python script using BBsocket.
Check http://opensoundcontrol.org too!

As it is only half finished, only sending broams to bb via osc works atm.

I'm still figuring out how to listen for broams and the call a send to osc function outside the infinite loop (this is my first python project ever)

Requirements: SimpleOSC : v0.2.3 for python and pd extended (for testing)

Attachments deleted as 0.0.2 is far superior.

tresni,
Is this a single threaded approach? I'm currently missing incoming data while it skips off elsewhere in the script.
Could you please post a simple example of a bro@m responder using asyncore?

I was also looking at twised but it seems like overkill for something that should be so trivial

I'll have to dig through my machine at home and see if I can find it. Been a while

Thanks muchness.

Pasted Source Code

That's the code I have. It works Beyond that, don't ask me

Thanks tresni that worked a treat,

I've also created the same thing using the twisted framework.


I was wrong!
It's far easier to see what's going on in the code.

For the benifit of other experimenters,
It did take me a while to figure out that @BBCore.* bro@ms aren't passed to plugins but that seems very logical



major edit: changed the protocol class to a lineReceiver with delimiter support