Hi. Great tutorial. I am at 11:48 and when I copy/paste the light fixture it stops cooking. And all the ops inside also. I cannot populate the select1 with more than one set. Please help me.
Hello! Thanks for this tutorial! Wondering if you know of a way to take DMX input from Artnet (lots of data of pixels of lights via DMX) and turn that into a video signal per pixel? I may have to do it pixel by pixel with a square object for each perhaps... thanks again!
Two ways: 1. Use shuffleCHOP to make the single channels in to one channel with 512 samples. Then another shuffelCHOP to make them in to rgb and finaly a chopToTop. 2. Basicly same as above, then use instancing.
@@AlphaMoonbase thanks for much for the reply. Update -- I got my device to send OSC color value per pixel (64 pixels total) and I understand how to remap and rename the data, but now I'm just not sure how to display. As in, how I get that color value to effect a pixel of a video signal. One idea would be just to create a square and have that color value manipulated (not sure what CHOP that would be through) and then shrink that down so I have 64 squares. I looked into the "ChopTo" but it doesn't have an input it seems. Thanks for all your help! (happy to jump this to email if you are up for it). Cheers!
really cool especialy using a replicator on lightfixture, but though could you advice a way to: 1) populate the UI with 170 controls simultaneously, 2) create a another UI to place the fixtures on stage map and show their level with alpha 3) a way to create a scene manager that would transition between fixture preset, ( and btw the 512 devices is wrong with 3 chanels by fixtures, should put 510 as the top math limit ) great job thx, really handy
In general, I would say use a proper lighting software. MA or ETC Eos are the big ones, but you will have to shill out some money. Some free tier solutions are Obsidian Onyx, QLC+, Enttect EMU (if you have an enttec interface) and I think chamSys has some free parameters. There is software made for this and TD surely coul handle this to a certain degree, but simply is not the right tool for that if you do not want to invest the time yourself. But, some answers: 1) Use something like UberGUI by Lucas Morgan. Widgets will kill the TD performance. They are not optimozed enough. 2) Instancing. Sreight forward. 3) Check Tauceti PrresetManager. Shuld do th trick (eve though 170*3 Parameters might be a lot.) And your 512 comment (sure, but youc an still fll it up with ther fixtures that arenot 3 channel. Soooo.
Hey man, hope you're doing well! This video was very helpful, but I'm looking to expand on it. Your tutorial allowed me to get a standard RGB fixture to work, but I'm looking to control a secondary fixture that has more complex controls such as pan and tilt. I was able to assign those controls to the UI and they are working properly but I need to send a constant to another channel (ch. 7) in order to open the shutter and actually get this particular light to work. Do you know how I may be able to access other channels other than the ones you talked about in the video? I believe the solution is within the python expression used in the rename chop of the fixture container. Any help would be greatly appreciated. Thanks!
Oh, there are a thousand ways :) The best staring point is the opFindDAT in combination with a replicator. This way you can reactivly create new parameterCOMPs for all the fixtures. Check out the Widget Tutorial series on the TouchDesigner-Channel to get intel on how to manage Comps .
@@AlphaMoonbase Thanks a lot for your answer. I just started yesterday to discover TD, there a lot to learn, and a lot to do with ;) Thanks for the tips, I'm gonna have a look on this!
Im probably missing something, but I followed this, and at the controller level, if I change a parameter on one of my lights, the signal doesnt go out to the light until i double click on the dmx_out. then it updates whatever parameter I changed
Hi! Thank you so much for the Tutorial great workflow. I do have an issue with this expression: op(op('null2')[1,1]), gives me a yellow "flag" and tells me invalid path for node xxx referenced by parameter Operator. So i am not able to see the controls in UI container... if anyone could point me to the right direction. Thanks in advanced
Man, this has been awesome and am subscribing but how are you gonna say this is a Simple DMX controller but get into Python like that at the 8 minute mark?
Not simple in any stretch of the human imagination. Why don't you make 1 light work (on Ch 1), and then show us how to extend the capability to address footprint?
![[TouchDesigner - Tutorial] Auto UI](http://i.ytimg.com/vi/B0lEnVglMkk/mqdefault.jpg)
![[TouchDesigner - Tutorial] Auto UI](/img/tr.png)
I'm learning touch designer now, and this was the video that finally flipped the switch in my mind on how to work with it. Thank you very much.
helpful, thank you, :)
though I will say, the touch designer community and I need to have a little semantic debate on what this word "SIMPLE" means.
Lets settle on the functionality it offers as simple. Maybe not the way to get there :)
Hi. Thank you. This was a very enjoyable and simple tutorial. Much appreciated.
Great. Thanks Wieland! My networks looks sooooo messy haha, with this one this will get a looooot more cleaner.
Hi. Great tutorial. I am at 11:48 and when I copy/paste the light fixture it stops cooking. And all the ops inside also. I cannot populate the select1 with more than one set. Please help me.
Ah. The parent of the parent stopped cooking for some strange reason. And now it works again. Let's see where this leads to...
Hello! Thanks for this tutorial! Wondering if you know of a way to take DMX input from Artnet (lots of data of pixels of lights via DMX) and turn that into a video signal per pixel? I may have to do it pixel by pixel with a square object for each perhaps... thanks again!
Two ways:
1. Use shuffleCHOP to make the single channels in to one channel with 512 samples. Then another shuffelCHOP to make them in to rgb and finaly a chopToTop.
2. Basicly same as above, then use instancing.
Thanks!!!@@AlphaMoonbase
@@AlphaMoonbase thanks for much for the reply. Update -- I got my device to send OSC color value per pixel (64 pixels total) and I understand how to remap and rename the data, but now I'm just not sure how to display. As in, how I get that color value to effect a pixel of a video signal. One idea would be just to create a square and have that color value manipulated (not sure what CHOP that would be through) and then shrink that down so I have 64 squares. I looked into the "ChopTo" but it doesn't have an input it seems. Thanks for all your help! (happy to jump this to email if you are up for it). Cheers!
really cool especialy using a replicator on lightfixture, but though could you advice a way to:
1) populate the UI with 170 controls simultaneously,
2) create a another UI to place the fixtures on stage map and show their level with alpha
3) a way to create a scene manager that would transition between fixture preset,
( and btw the 512 devices is wrong with 3 chanels by fixtures, should put 510 as the top math limit )
great job thx, really handy
In general, I would say use a proper lighting software. MA or ETC Eos are the big ones, but you will have to shill out some money.
Some free tier solutions are Obsidian Onyx, QLC+, Enttect EMU (if you have an enttec interface) and I think chamSys has some free parameters.
There is software made for this and TD surely coul handle this to a certain degree, but simply is not the right tool for that if you do not want to invest the time yourself.
But, some answers:
1) Use something like UberGUI by Lucas Morgan. Widgets will kill the TD performance. They are not optimozed enough.
2) Instancing. Sreight forward.
3) Check Tauceti PrresetManager. Shuld do th trick (eve though 170*3 Parameters might be a lot.)
And your 512 comment (sure, but youc an still fll it up with ther fixtures that arenot 3 channel. Soooo.
Hey man, hope you're doing well! This video was very helpful, but I'm looking to expand on it. Your tutorial allowed me to get a standard RGB fixture to work, but I'm looking to control a secondary fixture that has more complex controls such as pan and tilt. I was able to assign those controls to the UI and they are working properly but I need to send a constant to another channel (ch. 7) in order to open the shutter and actually get this particular light to work. Do you know how I may be able to access other channels other than the ones you talked about in the video? I believe the solution is within the python expression used in the rename chop of the fixture container. Any help would be greatly appreciated. Thanks!
You need to customize the light fixtures within the console to have more than 3 channels and then you would set [1,7] for instance.
Great tutorial, thanks a lot! Is there any way to have all the fixtures listed in the IU instead accessing them one by one through a drop down menu?
Oh, there are a thousand ways :) The best staring point is the opFindDAT in combination with a replicator. This way you can reactivly create new parameterCOMPs for all the fixtures. Check out the Widget Tutorial series on the TouchDesigner-Channel to get intel on how to manage Comps .
@@AlphaMoonbase Thanks a lot for your answer. I just started yesterday to discover TD, there a lot to learn, and a lot to do with ;)
Thanks for the tips, I'm gonna have a look on this!
great
Im probably missing something, but I followed this, and at the controller level, if I change a parameter on one of my lights, the signal doesnt go out to the light until i double click on the dmx_out. then it updates whatever parameter I changed
Hi! Thank you so much for the Tutorial great workflow. I do have an issue with this expression: op(op('null2')[1,1]), gives me a yellow "flag" and tells me invalid path for node xxx referenced by parameter Operator. So i am not able to see the controls in UI container... if anyone could point me to the right direction. Thanks in advanced
did you fix this? I have the same problem.
Man, this has been awesome and am subscribing but how are you gonna say this is a Simple DMX controller but get into Python like that at the 8 minute mark?
A, its a tiny snippet (check out my rubberduck streams, thats python hell ;D ). Without a little bit of Python you will get stranded quick in TD land.
Not simple in any stretch of the human imagination. Why don't you make 1 light work (on Ch 1), and then show us how to extend the capability to address footprint?