trouble with sub-compositions . . .

Status: 

Vuo version: 

Fixed in Vuo version: 

OS version: 

  • macOS 10.13

How severely does this bug affect you?: 

●●●○ — It prevents me from completing a specific task with Vuo.

Steps causing the bug to occur: 

  1. create sub-composition
  2. save it to the user folder
  3. composition runs perfectly
  4. export app, it won't run properly (extremely slow)
  5. then VUO will no longer open without a restart of laptop

Have you found a workaround?: 

No, well, except to reboot.

Other notes: 

The crash log I have included is just one of many as I'm trying to find a work-around. Perhaps I am building my sub-compositions incorrectly, but I have found V2.0 to be be very unstable in regards to sub-compositions and nodes in the user library.

Thank you in advance for any help/advice you can offer.

Compositions: 

AttachmentSize
Package icon Lighting Visualizer.zip12.2 MB

Crash reports: 

AttachmentSize
Plain text icon Crash Log.txt131.72 KB

reproducible crash in VuoCompiler() with 2.0.0.10830

mrray's picture

Submitted by on

Status: 

Vuo version: 

Fixed in Vuo version: 

OS version: 

  • macOS 10.13

How severely does this bug affect you?: 

●●●○ — It prevents me from completing a specific task with Vuo.

Steps causing the bug to occur: 

  • sample project included, build & run
  • alternate between clicking "Load 1st comp" and "Load 2nd comp" buttons until the app crashes.
  • crash is 100% reproducible on every machine we've tested so far.
  • crash almost always occurs within the first cycle or two (usually on 2nd click).
  • crash doesn't occur with the 2.0 alpha (2.0.0.10623)- only reproducible using the 2.0 public beta (2.0.0.10830).

  • stack usually looks something like this:

  • 0 0x00007fff58242b66 in __pthread_kill ()
  • #1 0x00000001053c10f0 in pthread_kill ()
  • #2 0x00007fff5819e1ae in abort ()
  • #3 0x00007fff582ade3d in nanozone_error ()
  • #4 0x00007fff582a1dde in _nano_malloc_check_clear ()
  • #5 0x00007fff582a1c23 in nano_malloc ()
  • #6 0x00007fff5829b241 in malloc_zone_malloc ()
  • #7 0x00007fff5829a5bf in malloc ()
  • #8 0x00007fff56099628 in operator new(unsigned long) ()
  • #9 0x00007fff5607ffc9 in std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator >::__init(char const*, unsigned long, unsigned long) ()
  • #10 0x000000010040b969 in std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator > std::__1::operator+<char, std::__1::char_traits, std::__1::allocator >(std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator > const&, char const*) ()
  • #11 0x00000001003ab4cf in VuoCompiler::VuoCompiler(std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator > const&) ()
  • #12 0x0000000100001877 in ::-[VuoHolder compileAndLoadComp:](NSString *) at /Users/testadmin/Documents/VuoQuestions6/VuoHolder.mm:50
  • #13 0x000000010000fb57 in ::__37-[AppDelegate loadSecondCompClicked:]_block_invoke() at /Users/testadmin/Documents/VuoQuestions6/VuoQuestions6/AppDelegate.mm:63

Have you found a workaround?: 

nope, sorry!

⌘⇧O doesn't work before opening "File" menu (when welcome screen enabled)

Status: 

Vuo version: 

OS version: 

  • macOS 10.13

Steps causing the bug to occur: 

  1. launch Vuo Editor (with welcome screen enabled) 1b. close welcome window, or leave it open, doesn't change behaviour
  2. press ⌘⇧O (cmd+shift+O) to open most recent composition
  3. be disappointed, nothing happens

Have you found a workaround?: 

  1. open File menu, then close it again (without selecting any option)
  2. press ⌘⇧O again: success! the composition opens.

- OR - disable welcome window. When Vuo opens with an empty composition, the shortcut also works.

Other notes: 

It's pretty obvious that the keyboard shortcut is registered only after the File menu has been opened OR a composition is loaded... not a major bug, but a little annoyance. Maybe a quick fix. Another idea: I do like the XCode welcome screen, where you are presented with a list of recently opened projects. Makes it fast and easy to get going. I would love to see that in Vuo!

Cannot correctly filter HID controls (button names)

Status: 

Vuo version: 

Fixed in Vuo version: 

OS version: 

  • macOS 10.13

How severely does this bug affect you?: 

●●●○ — It prevents me from completing a specific task with Vuo.

Steps causing the bug to occur: 

  1. Have an HID controller with buttons
  2. load vuo.hid.scale.control or vuo.hid.filter.control into a composition
  3. try, for example, accessing "Button 1" and "Button 10" and "Button 11" independently
  4. fail, because "Button 1" is part of the control's name for buttons 1, 10-19, 100-199, 1000-1999 etc.

Have you found a workaround?: 

No.

Other notes: 

This bug prevents from using an HID controller with more than 9 buttons, which is a shame, because I just built one with approx. 32.

Stochastic Camera Blur

Stochastic Camera Blur

Each frame, this composition renders the scene many times, moving the camera's location slightly each time, then blends all those images together to produce the output image.

This is one way to simulate camera blur / lens blur / depth of field.

Composition and supporting files: 

Package icon Stochastic Camera Blur.zip

Pages

Subscribe to RSS - macOS 10.13