Status: 

Vuo version: 

Fixed in Vuo version: 

Steps causing the bug to occur: 

.

Other notes: 

Hello all,

it seems to work fine on my macbook pro, but when I use on my desktop (gtx 970 or intel 4600) I do not get an image from this node. (scene to window works fine).

curious if anyone else has had an issue like this, or perhaps let me know i'm not crazy .

composition attached.

thanks

Sean

Compositions: 

AttachmentSize
Package icon test.zip95.98 KB

Comments

There's a bug report that I

jstrecker's picture
Submitted by

There's a bug report that I suspect is related: Different behavior between cmd-f and the built OSX fullscreen function. Both there and here, there's an intermittent rendering problem (that shows up often on some computers and not on others) when making windows fullscreen. Testing your composition on some Team Vuo computers — it works reliably on mine but shows the blank screen about half the time on my co-worker's. If the windows are made fullscreen on different displays, the problem still happens, though less often. If the windows are not made fullscreen, the problem doesn't happen.

Hi thanks.

seanradio's picture
Submitted by

Hi thanks.

Strange, it seems to happen to me whether I'm fullscreen or not, on either the intel gpu or the nvidia

(test2 attached) I converted my project to layers instead of objects to get thru (although I like scaling versatility with objects better) thanks for the info regardless.

My understanding is that,

jstrecker's picture
Submitted by

My understanding is that, even in systems with multiple GPUs (like some MacBook Pros, and some Mac Pros), the system only uses 1 GPU to render the user interface.

  • In the case of MacBook Pros, only 1 GPU is ever active (they're mutually exclusive).
  • In the case of the Mac Pro, the secondary GPU is only used for behind-the-scenes execution (OpenCL computation, or maybe OpenGL offline rendering), not for rendering directly visible content. https://discussions.apple.com/message/26416748#26416748 . Vuo currently only uses the display GPU (not the secondary GPU).

So which display Vuo Editor or the composition's window(s) are on doesn't affect which GPU it uses.

@seanradio, maybe (part of)

jstrecker's picture
Submitted by

seanradio, maybe (part of) the problem is specific your hardware. You mentioned that you have an NVIDIA GTX 970 and an Intel 4600. I'm wondering especially about the GTX 970 since that doesn't come with any Apple-provided Macs, and I don't know that Vuo has been tested on it before.

Could you provide your system specs (Apple > About this Mac > System Report > Show Less Information > Save)?

Would you mind checking some log messages that will tell us for sure what GPU driver Vuo is using (and if that makes any difference in whether the bug shows up)?

  • In Terminal.app, paste in this text and hit return: defaults write org.vuo.Editor debug -boolean true
  • (Re)start Vuo Editor.
  • Run the composition.
  • In Console.app, find the log messages containing "VuoGlContext_getRenderer" and let us know what they say.
  • In Terminal.app, paste in this text and hit return: defaults delete org.vuo.Editor debug

Hi thanks,

seanradio's picture
Submitted by

Hi thanks,

I attached the requested info, it seems to be rendering on the intel graphics only, regardless of which GPU the editor or composition window is on.
it's a Hackintosh BTW,
i7 4790K 4 SSDs GTX970 GTX560ti Gigabyte z97x UD7-TH 16gig DDR3 Ram I ran the reports/tests as both Mac Pro 3.1 and iMac 14.2 sysdefs just to double check.

i recently learned as i use Resolume Arena a lot on this machine for work, that regardless of which GPU the output(s) is on, whichever GPU the Resolume editor window is on, actually does the rendering.. so that's what led me to ask if the same was for Vuo.

I do have My GTX 970 as my main finder desktop output in my screen arrangement also,. with "displays have separate spaces" unchecked in Mission control, altough I've tried it "checked" as well.

I guess the only other thing I could try is to turn off all my overclock settings, but i have noticed in Cinebench/GLview/Geekbench it does increase my GPU Fps and render speeds.

thanks again for all the good work.

just to double check, i did

seanradio's picture
Submitted by

just to double check, i did some more testing,

i turned off the Nvidia drivers and rebooted as to only use the Apple ones( which means I can't use the GTX970, but can use the GTX560ti), it renders the "scene to image" on both the intel 4600 and 560ti displays. although the Console report still says its rendering on the intel iris pro GL engine for both display scenarios.

happy to do any more testing if it will help out. would love to render on my discrete GPUs if possible in the future.

thanks again!

sean

last one,

seanradio's picture
Submitted by

last one,

decided to do something a little bit more GPU intensive outputting on the 560ti.

unless i'm mistaken, it's rendering on the nvidia 560 according to the istat menu GPU monitor , even though the console.app is still saying "intel iris" etc.

I'm going to assume it's something with Vuo and the Nvidia drivers, but I'll turn them back on and try the same test on the 560ti to be sure.

if there is anything else you want me to test specifically, now or in the future, let me know.

thanks

@seanradio, thanks for the

jstrecker's picture
Submitted by
Status:
Waiting for review by Vuo Support Team
»
Accepted

seanradio, thanks for the additional info! Looking through your crash reports, we found this:

t= 0.1375s VuoSceneRenderer.cc:1359 VuoSceneRenderer_renderToImage() Not enough graphics memory for a 1920x1080 (4 bytes/pixel * 1 sample) render with depth buffer. Requires 11 MB, have 0 MB.

Looks like Vuo is miscalculating the amount of graphics memory available on your system, which prevents the image from being rendered. Maybe it doesn't correctly handle multiple GPUs. We'll fix that calculation.