Bodysoulspirit's picture

And for the others questions, Generally, for most nodes you only need a Fire on start.
But for the nodes that must move or use time inputs you need time or screen refresh frequency of course.

I guess you probably wonder when yo use Fire On Start or Fire Periodically because right now when you LIVECODE the node does not reload itself when you change a parameter (as QC does because it has PULL and Vuo right now only PUSH). But that is changing it the next update and nodes will auto reload. If already you want to see changes automatically when you live code you'll have to relaunch the node after changes (cmd-click ont a port for example) or you use a Fire Periodically but be sure to disconnect it when you're done live coding because that will slow down your composition.
Fire Periodically is still useful if you want your text strings to change every minute for example ;)

Check the manual or some examples that's in there.

And if the string has a video url in it yes you can play it. Click on the Play Movie node in the node gallery below in the node info there are links to some compositions that use that node.

However I'm not sure if Vuo can already download and play videos from the web, images yes, videos the only time I tried it did not work but that really can be because of me doing it wrong.

Bodysoulspirit's picture

If even the image was stretched during the tube processing, I thought about adding the image later, with change shaders, but that will perhaps make the shader appear later. I thought it would have shaded the top and bottom as well but with a thickness of 0 it seems not (or it's invisible).

What I still wonder, there may be some info about about that that I have missed on the website but if I create a very detailed tube with > 100 lines and apply a live image to it, is it better to reshade the tube lower in the node pipeline with some Change All Shaders or can I apply it directly on the tube node and only the shader part of the node is being recreated (and not the whole tube).

Bodysoulspirit's picture

Yes but correct me if I'm wrong, if you render the layers at 3000*1000 and stretch that image to the tube it will have the correct proportions and ratio but would there not be a huge loss of quality ?

For example if I take an image that is 1000 px large, stretch export it to 300 px large (with same original height) and reload it and stretch it at 1000 again, quality drops very much.

So your question still stands, what is rendered in what order, but somehow even if the image shortly is stretched and applied to a 111 tube it perhaps still has access to the original image so that you loose some extra hardware work but at least your image would be at better quality ?

Don't know quite technical for me ;)

bLackburst's picture

Make Noise Image Range doesn't cover small resolutions

Status: 

Vuo version: 

Fixed in Vuo version: 

OS version: 

  • macOS 10.12

How severely does this bug affect you?: 

●●○○ — It's annoying but I can work around it.

Steps causing the bug to occur: 

  1. Create Make noise image node and move it with time, render to window.
  2. Change height to 1 pixel
  3. No amount of adjusting range parameter will give you full range at this resolution.

Other notes: 

I'm just trying to create colourful noise patterns 1-pixel high to send to artnet strings, but it changes the nature of the noise to a point that I can't get full range.

Also if you render this image to a window you will notice that the window doesn't display this line unless the window is resized.

Bodysoulspirit's picture

Not such a noob question in my opinion. I ran some tests but could not find yet a solution neither.

That will be way easier when that feature requests get implemented : Provide option to automatically wrap text images/layers

Bodysoulspirit's picture

;) No probably not. Try using Copy List Items with Interleave Lists and if that works just do the same 4x (connected for one corner). Splitting the 4 corners would allow you to set different colors for each corner f.e. !?

boomshokka's picture
boomshokka commented on boomshokka's Discussion, “connecting points with lines ?

Hey :) thanks for your reply man. This is almost what I was looking for. I got to the point where I can connect dots, but lets say you would like a line from the top right corner going to every body part, like a kind of laser effect. would i have to make line mesh nodes for every single line?

Bodysoulspirit's picture

Hey, I posted a comment but somehow it went to a wrong place, trying to link to it : Comment

Kewl's picture

Yes, you're right. But... For me it changes the strategy for the image rendering from layers.

Let's say I want a 1x3x1 tube scaling. A good image for that would be 3140x3000 pixels. But if the image is applied to the tube before the tube scaling, the image will be squeezed to 3140x1000 pixels (loss of data) and than re-stretched to 3140x3000 (extrapolation of data). I have waisted CPU cycles to render an image bigger than necessary and to squeeze that image.

If I know that the image is applied before the tube scaling, I can distort the layers (taking into account the tube scaling) before render to image and render the image at 3140x1000. Once applied and scaled on the tube, the image will have the good proportions, but I will have potentially saved a few CPU cycles by avoiding the generation of "useless" pixels that get lost on the image squeezing.

Or maybe not... Is Vuo vectorizing matrix data for processing?

Pages

Welcome!

Vuo is more than nodes and cables, it's a community! Feel free to browse or add your voice.

Browse Discussions

Start a Discussion


Browse Feature Requests

Suggest a Feature


Browse the Composition Gallery

Share a Composition


How can I get notifications?

Learn more about the community

Learn more about Vuo

Vuo Announcements

Sign up for the Vuo announcements mailing list to get news and join the community. We post about once per month.