Bodysoulspirit's picture

@Bodysoulspirit

Bodysoulspirit's picture
Bodysoulspirit commented on howie's Discussion, “Turning off nodes

There is a feature request to turn off nodes.

Right now you can put another select in front of the chain, and leave one port empty, and add an Allow Changes node to prevent unessery events from entering the resize node.

See joined comp.

Bodysoulspirit's picture

Thanks mic, the workaround to use fire on start + fire periodically works.

So the problem does not seem to happen because the image is being loaded into the composition I guess.

Mmm, problem is for image protocols you should use "Allow Periodic Events" instead of "Fire Periodically" (for example for screensavers).

But solves my problem for now ;)

Tnx

Bodysoulspirit's picture

Periodic Check Image URL Events seen / frame drop

Status: 

Vuo version: 

OS version: 

  • macOS 10.13

How severely does this bug affect you?: 

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

Steps causing the bug to occur: 

Not sure this is a bug, or related to to my old hardware.

I want to check every 0,5 seconds if an image has changed, load it, and apply a rotation to the layer.
It has an Allow changes after the fetch image to update events down the node chains only if the image changed.

However, on the rotation animation, I'm seeing a frame drop every 0,5 seconds, from 60 to +/- 55 FPS.

Since I have an allow changes node that block events, I guess the choppy rotation is because of the frame drop from loading the image into the composition ?

Is it because of my hardware ? Or something else ?

Thanks

Have you found a workaround?: 

Nopynope. Since the image name stays the same even if the image updates, I don't know how to load the image into the composition only when changed.

Screenshots: 

Compositions: 

AttachmentSize
Package icon Periodic Check Image Events.zip3.84 KB
Bodysoulspirit's picture
Bodysoulspirit commented on Mechanica's Discussion, “Crashing Subcomposition

Okay, that makes sense. I just went ahead and upgraded to Pro and the beta, so hopefully I'll have better luck now.

Ah cool ;) In Vuo 2, sub-compositions don't need to be installed strictly in the Vuo Application Support library, they can for example be shared alongside a composition, like I did, in a modules folder next to the composition (you can still install those if you wanna use it across several compositions).

And in Vuo 1, the whole sub-composition was updated when any port was updated, in Vuo 2 not the case anymore, ports get updated individually.

Bodysoulspirit's picture
Bodysoulspirit commented on Mechanica's Discussion, “Crashing Subcomposition

Mechanica

Vuo is Mac only for now, Linux and Windows versions are still on the roadmap.

If you got errors for Render Scene and Draggable Camera it should mean you're using Vuo 1.2.8, sorry, my uploaded version was for Vuo 2 beta.

Although I get no crash using your composition both in Vuo 1.2.8 or Vuo 2, I couldn't get the shader to work in Vuo 1.2.8 by quick testing. Going to work now, will check it later again, but even when you set a shader on the parent node, and feed a shader into the sub-composition for one of the cube sides, for me the sub-composition still says "no shader".
In Vuo 2, how the events flow through sub-compositions have changed, and there it works.

I switched the true / false input selector though in the sub-composition, as I understand you wanted to display a wireframe shader if no other shader is provided ? (see screenshot, all sides except front has color shader, front has wireframe)

Will check later

Pages