pbourke's picture

Reinstalled Vuo 2.0.1, no change.

pbourke's picture

Can't play any composition after upgrading to 2.0.1

Status: 

Vuo version: 

OS version: 

  • macOS 10.14

How severely does this bug affect you?: 

●●●● — It prevents me from using Vuo at all.

Steps causing the bug to occur: 

  1. Create a simple composition, see attached.
  2. Hit play button from the editor.
  3. Get a spinning beach ball for a second or two, then nothing.

Have you found a workaround?: 

Not yet.

Other notes: 

Strange, upgraded from 2.0.0 to 2.0.1 yesterday. All working, or so it seemed. this morning no composition can be played from editor. Even the simple one attached created from scratch. I have removed modules directory from the user library application support .... there are no Vuo crash logs from today. Rebooted, no change. Is 2.0.0 still available somewhere?

Screenshots: 

pbourke's picture

For my current use case I have realtime graphics being created by Vuo on a secondary screen that is projected, this is what the audience sees. I wanted the operator (teacher) to be able to feed text questions into the realtime graphics.

pbourke's picture
Paul commented on Paul's Bug Report, “fisheye camera node limitations

I accept there is a performance hit with this approach.

Isn't the equirectangular solution already also going to be a 6 camera pass? Or a different method?

With regard to the vertex shader used in the current fisheye node, it unfortunately does not give the correct results, unless it internally tessellates the geometry into very small triangle sections. By "prewarping all the vertices" it assumes that a straight line between two vertices is a straight line in the projection ... true for a planar projection plane but not true for a fisheye projection. So a triangle that occupies a reasonable amount of the FOV the resulting fisheye is incorrect.

Bodysoulspirit's picture
Bodysoulspirit posted a new Composition, “Triangles Tunnel
useful design's picture
Alastair commented on Bodysoulspirit's Feature Request, “Export as OSX Screensavers

Thanks Bodysoulspirit! I didn't realise @TeamVuo were looking to create a solution for automated code signing.

Bodysoulspirit's picture
Bodysoulspirit commented on Bodysoulspirit's Feature Request, “Export as OSX Screensavers

Alastair although I have not searched much on the subject, some things that pop to my mind are :

• The Code sign and notarize exported apps feature request.
• Jaymie's answer on the Apps notarized by Apple topic.
• Apple's page Notarizing macOS before distribution.
• Tutorial 1 : CodeSign & Notarization

Like Jaymie said I guess, they don't know exactly how this will be implemented in Vuo yet, how much manual work we'll have to do ourselves, and what we will need to install. So cross fingers for the easiest most automated way within Vuo (with manual override possibilities I guess is always good).

jmcc's picture
Jean Marie commented on Paul's Bug Report, “fisheye camera node limitations

Paul,

Based on the underlying code, our node is limited to 180 degrees. The current hemispherical fisheye projection code is based on "Realtime Dome Imaging and Interaction" by Bailey/Clothier/Gebbie 2006. If you can point us to a technique that satisfies your criteria (and also produces the same result for FOV < 180), we’d certainly look at incorporating it. The Vignette Width/Sharpness ports can let you clip to a unit circle by setting both to 1. We’ll take a look at making that clearer in the documentation.

As to the more general fisheye, your composition renders a scene 6 times using perspective cameras, then feeds them to an image filter shader to combine them into a circular fisheye image, then renders them to a window. That's less efficient since it's performing 8 render passes. We think the already proposed FR, Render scenes to equirectangular panoramas and cube maps could be expanded to include circular fisheye. Would that be an acceptable solution?

jmcc's picture

Paul,

We are interested in knowing how you would use a text input UI node. As a workaround, perhaps a TouchOSC implementation might work (as in Simple TouchOSC Typewriter). Once we know what you need, we could give you an estimate on commissioning it.

jstrecker's picture

Indeed, Console logs would be helpful. I wonder if it's the same problem as this one. Sorry for the trouble, DetAndreTeatret.

In addition to the suggestions on that bug report, one other thing to try:

  • Quit Vuo.
  • In Finder, go to the Go menu, hold down Option, and select Library.
  • Navigate to Library > Caches.
  • Find the org.vuo folder and throw it in the Trash.
  • Launch Vuo.

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.