@mark in PD is implemented the ambisonic system for sound spatialization, but clearly it is not a priority. I am very glad for your fantastic work, best!

@skulpture Thanks a lot, Graham! Best regards.

yes you can. its easy and you can do it in a variety of waysstep one is to connect your midi controller and select it in the communications menu / midi setupstep two, add a "note on" watcher to your patch, and hit the button you would like to use. On the right side of the actor you see the values of the incoming midi note as you tap your button, change the values on the left side of the actor to these values and you now have a note on watcher that only listens to this button on your controller.repeat for any other buttons, and use the "control watcher" for sliders and knobs.if you want to use two buttons for on and off, connect them to a "trigger value" actor and trigger 100 to turn on and a 0 to turn off your projectors volume. if you want to use only one button to toggle, use the "sequential trigger".

@kurious said: I would like to use the Lanbox Channels Actor, which communicates over UDP  Actually, your post provides an opportunity to test my LanBox LCX with the current Isadora version so here goes- I am running a test using LanBox with Isadora on MacOSX (currently 10.14.6 Mojave). Just to note that the LCEdit software that comes with the LanBox is likely to be 32bit and will no longer operate on MacOS after Mojave! Hardwire:MacBook Pro (2015)LanBox LCXNetgear wired/wireless routerEthernet network patch cableUSB cable DMX cableSlimPar RGBA (to test dmx connection) Software:MacOSX Mojave 10.14.6LCEdit 3.5.4Isadora 3.0.7  Hardware configuration:Starting with the LanBox LCX, I have connected a Cat5 patch cable between the LanBox tcp/ip I/O port and a network port on the Netgear router. I have also connected a USB cable between the LanBox and the MacBook Pro so that I can access the LanBox configuration through LCEdit software. The MacBook Pro is connected to the Netgear router using Wifi. I have a dmx cable between the LanBox and a RGBA parcan light instrument to test the functionality of the setup. Getting the LanBox to function over tcp/ip:step 1, you will need to access the settings of the LanBox through the LCEdit software. Make sure everything is connected and then launch LCEdit. From the File menu/ New Project... Configure the interface to use the USB connection for the moment so that the tcp/ip settings can be accessed in LCEdit. You can determine that you have a successful connection by checking the Fixture interface window of LCEdit. If the little square is green the connection between the LCEdit software and the LanBox is functioning. The tcp/ip settings are in the tools/ Global Settings... dialog. The LanBox tcp/ip have default settings. It is here that you need to make the settings compatible with your system. Possibly the easiest way to make the settings work is to use the Network System Preferences in MacOSX to compare the ip address numbers and make changes accordingly. In this example the default LanBox Gateway ip address is set to '192.168.0.1', but I can see that my system router setting is '192.168.1.1' - so they do not match and I will not get a connection with these LanBox defaults - I need to change them... In LCEdit I change the Gateway IP setting to match the router ip of my system. In LCEdit I will also need to change the IP address setting of the LanBox to be compatible with my system. With those two changes to the default LanBox ip settings in LCEdit we can now test the tcp/ip connection between the LCEdit software and the LanBox. In LCEdit, Window/ Reconnect Interfaces... Finally, in the Configure Interfaces dialog, enter the correct ip address for the LanBox in the TCP/IP tab. If all is going well, you will be asked for the password (the default is: 777) Check that the connection is active by looking for the little green square in the Fixture interface of LCEdit. If the LanBox and LCEdit are not connecting, then it is unlikely that Isadora software will connect. You can reset the LanBox to its defaults and try again, by accessing Tools/ Erase LanBox... If you have data on your LanBox you can save it to an external file, Tools/ Save LanBox Data. Step 2, The Isadora actor 'LanBox Channels' requires the same settings as indicated for the LanBox that match your system. If you have dmx equipment around (I am using a single 4 channel RGBA parcan) then you should be able to get a response using the configured dmx channels of the 'LanBox Channels' module. Next thing is to construct an Isadora system that will function with the dmx equipment that you have. Attached here is a simple User Actor module (Isadora 3) that allows you to change and store levels for 96 dmx channels with a 2 second envelop. It is a few years old and the envelop generators don't function like this anymore, but it will give you an idea of what you might need to do. 1-96 LanBox.iua3 Step 3, When you have everything working, some of the setup is now redundant. If you want to save the setup in your LanBox save the settings using LCEdit. Once that is done LCEdit is no longer needed as the LanBox interface is directly with your Isadora patch. LCEdit can be closed and quit. The USB interface is now no longer required and the cable can be disconnected. Best Wishes Russell

@woland ah ok... I dindt know or remember.thanks a LotBest,

Thanks to everyone for those several propositions. As it is often the case, because of lack of time, the Director didn't keep this path. the Premiere is tomorrow...I'll take time later to experiment for my own some solutions. Maybe this topic will be usefull for someone else.

@juriaandon't you find it very very critical to write in the promotion on the homepage that izzy 3 has an build in support for these types of camera, and no hint, no chance to realise that is it not ready now. its very difficult to see the point why it is not declared for new costumer. ?! that it is work in progress. thx.r.h

Hello, I'm trying to use LeapMotion Watcher and 3D particles to create an interactive projected installation. However, I need some very specific particle behaviors that are hard to nail.  The particles are supposed to look like stars, and participants are meant to use their hands to collect and "toss" stars into a sky-like environment.  The motion I'm envisioning is similar to this video from 0:58 onward:  (this was not made in Isadora, but it's a similar type of hand motion and particle behavior):  https://www.youtube.com/watch?v=2GNmNjME2vg I've been studying the documentation of 3D particles, but it's all very difficult to follow and/or the videos are too blurry to see.  I know it's not difficult to get particles to start emitting, but tracking the appropriate motions of gathering and tossing, as well as making the particles appear to react to this motion (especially tossing, and how that action would translate into the LeapMotion Watcher's parameters like "swipe", "roll," etc) is very hard for me to concieve of.  Does anyone have any suggestions to get me started in the right direction?  Thank you, and please let me know if this is unclear.

thanks a lot 

For this project, we want to create the impression that a person's hands are creating smoke trails using Leap Motion Watcher.  Is such a thing possible?  The idea is 2-fold:1) We have footage of fire output to the projector.  This fire "grows" with the hand count on Leap Motion Watcher (i.e. as more hands trigger the Leap sensor, the movie watcher is set to play video files of progressively larger fires.  2)On top of this, participants are supposed to be able to wave their hands and create the impression that they are swirling smoke around the fire.  I'm wondering how this can be achieved, or if this is best suited to a different software.  And apologies if the answer is obvious; I'm new to using Leap and Isadora combined.Thank you!

I agree with Fred and asked this before. In complex mapping situations I leave out (if possible) the projector out of a group for this reason.

Just came across this article on the development of the Kinect.  Pretty interesting deep dive into the little piece of hardware that we know has taken on a new life of it's own outside of gaming...

@michel Thank you  !!Best,

Ah, I'm being thick. It took me a bit to understand your use-case wherein sometimes User Actors might have different names (because of position/function) but that you'd still want them to be part of the same "group" and update together (or ones with matching names being part of different groups and not updating together). I can definitely see how what you're talking about doesn't currently exist and could be helpful. (To be transparent, even though I'd personally love it now that I understand what you're saying, it's a very power-user-centric feature request so it may end up lower on the list than other feature requests that would affect a larger percent of our userbase. Like I said, I love the idea though.)