Hello @id_mora -
Have you tried copying the supplied vidvox touch file, with working output, saving as a new name, and integrating your TD constructions inside that?
That should work…
I’m still learning TD atm, and did the above, as a brief test / ‘proof of concept’ to see if i could get a TD edit exposing parameters for playing inside VDMX…
That worked for me, but now I’m back to working my way through learning more TD before trying to build anything else for vdmx…
Re: your problem tho -
Open up the vidvox image input example,
Click on the comp - you’ll see in the comp’s parameter window that the rendersize width + height references data from the ‘par1’ CHOP.
You can add those scripts, or click the + of par1, to make the data sliders available for dragging and dropping onto the resolution width+height
Maybe I am not explaining myself well. Iterating with a known factor of times is indeed doable and simple. What I would like to achieve is having control on how many iterations are there, while the compostion is running. So that you could change the number of iterations with a slider. You could maybe do like 5-100 nodes and switch them on and off, but that is not the itertive way of doing it. The solution would be to have a node that can copy an operation several time, while changing some parameters. In the trails example you would have only one of the selectframe nodes, which would then in turn be repeated and modified by another node. Quartz Composer had pretty simple iteration and Vuo has decent iterative options. IDK about TD, though.
The second video with the NOTO the talking ball is indeed super cute! And great resource. I think I am starting to understand where the issues with the feedback and video lies. And I believe the problem is with the framerate of the specific video. I was searching for a way to change that inside a compostion, but the only frame changes I have found is the same as in this tutorial. Basically changeing the FPS of the compostion instead of manupulating the framerate of the video.
Okay, I know what you’re getting at. It’s very simple. There are two editing modes in TD: viewer mode and active mode.
If you look closely, each operator has a + symbol at the bottom right. This activates active editing mode. This allows you to link with links (not cables). The keyboard shortcut is “a.” You’ll see the operator change appearance. Depending on the operator’s family type, it has one function or another.
In the case of chops (green operators), it’s used to select a specific value. When you hover the mouse over a value, it shows an arrow and highlights the value in green. Now it’s a matter of selecting that value and dragging it to the value you want to link. This way, a link line will appear, if everything is correct.
This tutorial I made years ago explains the topic quite well.
Hi,
I was able to make it all work, I get my TD comps in vdmx now. But I have a little problem with the published parameters. For example here: in TD I set Noise min. to 1 and max. to 7 with the default of 2.
But then once imported into vdmx it only reads from 0 to 1. I am not able to get the 1 to 7 parameters there published. Am I missing some step in TD maybe? Thanks for any help!
I’m guessing something is off because the TDIO_Float_Input example that comes bundled with VDMX6 has a float value of 2. Here’s a modified version of that that goes to 7 TDIO_Float_Input_val7.tox.zip (12.1 KB)
thanks! But does this work for you in vdmx up to 7? I just import that comp into mine and again only get the float 0-1 like before. Otherwise in TD it seems identical to my Customize component panel.
Ok, thanks. I think I will have to update my TD then.
A question…the comps go to TouchDesignerFX or TouchDesignerSource, does it matter? Or it depends on what kind of a comp it is? Like for example in Vuo…Image Filter, Image Generator?
Thanks
You can solve this in any red TD standardizing data from the input / valid with a Math operator:
and the Math/Range/ operator. From Rage 0 -1. To range 0 - 7. o el valor que desees
This is a usual practice for example when we control the DMX lights, convert the values from 0-1 to 0 255. for example.
Hola Juanjo, gracias. Lo he probado de mil maneras pero no lo consigo. Es conectar el nodo de math y publicar los valores del Math? Y como por ejemplo conecto el Math a un nodo azul SOP si quisiera publicar algun valor del SOP?
Gracias!
