I was very slowly working through the method I linked to yesterday, and was starting to get confused because it only describes working within one plane. Will probably show you where I get to with it later today.
Yes, with the arrow composition I just hooked something up to the inputs quickly to see what came out. Any resources you can point me at for normals, tangents, and bitangents? I wish there were some examples to use the Parabox nodes which showed all of the potential they have.
Thanks Bodysoulspirit for the helper compositions. Now you mention it I made something a bit like this in Quartz Composer once to help with aligning hit-zone for buttons into a JS patch data store! I was up really late last night and I wasn't thinking laterally at all by then (not in Vuo, I was also trying things in AI, Kineme QCrystal, mimoLive rendering to ProRes4444, AE and PremPro), and as you can read I got increasingly trusted with the stock tools for adjusting port values. B/c I'm still pretty novice at using Vuo I haven't thought through all the helper tools we need to do graphic designer type work in Vuo, I had loads of such tools for QC after a few years of regular use. Maybe some of us could compile a set of these user made helper tools and Vuo could place on the site in a reserved place for Editor additions or something?
—> 2. I was originally building it in QC partly so I could use it in mimLive (formerly BonixTV) as a custom layer as well as generate some footage to overly in Premier Pro right now for a past event. mimoLive allows you to record input settings as Layer variants. (It will be neat if we can find a way to wrap Vuo comps in QC wrappers to use in mimoLive, via Syphon is the most obvious but hacky way). So I had each element as an adjustable colour so I could have different (editable) versions storage in mimoLive i.e. a colour version, and a few greyscale and a translucent white variation. When working with transference it depends on the footage the bug is over so it needs to be flexible on the job. I just continued with that approach, yes I could have used just the two images, but I was repeating my workflow from QC/mimoLive. And when Vuo can export Image generators for Motion and FCP X it will work for those two I guess I was thinking.
–> 1. Thanks for the Map Image node, I was looking at a couple of other nodes in Vuo's long list of image adjustment layer choices but couldn't get anything to work, I must have missed that one, I guess it's the most ideal one yet (and small on screen space too!).
Joining a composition where you can simply connect the magenta "Select Latest" Output to the
Position port of any layer to arrow-move it with custom increments (or add layer name for mouse drag). Disconnect cable to lock position.
When done, remove magenta nodes & turn composition into image generator mode for movie export.
PS : you can also group sub-elements together into combine layers and the whole group together in case you wanna move the whole block later.
1 - Regarding tint image for a simple dual tone png you can also use
Map Image Colors (see composition joined).
2 - Not sure I understand what you mean with "Color Wells" but since you mentioned "Published Colors" I guess you want to have control over the colors and change them over time ? Otherwise if not of course one would export only 1 image with all the elements from AI with the correct colors, and 1 extra image with the rotating propeller, and you'd have only 2 layers to place & 1 to rotate.
3 - "if it was possible to adjust the standard increment in preferences" would make a great feature request yes ! And a way to replace sliders (right click on port ?) with wheels too (I know what you mean giving a long arm for a more precise adjustment).
4 - If you want to manually place a layer either with mouse drags or custom arrow keys increments, copy & paste the magenta nodes from the joined "Move Layer" composition, connect them as shown, give your layers some name and adjust them (don't forget to change the corresponding layer name on the "Receive Mouse Drags on Layer" node (this will be easier in Vuo 2) & connect the "fire on start" or "allow first event" to the layers themselves as shown).
When all placed, remove all the magenta nodes and your layers are placed and if the composition is running when deleting, all the values will be saved & stored.
The UVs for your quad look correct. For your rotating arrow or other objects, where are you stuck in the procedure that you linked to?
By the way, for correct lighting and correct behavior with some 3D object filter nodes, you'll need to fix the normals, tangents, and bitangents into the Parabox
Make Mesh with Values node. Maybe you're already aware and just filled them in real quick for this experiment, but I just wanted to make sure you knew they should be different than positions.
I gave up on this because positioning each of the eight elements was taking about 5 minutes each and it did my head in. And if I find the last one doesn't have room I have to move them all over again one by one. It's just so frustrating, @teamVuo.
QC has dials for adjusting number inputs (which can be replaced with an Input Splitter with a set range if desired but not compelled to use). Vuo has decided to put range bars with a very small pixel range for adjusting these standard input values. As if nobody would ever care about any kind of precision.
Using the slider is impossible to get the accuracy I need. Using the up and down arrows are too big in the jumps. If there were some modifier keys for making the up and down arrows move in smaller and larger increments or if it was possible to adjust the standard increment in preferences there would be other ways to do this. As it is it's insanely problematic and not the first time I've thought so and given up using Vuo for a project. I'm forced to manually keep trying numbers (trial and error) and unlike the standard macOS interface default that "enter" updates the number with the typed input but keeps the highlight on that input it "Tabs" to the next one. So I have to enter a number and then tab forward then "shift" + "tab" back to enter another number, over and over and over again. It's a bit dispiriting for a designer trying to line up a few objects visually.
Most of my PNG file sizes are the same so I should be able to give them all the same position and they sit in place but that isn't working for me either, and in any case sometimes you need quick and precise manual adjustments in visual design without the frustration of typing in 30 values until you get the right one.
In QC you can grab the adjustment dial for an input and drag the cursor away from the dial half a screen length and then get very tiny increments per 10 pixels of movement of the cursor, like a wretch with a very long arm. THere's no way to do this in Vuo and this is not the first time I've given up using it for some UI frustration.
Vuo doesn't have an option to append to a file, only create a new file or overwrite an existing file (
Save Data node). Since you're nervous about overwriting, what you could do is save each table row to a separate file whose name is the timestamp, then after the event use
cat on the command line to combine the files.
I said a monospaced font but actually testing it with a non-monospaced font (ex AvenirNext) it still looks pretty good IMO.
Yeah, because of how you produced and positioned the layers.
Make Text Layer makes each letter's layer only as wide as the letter.
Arrange Layers in Row tightly packs the layers (unlike
Arrange Layers in Grid which evenly spaces them). So you get a linotype effect, no overlaps between letters, but depending on the font it might not look too out of place.
Sign up for the Vuo announcements mailing list to get news and join the community. We post about once per month.